On 20 Aug 2010, at 09:18:11, Paul Davis <email@hidden>
That operation involves running the plugin faster than realtime - we
deactivate the plugin(s), reset their block sizes, reactivate them and
then run them as fast as the CPU allows. Is there likely to be some
issue that we are triggering that would affect FFT (and thus
presumably thread-using) plugins that has no impact on other plugins?
I can't think or any reason why code that uses FFTs would need to mess
about with threads.
However, code that processes samples in discrete blocks (such as FFT)
might well be more sensitive to the precise way in which you are
changing the maximum buffer size. Since you just say "deactivate" and
"reactivate" it's not clear what precisely you're doing, but it might
be worth checking that you're doing it exactly as Apple recommends.
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