Re: Sample gaps in the IOProc?
Re: Sample gaps in the IOProc?
- Subject: Re: Sample gaps in the IOProc?
- From: Jeff Moore <email@hidden>
- Date: Wed, 5 Mar 2003 12:08:07 -0800
Discontiguous sample numbers indicate that the HAL had to resynch for
some reason. The most common reason for this is the process is taking
too long in the IOProcs. This is indicated by notifications on
kAudioDeviceProcessorOverload.
On Wednesday, March 5, 2003, at 12:43 AM, Jeremy Sagan wrote:
What does it mean, when in successive calls to my Core Audio IO
procedure the difference in inOutputTime-> mSampleTime is not equal to
the completion (audio packet) size?
I am assuming this means my processor is too slow. Yes? Or is this
caused by page faults?
Here is the pseudo code for checking for a glitch (gap). I left out
the initialize code.
static OSStatus myIOProc ( AudioDeviceID inDevice, const
AudioTimeStamp* inNow, const AudioBufferList* inInputData, const
AudioTimeStamp* inInputTime, AudioBufferList* outOutputData, const
AudioTimeStamp* inOutputTime, void* inClientData)
if (inOutputTime->mSampleTime - gCASampleTime != caCompletionSize)
{
Is this the source of an audio glitch?
gCASampleTime = inOutputTime->mSampleTime;
}
Jeremy
_______________________________________________
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.
--
Jeff Moore
Core Audio
Apple
_______________________________________________
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.