Re: Does anybody implement 'reset' in their Instrument Audio Units?
Re: Does anybody implement 'reset' in their Instrument Audio Units?
- Subject: Re: Does anybody implement 'reset' in their Instrument Audio Units?
- From: Jim Wintermyre <email@hidden>
- Date: Thu, 25 Feb 2010 19:00:29 -0800
Specifically in Ableton Live, the host calls AudioUnitReset when the
transport is stopped, meaning that if you have some nice long delay
tails fading out at the end of your set and you hit stop, the audio
cuts off.
Yeah. Super annoying. We've reported this to them on more than one
occassion. We implemented reset in our plugins, so now in Live it
does what you describe. Another weird thing is that the behavior
with VST is different! With VST, they don't do anything to reset the
plugin (there's not a direct call for this that's lightweight, except
maybe setBypass), and they keep calling process until they think that
the output of the plugin is silence. So the reverb tails continue
uninterrupted on transport stop. For AU, they call AUReset
immediately on transport stop, so the reverb tails stop immediately.
But they keep calling Render on the AU, instead of analyzing the
audio output as in the VST case. I believe they check for the
kAudioUnitRenderAction_OutputIsSilence flag and only stop calling the
plugin if that is set.
In our case, it seems that after the AUReset we get a click sent
through the plugin (perhaps because we have a reported latency). So
in the case of a reverb, when you stop the transport the tail
immediately stops, but then you get a click that goes through and
since they keep calling Render, you now have a nice long tail from
the click! Sweet! :)
Jim
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Coreaudio-api mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden