0
0

A machine here with an nVidia nForce with the latest drivers fails with FMOD_ERR_OUTPUT_DRIVERCALL under the following circumstances:
[code:m4eqqu7s]System::createSound, mode = FMOD_HARDWARE | FMOD_OPENMEMORY
System::playSound, FMOD_CHANNEL_FREE, paused = false
[/code:m4eqqu7s]
Using FMOD_SOFTWARE works. HARDWARE channels work fine on this soundcard for files opened without FMOD_OPENMEMORY.
Is this documented/intentional behaviour?

  • You must to post comments
0
0

it might be something to do with the frequency of the sound. Some soundcards don’t support certain frequency ranges when they report they do.
Just use FMOD_SOFTWARE anyway, FMOD_HARDWARE is becoming more and more redundant with FMOD Ex, we may even remove it in the future.

  • You must to post comments
Showing 1 result
Your Answer

Please first to submit.