You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The callback is not triggered after calling ma_sound_stop, it is called only when we reach the end of the audio file.
This may cause a race cindition as we do not know at this point if the audio thread is properly stopped.
The text was updated successfully, but these errors were encountered:
That technique is not technically the right way to do it, but probably won't cause any issues. Typically you would configure that via the device config, but that is inconvenient because you would need a self-managed device in that case. A better solution might be for the onNotification callback to be added to ma_engine_config. I'll leave this issue open to remind me to consider adding support for that.
The callback is not triggered after calling ma_sound_stop, it is called only when we reach the end of the audio file.
This may cause a race cindition as we do not know at this point if the audio thread is properly stopped.
The text was updated successfully, but these errors were encountered: