# \[RESOLVED\]Custom codec priority issue with fmod 5

**URL:** <https://qa.fmod.com/t/resolved-custom-codec-priority-issue-with-fmod-5/12082>\
**Category:** FMOD Engine\
**Created:** [October 12, 2015, 8:55am UTC](https://qa.fmod.com/t/resolved-custom-codec-priority-issue-with-fmod-5/12082 "2015-10-12T08:55:31Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![luojinghua](https://avatars.discourse-cdn.com/v4/letter/l/c5a1d2/32.png) [@luojinghua](https://qa.fmod.com/u/luojinghua)\
**Post date:** [October 12, 2015, 8:55am UTC](https://qa.fmod.com/t/resolved-custom-codec-priority-issue-with-fmod-5/12082/1 "2015-10-12T08:55:31Z")

</div>

Hi,

I have a static opus codec which works fine on fmod 4. The codec is registered to FMOD with priority 2700. FMOD 5 seems ignore my codec when creating a sound with opus file. if I change the priority to 0, then both open and play works. But all other sounds won’t work any more since FMOD tries to open them with my codec.

---

<div class="post-metadata">

**Author:** ![nick1](https://avatars.discourse-cdn.com/v4/letter/n/47e85d/32.png) [@nick1](https://qa.fmod.com/u/nick1)\
**Post date:** [October 12, 2015, 11:22pm UTC](https://qa.fmod.com/t/resolved-custom-codec-priority-issue-with-fmod-5/12082/2 "2015-10-12T23:22:00Z")

</div>

That’s weird the codec list logic hasn’t changed between FMOD 4 and FMOD 5.

What sort of container format are you putting your encoded data in?

If your codec returns FMOD\_ERR\_FORMAT from the open callback FMOD will move the next codec in the list. So putting your codec at position 0 shouldn’t be a deal breaker.

---

<div class="post-metadata">

**Author:** ![luojinghua](https://avatars.discourse-cdn.com/v4/letter/l/c5a1d2/32.png) [@luojinghua](https://qa.fmod.com/u/luojinghua)\
**Post date:** [October 12, 2015, 11:57pm UTC](https://qa.fmod.com/t/resolved-custom-codec-priority-issue-with-fmod-5/12082/3 "2015-10-12T23:57:00Z")

</div>

> [@](#):
>
> That’s weird the codec list logic hasn’t changed between FMOD 4 and FMOD 5.
> 
> What sort of container format are you putting your encoded data in?
> 
> If your codec returns FMOD\_ERR\_FORMAT from the open callback FMOD will move the next codec in the list. So putting your codec at position 0 shouldn’t be a deal breaker.

Thanks very much. The FMOD\_ERR\_FORMAT is exactly what I’m looking for. Changing the code to return FMOD\_ERR\_FORMAT instead of FMOD\_ERR\_UNSUPPORTED should fix the issue.