Re: SimplePlayThru moved?
Re: SimplePlayThru moved?
- Subject: Re: SimplePlayThru moved?
- From: Doug Wyatt <email@hidden>
- Date: Thu, 29 Jul 2010 08:58:40 -0700
Some desktop machines have a single input/output audio device for built-in. Many don't. You can't assume one way or the other.
You might play around with Audio MIDI Setup's audio windows -- it's built using the same public API's that you can use.
You'll need an AUHAL instance per device.
An alternative is to aggregate the built-in input and output devices, though that has its tradeoffs... (for starters, you'd have to force the two hardware sample rates to match)
Doug
On Jul 29, 2010, at 8:41 , Chris Adamson wrote: To clarify why I'm looking to make the distinction between using a CAPlayThrough (which uses two units [either two AUHALs or an AUHAL for input and DefaultOutput for output… the description in the CA Overview doesn't match the sample's README]), versus SimplePlayThru (which apparently uses a single AUHAL)…
I've done most of my Core Audio work on iOS, where I've used a single RemoteIO unit for both input and output. It's pretty trivial to do pass-through by enabling input-scope/bus1 and output-scope/bus0, and then connecting output-scope/bus1 to input-scope/bus0.
I was trying to do the same thing in OS X this morning by setting up an AUHAL unit with the default input device, but I find I can't set the device on the unit (kAudioUnitErr_InvalidPropertyValue) unless I disable output on the unit. Which makes me think I must use two units on OS X, one for input and one for output, as CAPlayThrough does. If SimplePlayThru uses a single unit for input and output, that seems more like the iOS case. And that would make me happy.
--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