• 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: One io procedure for two related devices
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: One io procedure for two related devices


  • Subject: Re: One io procedure for two related devices
  • From: Jeff Moore <email@hidden>
  • Date: Wed, 21 Jan 2009 14:34:08 -0800

The construct you are looking for is an aggregate device. Aggregate devices allow you to combine multiple devices into a single virtual device with the HAL taking care of making sure the devices are synchronized.

The easiest way to check out aggregate devices is to use Audio MIDI Setup to build one. Then you can poke at it with your app code to see how things work. Note that you can also build aggregate devices programatically via the HAL's API.


On Jan 21, 2009, at 2:24 PM, email@hidden wrote:

I would like to do some simple processing on audio from an input only device to an output only device that are found to be related by the kAudioDevicePropertyRelatedDevices key.

I would like to have just one AudioDeviceIOProc. Should I call AudioDeviceAddIOProc for each device with the same callback, then start each with AudioDeviceStart?



--

Jeff Moore
Core Audio
Apple


_______________________________________________ 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
References: 
 >One io procedure for two related devices (From: email@hidden)

  • Prev by Date: One io procedure for two related devices
  • Next by Date: Re: Few sample rate conversion questions
  • Previous by thread: One io procedure for two related devices
  • Next by thread: Question regarding sound card output latency
  • Index(es):
    • Date
    • Thread