Ok, a quick idea – how about an ‘FMOD_SAFEMODE’ flag at FMOD_Init time.

This flag could force FMOD to use settings that are generally ‘safe’ to use on a wide range of cards/configs etc, and ignore potentially unsafe settings.

Brett is likely to have a much better idea of what’s ‘safe’ or not over a wide range of configs, so it would save users from having to find out this stuff the hard way.

I’m thinking of things like USEDEFAULTMIDISYNTH, HW3D (and the related SetMaxChannels() ‘fix’) and possibly other stuff I don’t know about yet.


  • You must to post comments
Showing 0 results
Your Answer

Please first to submit.