. Re: Aggregate devices and clock domains question
. Re: Aggregate devices and clock domains question
- Subject: . Re: Aggregate devices and clock domains question
- From: Stéphane Letz <email@hidden>
- Date: Tue, 17 Nov 2009 18:15:29 +0100
>
>
> Message: 14
> Date: Tue, 17 Nov 2009 08:51:56 -0800
> From: Jeff Moore <email@hidden>
> Subject: Re: Aggregate devices and clock domains question
> To: CoreAudio API <email@hidden>
> Message-ID: <email@hidden>
> Content-Type: text/plain; charset=iso-8859-1
>
> 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.
>
>
So what would happen if devices are effectively synched but clock domain property does not report that fact correctly? What would setting "clock drift compensation" do in this case?
I hope it does nothing so that we can activate "clock drift compensation" in *all* cases where clock domain is not the same for all devices, and it would not harm if devices are hardware synched.
Can we do that safely?
Thanks
Stéphane Letz _______________________________________________
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