0
0

When calling getOpenState on a non-blocking stream (e.g. streaming a large MP3), after the initial FMOD_OPENSTATE_SEEKING or FMOD_OPENSTATE_BUFFERING states change to FMOD_OPENSTATE_READY, would you expect the FMOD_OPENSTATE to change [b:hvcykusa]from[/b:hvcykusa] FMOD_OPENSTATE_READY if it’s buffering normally without any problems?

Specifically should it change to FMOD_OPENSTATE_BUFFERING when it’s accessing the media to get new data, or does it only change to FMOD_OPENSTATE_BUFFERING if it’s been unable to get data in time due to it starving or whatever?

  • You must to post comments
0
0

buffering is a normal operation and it just means it is reading in another thread.

For starvation, check the ‘starving’ flag at the end of getOpenState. That is the best function to use if you need to mute the sound due to stuttering/starvation.

  • You must to post comments
Showing 1 result
Your Answer

Please first to submit.