• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: recommended practice for routing to multiple devices from one augraph
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: recommended practice for routing to multiple devices from one augraph


  • Subject: Re: recommended practice for routing to multiple devices from one augraph
  • From: William Stewart <email@hidden>
  • Date: Wed, 19 Apr 2006 15:25:24 -0700


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.

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?

yes


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?

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...

BIll


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

--
mailto:email@hidden
tel: +1 408 974 4056
________________________________________________________________________ __
"Much human ingenuity has gone into finding the ultimate Before.
The current state of knowledge can be summarized thus:
In the beginning, there was nothing, which exploded" - Terry Pratchett
________________________________________________________________________ __


_______________________________________________
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


  • Follow-Ups:
    • OT: xcode and cvs
      • From: Peter Thom <email@hidden>
    • Re: recommended practice for routing to multiple devices from one augraph
      • From: Christopher Ashworth <email@hidden>
References: 
 >recommended practice for routing to multiple devices from one augraph (From: Christopher Ashworth <email@hidden>)

  • Prev by Date: Re: siCompressionParams Question
  • Next by Date: Re: Crashing Auval
  • Previous by thread: recommended practice for routing to multiple devices from one augraph
  • Next by thread: Re: recommended practice for routing to multiple devices from one augraph
  • Index(es):
    • Date
    • Thread