Hi, I’m not sure if this is a bug or not. This could be a case of RTFM that becomes a feature request…
There is an event “AmbianceOn” that plays a snapshot instrument + a loop region. Documentation says that a snapshot doesn’t need a loop region and is active until stopped, that’s the RTFM part
There is another event “AmbianceOff” that stops the event “AmbianceOn” with a command instrument (stops the event, not the snapshot).
Doing that, the stop is propagated to the snapshot so that’s great, but the snapshot stops without the “fade out” parameter on, so it produces a click (I can replicate this click behavior in code by stopping the snapshot without fade out)
The fix is done by removing the loop region on the event “AmbianceOn” and using the command instrument from “AmbianceOff” to stop the snapshot, not the event. Doing that stops the snapshot with fade out and no click.
So bug, “as designed” or feature request?..
EDIT: ooops, it seems I mixed up things and the loop region is needed for the snapshot to be active. The documentation says that too.
So the fix is “AmbianceOff” event must contain a command instrument that stops the snapshot immediately and then stops the “AmbianceOn” event after 500ms or something so the fadeout can occur… This seems a little tedious: is there another way to do that?