Initialize an ma_sound from a file, with notification callbacks

[altschuler]

Thank you for a fantastic library! I recently switched from FMOD core and in several ways the experience has been far better.

I'm looking for a way to initialize an ma_sound with a notification callback setup, like you can with ma_resource_manager_data_source_init (as per 6.1 in the manual). I tried initializing a data source separately and initializing a sound from that, but it becomes somewhat complicated because I then have to wait for the data source to not be MA_BUSY before initializing the sound.

I can add a fence, but the callback mechanism works much better in my case. I'd like this because I want to read and store the length of the audio clip, for which I need the sound/data source to be completely decoded. I'm loading asynchronously.

So to put it simply, is there a built-in way to add a notification callback when initializing a sound from a file? I could create my own version of ma_sound_init_from_file_internal and add it there, but if there's a better way I'd rather do that.

Thanks!

EDIT: I found that by using MA_RESOURCE_MANAGER_DATA_SOURCE_FLAG_WAIT_INIT I don't have to delay initializing the sound. However, I then have to set ma_sound::pResourceManagerDataSource "manually" because I later need to init a sound by copy. Feels a little bit like a workaround.

[mackron]

At first when I was reading I was very confused because I thought it was strange that you wouldn't just do the exact same thing with ma_sound_init() as ma_resource_manager_data_source_init(), but just looking at the code now I see that ma_sound_init() accepts only a fence whereas ma_resource_manager_data_source_init() takes the more flexible ma_resource_manager_pipeline_notifications which supports callbacks. I think this might actually be an oversight on my part. There's no reason not to support callback-based notifications for ma_sound.

There's no easy way to do what you're after. I'll have to figure out a solution for this and report back.

[mackron]

I've gone ahead and pushed a change to the dev branch. I can't change the ma_sound_init_from_file() API because I'm not ready to do a breaking API change, however I've got it so it should work with ma_sound_init_ex().

To use it, you would do something like this:

ma_sound_config config = ma_sound_config_init_2(pEngine);
config.pFilePath = pFilePath;
config.flags = flags;
config.initNotifications.done.pNotification = &myNotification;

result = ma_sound_init_ex(pEngine, &config, &sound);

It's a bit tedious, but it's the best I can do for now. The myNotification will be you custom object that extends from ma_async_notification_callbacks.

Note that I've not had a chance to properly test this yet.

[altschuler]

Thank you so much! 😍 it works great!