useForNotification - handle that only one at a time

[alexbainbridge]

Could you handle useForNotification state, and if one is set (and one is already set) that the prior (existing) one is destroyed first

We have multiple features vying to play audio and managing state at our end is ok, but also a bit of overhead could quite like not to have....

Thanks!

[wsamoht]

I see your pain point. Are you trying do a playlist or you just have multiple features playing audio one after another?

Are you using the changeAudioSource and changeMetadata methods? Those were created to easily change the audio for an already added audio item.

[alexbainbridge]

Some of our audio is AI generated, so takes e.g. 10 seconds to generate (at point of initialize), so we cant do that preload at the same time we are playing something else..... beginning to think all our audio should be background, and we just initialize the usefornotificaiton with e.g 1 second of silence, and never actually play or destroy it.....

No, we are destroying and restarting everytime, mostly because it kind of "just works" ;)

[wsamoht]

Got it. It sounds like more of a playlist style would be better. Several people are using this plugin for a playlist which was not thought of when I created it as we didn't need it at for our app. But, I am considering doing some rewrite to support a playlist and changing how background music is added.