Question: Thread-safety of ma_engine / ma_sound operations (loading, playing, stopping)

[Snouf-ID]

Hi,

I’d like to clarify the thread-safety guarantees of miniaudio, especially regarding the high-level API (ma_engine, ma_sound, etc.).

In my game engine, I use a thread pool for asset loading and audio playback management.
Before integrating deeper, I want to make sure which of the following operations are safe to call concurrently from multiple threads that share the same ma_engine instance:

ma_sound_init_from_file() / ma_sound_init_from_data_source()

ma_sound_uninit()

ma_sound_start() / ma_sound_stop() / ma_sound_seek_to_pcm_frame()

ma_engine_play_sound()

ma_engine_play_sound_ex()

ma_engine_stop()

In short:
Can these functions be called safely from multiple threads (e.g., background loading threads) without explicit synchronization?
Or should I protect access to the shared ma_engine (and its sounds) with a mutex on my side ?

Thank you :)

[mackron]

Sorry for the delay. Everything you mentioned there should be thread safe. If you find a threading related bug in any of those functions that should definitely be considered a bug.