Re: Aggregate devices and clock domains question
Re: Aggregate devices and clock domains question
- Subject: Re: Aggregate devices and clock domains question
- From: Jeff Moore <email@hidden>
- Date: Tue, 17 Nov 2009 08:51:56 -0800
That's something for the drivers involved to figure out. To be sure in some cases, it's hard or impossible to do because the device itself doesn't know enough about the situation, so the driver can't really do anything. There are other cases though, where it does work out and the drivers can provide the specific information necessary.
On Nov 17, 2009, at 8:44 AM, Paul Davis wrote:
> On Tue, Nov 17, 2009 at 11:39 AM, Jeff Moore <email@hidden> wrote:
>>
>> On Nov 17, 2009, at 6:49 AM, Stéphane Letz wrote:
>>
>>> So continuing the thead on Aggregate devices and clock domains :
>>>
>>> - do externally synched audio devices (using wordclock...) would appear as a same " clock domain"?
>>
>> They should, but not all drivers support the clock domain property.
>
> Even if if they support the property, how would they know? If I have
> two devices, both connected to an external clock source, how could
> they determine that they are on the same clock, and thus in the same
> clock domain? What clock domain would it be?
--
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