Re: Getting notifications for AudioUnit ProcessBufferLists method
Re: Getting notifications for AudioUnit ProcessBufferLists method
- Subject: Re: Getting notifications for AudioUnit ProcessBufferLists method
- From: Stefan Gretscher <email@hidden>
- Date: Tue, 8 Feb 2005 19:40:12 +0100
Am 08.02.2005 um 19:09 schrieb Marc Poirier:
I believe that the original question is not about sequencer
start/stop, but about the starting and stopping of DSP rendering
between discontiguous audio regions, where Logic will turn off effects
during the breaks to save on CPU (i.e. the sequencer is continuing to
run this whole time). So far as I could tell from my tests, Logic is
not calling AudioUnitReset() when stopping or restarting DSP in these
cases, which causes the problem originally described. Unless I am
missing something, I think that Logic should be doing a Reset on the
AU(s) in those cases.
Ok, a "gap" in arrangement is something different.
In this case, there is indeed no reset because the engine keeps running
during all time and we've found a few AUs acting so slow on Reset()
(and allocating memory during that function) that it caused serious
problems.
However, the missing reset should not be a problem because the engine
keeps on processing the AU until the tailtime reported by the AU is
over (or until there's less than 60 dB of output for more than 1 second
or so). This way, the AU will run until their buffers are (at least
very close to) silent, and the start of the next audio region should be
processed without leftovers.
Again, if this isn't working as expected please let me know how to
reproduce.
Best,
Stefan
_______________________________________________
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