RE: Recognizing iSight as audio input device?
RE: Recognizing iSight as audio input device?
- Subject: RE: Recognizing iSight as audio input device?
- From: "Stephen Shaw" <email@hidden>
- Date: Fri, 24 Feb 2006 17:13:41 -0800
- Thread-topic: Recognizing iSight as audio input device?
Looking at the # of frames on the inputProc it looks like using iSight
it is processing (and filling the ring buffer with) 800 frames instead
of the usual 512
Meanwhile the output proc is only processing (and pulling from the ring
buffer) 516 frames per call, so it looks like it gets so far behind,
that the input proc just keeps overwriting it and resetting the read
start time.
Using HALLab, it looks like the firewire iSight is 48khz, and the IO
buffer size is 800, and the IO Buffer Size Range is 800 - 800.
In HALLab, the built-in audio has a rate of 48khz, and the IO buffer
size is 512, and the IO Buffer Size Range is 15-6144
I'm not certain how to prevent this overwrite from occurring, even if I
increase the buffer, it will eventually happen.
Thanks!
-Stephen
>According to the code for AudioRingBuffer::CheckTimeBounds, it returns
>kAudioRingBufferError_WayAhead when the requested range isn't currently
in >the ring buffer.
>I'd imagine that this implies that the input device isn't filling the
ring >buffer up for some reason.
_______________________________________________
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