Re: recommended practice for routing to multiple devices from one augraph
Re: recommended practice for routing to multiple devices from one augraph
- Subject: Re: recommended practice for routing to multiple devices from one augraph
- From: Christopher Ashworth <email@hidden>
- Date: Wed, 19 Apr 2006 19:41:20 -0400
On Apr 19, 2006, at 6:25 PM, William Stewart wrote:
On 18/04/2006, at 9:46 PM, Christopher Ashworth wrote:
I know that aggregate devices are available on Tiger (both
programmatically and via the setup utility), and that folks have
done output to multiple output devices before Tiger using a matrix
mixer and multiple output AUs.
Ah - I wouldn't be so sure about that assertion.
Huh. Guess I misread this post:
http://lists.apple.com/archives/coreaudio-api/2005/Jan/msg00129.html
<snip>
Its beyond the concept of an AUGraph in general. An AUGraph has a
single output unit - and the device output unit represents a single
device.
If you are running with multiple devices, then you have multiple I/
O procs to deal with (that is, multiple I/O threads). You need to
varispeed the way you feed the various devices (if you are trying
to do what the Agg Device support does and keep multiple devices in
sync), etc... You'd need to buffer your output, etc...
Thanks. That's what I was expecting, and more or less hoping for.
The only trouble then is how to work around the need for that 1-2
second pause when an aggregate device initially starts.
Chris
_______________________________________________
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