Re: Using aggregate devices with iSight
Re: Using aggregate devices with iSight
- Subject: Re: Using aggregate devices with iSight
- From: Jeff Moore <email@hidden>
- Date: Mon, 17 Jul 2006 09:08:14 -0700
I guess I don't understand the question. What other API would you
use? The HAL is the only API for talking to audio hardware.
This situation is that some devices can be aggregated while some
devices can't. It is no different than what you have where some
devices have a master volume control and some devices don't.
Applications need to be prepared to deal with both situations.
On Jul 15, 2006, at 11:23 PM, Neil Clayton wrote:
Thank Jeff,
So am I really going about things the wrong way using CoreAudio as
a means by which to monitor any device? Or is it expected that I
have to have special case code to see if the particular device is
supported by CA and then use some other method?
---
Neil Clayton
On 16 Jul 2006, at 02:44, Jeff Moore wrote:
Device aggregation only supports devices implemented via an
IOAudio family-based driver in the kernel. The reason why is that
device aggregation is exploiting features of IOAudio in order to
function.
The iSight, being a user-space driver, is ineligible for aggregation.
On Jul 15, 2006, at 1:28 PM, Neil Clayton wrote:
I'm messing with aggregate devices at the moment, in my
continuing quest to be able to reliably monitor the audio level
of some random input device. In my case, I'm only wanting to
monitor things like mics, usb mics, and iSights - essentially any
standard input source.
I thought I'd then try the iSight, but soon found that when I add
a new aggregate in AMS - the iSight doesn't appear in the sub
device list.
What must I must do to get the iSight available as an input source?
--
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