David Reid

I think you might have hit a limitation in miniaudio's graph system that I didn't anticipate. So this is your setup for the vumeter part? ``` test.flac --> splitter -->...

That callback thing is already in the dev-0.12 branch so that'll definitely be coming. However, that's at the `ma_sound` level which is higher level than `ma_node` (`ma_sound` wraps around `ma_node`)....

Sorry the unacceptably long delay on this. I have pushed a potential fix for this to the dev branch. Are you able to verify that fix on your end?

I believe this ticket has been addressed. If not, feel free to reopen this one.

Thanks. I'm going to sit on this for the moment. In the dev-0.12 branch I've actually done a complete overhaul of the decoding backend selection logic and I'm not sure...

So I've taken a look at what I'm doing in the dev-0.12 branch and it was indeed overwriting the result code and returning `MA_NO_BACKEND` at all times in the result...

I deal with all bug reports publicly and transparently. Please post the report here like any other bug report.

This is fixed in 0.11.22. It was from dr_flac which I amalgamate into miniaudio using a tool. dr_flac has also been fixed.

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...

It turns out that support for setting the notification callback via `ma_engine_config` already exists. The correct way to set the callback is like this: ```c ma_engine_config engineConfig = ma_engine_config_init(); engineConfig.notificationCallback...