Re: Jaguar broke our audio input engine
Re: Jaguar broke our audio input engine
- Subject: Re: Jaguar broke our audio input engine
- From: Rob Cas <email@hidden>
- Date: Wed, 11 Sep 2002 16:36:51 +1000 (EST)
Hi Tim,
I can't offer any solution, but I've been seeing exactly the same
thing as well, and am equally puzzled.
Rob.
>
Hello,
>
>
Our core audio driver was working fine in 10.1.5, but we are seeing
the
>
following error in the system log under 10.2:
>
>
!!! firstSampleFrame->audioEngine->numSampleFramesPerBuffer (XXXXX >
16384)
>
>
This error occurs after we have taken the initial time stamp and
started our
>
engine and before we get to the end of our buffer to take another
time
>
stamp.
>
>
Furthermore, the first time CoreAudio calls our ConvertInputSamples
it does
>
so with the firstSampleFrame being somewhere around 13000. At this
time we
>
have only filled approximately 7000 frames into our buffer.
>
>
Two questions:
>
>
(1) How does CoreAudio calculate the firstSampleFrame when it sends
the
>
above error to the system log? Is it via getCurrentSampleFrame()? If
so, how
>
is it computing that we are out of our NumSampleFrames (16k in our
case)? We
>
have verified that we only pass back a number between 0 & 16383.
>
>
(2) Why would CoreAudio call ConvertInputSamples with the
firstSampleFrame
>
way ahead of our hardware pointer? Is there a mechanism whereby we
can set a
>
certain offset so that this is delayed until we have actually filled
our
>
sample buffer up to that point?
>
>
Any help would be greatly appreciated.
>
>
Thanks,
>
>
Tim
http://mobile.yahoo.com.au - Yahoo! Messenger for SMS
- Now send & receive IMs on your mobile via SMS
_______________________________________________
coreaudio-api mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/coreaudio-api
Do not post admin requests to the list. They will be ignored.