Re: AU "offline" processing
Re: AU "offline" processing
- Subject: Re: AU "offline" processing
- From: Alberto Ricci <email@hidden>
- Date: Tue, 4 Feb 2003 09:47:17 +0100
At 6:13 PM -0800 2/3/03, Bill Stewart wrote:
We've never scene the distinction between off-line and real time as
a necessary distinction to make at the AU level - typically that is
a host level decision.
I agree. Rendering quality and other properties provide all the
flexibility that's needed by AU hosts.
The point here is non-causal effects. Those ones cannot run in real
time by definition.
Random access to different data streams from the host is *another*
topic entirely - I don't see that it has anything to do with either
offline/RT rendering (or format conversion)...
It doesn't have anything to do with offline rendering, but it's
important non-causal effects. This is because the only way for a
non-causal effect to do its job is to be able to access samples
randomly.
I'm not sure that I understand the reversal semantic - it seems to
me this is a host problem, not an AU one (and then the host just
has to feed that data a different way - and it gets really
complicated for soft-synths:)
The Reverse plug-in (or time-reversal, or whatever) was merely an
example of a non-causal process. A normalization plug-in is another
example, brought up by Steve. It can't be handled by the host,
because to the host, such plug-ins appear just like any other
plug-in. They wouldn't know that they should feed data backwards to a
Reverse plug-in. Similarly, they wouldn't know that they should feed
data twice to a normalize plug-in, once for finding the peak value
and a second time for adjusting the gain.
Alberto.
_______________________________________________
coreaudio-api mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/coreaudio-api
Do not post admin requests to the list. They will be ignored.