recommended practice for routing to multiple devices from one augraph
recommended practice for routing to multiple devices from one augraph
- Subject: recommended practice for routing to multiple devices from one augraph
- From: Christopher Ashworth <email@hidden>
- Date: Wed, 19 Apr 2006 00:46:13 -0400
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. I've had trouble pulling up definitive
references on the subject in the archives, however, so:
On 10.4 and later, is the "right" way to do multiple device output
using one graph an aggregate device?
Is it fair to say it takes a good bit of effort to get an AUGraph
with multiple output devices to behave correctly, if one was not to
use an aggregate device?
I have a user who would like me to implement mapping outputs across
multiple devices within my application; I'm trying to get a sense of
the recommended approach. Setting up an aggregate device externally
works now, and I wonder if I should just leave it at that or if there
is any benefit that can be reaped from managing it in the application.
Thanks much,
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