Re: IOAudioStream[0x148cc00]::clipIfNecessary() - Error:
Re: IOAudioStream[0x148cc00]::clipIfNecessary() - Error:
- Subject: Re: IOAudioStream[0x148cc00]::clipIfNecessary() - Error:
- From: Mark Cookson <email@hidden>
- Date: Tue, 02 Nov 2004 17:09:49 -0500
That error comes from IOAudioFamily when it detects that CoreAudio is
calling it to process output samples that are discontinuous from the
previous call by more than the size of the driver's ring buffer. Like the
first call is on loop count 20 and the second call is on loop count 22+.
In this case, it's loop count 416c9 to 416ce, a gap of 5 loops around the
hardware's buffer. That's a mighty big dropout. IOAudioFamily can't do
anything about it, so it just throws away its old idea of where the loop
count was and syncs up with where CoreAudio thinks it should be (which is
416cd in this case because it loops around the end of the buffer).
For the most part, this is generally related to bad time stamps coming from
the driving confusing CoreAudio as to where it should be writing samples.
It's odd that you say you are seeing this with multiple different vendor's
hardware that have shipping drivers.
Are there lots of these errors in /var/log/system.log, or only a few? If
there are lots, then they are likely to be an important clue, but if they
are few and far between, they could be startup noise that happens every once
in a while and can be ignored.
Regards,
Mark
--
Mark Cookson
M-Audio
225 Locust St.
Hudson, WI 54016
On 11/2/04 6:21 AM, "Stefan Haller" <email@hidden> wrote:
> We are receiving customer reports about audio dropouts. They tell us
> that they find console log entries like these:
>
> Oct 28 23:38:05 localhost kernel: IOAudioStream[0x148cc00]::clipIfNecessary()
> - Error: attempting to clip to a position more than one buffer ahead of last
> clip position (416c9,219)->(416ce,69).
> Oct 28 23:38:05 localhost kernel: IOAudioStream[0x148cc00]::clipIfNecessary()
> - adjusting clipped position to (416cd,219)
>
> This seems to happen with various hardware, for example Motu 828, or
> M-Audio Audiophile FW.
>
> Is this a problem of the driver, of the hardware, or of the host
> application? What can we do to figure out what's wrong?
>
_______________________________________________
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