Re: ComplexPlayThru failure if input srate != output srate
Re: ComplexPlayThru failure if input srate != output srate
- Subject: Re: ComplexPlayThru failure if input srate != output srate
- From: Stephen Davis <email@hidden>
- Date: Mon, 19 Mar 2007 13:49:17 -0700
What's even weirder is that it works fine if the input = output when
you start it running and *then* change the input sample rate to
something else. I started at 44100(in):44100(out) and then switched
to 48000:44100 and then 96000:44100 with no issue whatsoever. If I
start running when input != output then it fails almost immediately.
Strange.
stephen
On Mar 18, 2007, at 5:52 AM, Tommy Braas wrote:
I've been experiencing the same problem.
Is the ComplexPlayThru sample code broken?
Any help would be greatly appreciated.
Thanks,
\tommy
On Mar 17, 2007, at 8:13 , Stephen Davis wrote:
I downloaded the ComplexPlayThru example and configured my MacBook
Pro's line input device to 48kHz and the output device to
44.1kHz. I then built and ran the app and it got out of sync
almost immediately and stopped producing output so that the last
buffer it produced repeated over and over again. According to the
code, it should handle devices with different sample rates (and it
prints a message about the mismatch and that it is setting the
playback rate of the AUVarispeed unit to some non-1.0 value) -- is
there something missing?
Some previous posts to this list (Neil Clayton, Bill, and Jeff)
indicate that the code is probably fragile with regard to handling
overloads and discontinuities well. Is there a better example
anywhere?
10.4.9, QT 7.1.5
thanks,
stephen
_______________________________________________
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