0
0

I haven’t had any luck finding an answer in the examples or in the docs. Since the 360 is using the lib with all plugins included is there a way to explicitly specify which codec to use when calling createstream instead of having fmod try each codec until it finds the right one. I am running in to timing issues with streams, I know one simple workaround is to create them asynchro but it seems inefficient to try all the codecs when extensions or tags can specify the correct type.

  • You must to post comments
0
0

The information can be found from the createStream documentation linking to FMOD_CREATESOUNDEXINFO structure. It has a member called ‘suggestedsoundtype’

  • You must to post comments
Showing 1 result
Your Answer

Please first to submit.