Play through (was Re: SimplePlayThru moved?)
Play through (was Re: SimplePlayThru moved?)
- Subject: Play through (was Re: SimplePlayThru moved?)
- From: Chris Adamson <email@hidden>
- Date: Thu, 29 Jul 2010 16:40:22 -0400
Thanks Doug. Two quick questions for a simple play through example that uses two units:
* Can I use kAudioUnitSubType_DefaultOutput for the output unit, rather than an kAudioUnitSubType_HALOutput? Is there a particularly good reason to coose one or the other?
* My current strategy is to set up and start input and output units, and have output unit's render proc call AudioUnitRender() on the input unit. Doesn't work, at least not yet. Do I need to plan on having a separate render proc for each, with input's render proc buffering samples and output's reading from that buffer? (Ugh.)
Play through was pretty simple on iOS (an example I wrote for a conference talk was under 300 lines), so I'm stunned that it's so much harder on OS X. To wit, CAPlayThrough requires 1,500 lines and three languages. I'm eager to show something simpler, if possible.
And, apropos of the original subject, was the SimplePlayThru example removed from the developer.apple.com site at some point?
--Chris
On Jul 29, 2010, at 11:58 AM, Doug Wyatt wrote:
> 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)
_______________________________________________
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