I’m using an app that uses fmod.dll (prod version 1.8.15). This app does not handle opus codec, but as far as I know fmod supports opus through a plugin. Where can I find that opus plugin, would this work without recompiling the app (e.g. by dropping whatever dll beside fmod.dll)?
There’s no opus support or opus plugin that i’m aware of, unless a 3rd party has written one.
Its entirely possible to have a plugin that supports ogg? opus.. opus is a name for the combination of the low level silk/celt codecs , but its not a file format itself.
in my case opus is inside ogg, yes. I’d like to write my own plugin and after some google-fu I found that fmod_codec_raw.cpp example.
How does fmod know to use this codec_raw?.. where do I put generated dll? does fmod need to be updated? There is absolutely no code that in any way could tell that, “yes, this codec_raw should be used for this file format/codec.”
In other word, this sample is nonsense and IMO it should be redone by somebody who does not know internals of fmod, as this code is full of some assumptions that only known to the person familiar with internals of fmod.
it took me entire day to hard guessing how to write an opus module for fmod. It shouldn’t be overloaded with guesswork, for somebody not very familiar with how media works this would probably be impossible to do.
I deleted my rant comments, as these aren’t relevant to my original topic.
I strongly suggest to delete codec_raw example and rewrite it with codec_wav that would read a wave a file instead of raw pcm. This way, that sample would probably cover most of the basics. It should also make it clear that fmod codec is a format parser and/or decoder at the same time.
Another point… I always wasn’t too happy when some company uses 80 char limit per line or something like that. After working, with fmod I can definitely tell that important docs should never be endless lines that require horizontal scrolling.
Sorry you had trouble writing the codec, I had a look at fmod_codec_raw and yes it is ‘brief’, it from the look of it is also 13 years old, yikes! The codec plugin side of things aren’t used that often, so it doesnt get the same love as some of the other areas, like DSP plugins (that was just updated recently).
Sounds like a good idea to put a more ‘complete’ codec in there, we could just take our current wav codec and strip it down a bit (because ours supports ACM and riff wrapped mp3, and all sorts of weird stuff).
I’m not sure what you mean about the docs, if you work in markdown or html for example, its not the document’s job to word wrap for the user, its the viewer that is supposed to do that (so it is resolution independent), like our online docs at http://www.fmod.org/documentation or the .chm version with that viewer.
We’d love to hear how we can improve the codec side of things, i’ll look at doing something for the next release, if you’d like please contact me at firstname.lastname@example.org and we can try and make it better for the next release.
- You must login to post comments
Please login first to submit.