hey fmod,
we’re using some StudioEventEmitter components set to play OnEnable and stop OnDisable events to play some looping sounds in the background of a scene. Normally this is fine if plays and stops are not called on the same frame.
However, we’ve hit a small issue when some other logic enables and disables the emitter several times during the same frame during scene startup and the sounds are looping / not oneshots. Our game logic actually activates/deactivates a hierarchy of gameobjects due to how the host/client networking framework works and some sound emitters are children under that hierarchy so they’re affected as various things start up. It’s also not really valid to shift to using Start/Destroy type events as the networking can start/stop any time, so OnEnable/OnDisable are appropriate events for us to use.
Making a repro for the issue, it looks like the StudioEventEmitter doesn’t support doing a Play Stop Play immediately after each other on the same frame. The final Play does not work. If the instance is manually released (I tested adding this into the fmod PlayInstance code) then it plays ok, so it appears the calls aren’t being handled correctly somewhere either by the StudioEventEmitter with some protection or in the engine processing the events and invalidating the instance.
This might be a known issue - apologies if I haven’t found it. Is there a workaround within fmod studio or using the StudioEventEmitter or do we need to wrap our usage in a coroutine/async or some other handler to avoid the repeated Play Stop Play?
A repro for this is fairly easy - just make a script with a reference to a StudioEventEmitter and in a test method call myEventRef.Play(); myEventRef.Stop(); myEventRef.Play(); and you should notice that the sound does not play.
Thanks for any tips or advice on this little issue. I’m sure we can work around it but if there’s an obvious fix or you can repro and fix in the future then great.
cheers,
// greg
