Re: Work-arounds for driver-level input latency
Re: Work-arounds for driver-level input latency
- Subject: Re: Work-arounds for driver-level input latency
- From: William Stewart <email@hidden>
- Date: Fri, 4 Sep 2009 19:46:30 -0700
On Sep 4, 2009, at 3:43 PM, Jeff Moore wrote:
On Sep 4, 2009, at 3:35 PM, Zachary Schneirov wrote:
The same device has both an input and output stream and refuses
sample rates that differ between them. It uses Apple's built-in USB
audio driver. Unfortunately I can't seem to avoid this increase in
input latency using aggregate devices with a clock source of either
the USB or Built-In device regardless of which is resampled. Output
latency on the C-Media device is not as much of an issue.
It sounds like the device in question has a problematic USB
implementation. It would probably be worth filing a bug in Radar
about it so that the folks that work on the USB Audio driver can
take a look to see what's going on.
If this is a bug in the AppleUSBAudio driver, what might be
conceivable workarounds? I'm willing to consider time-consuming and/
or not-entirely-ideal alternatives.
I imagine that there are no work-arounds since the problem seems to
be related to the hardware.
To add to this - I would also verify your testing, etc, by running
another device. Try the built-in (make an aggregate from the input/
output in Audio MIDI Setup (AMS)) and see if you get similar results.
Thanks
Bill
_______________________________________________
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