timestamps/ buffering with incoming NTSC audio frames in CoreAudio driver
timestamps/ buffering with incoming NTSC audio frames in CoreAudio driver
- Subject: timestamps/ buffering with incoming NTSC audio frames in CoreAudio driver
- From: Tommy Schell <email@hidden>
- Date: Thu, 6 Jan 2005 09:01:24 -0700
Hi,
What is a good strategy for buffering/ timestamping incoming NTSC audio
in a CoreAudio driver?
A frame of NTSC audio contains between 1600 and 1602 audio samples.
So should I make 1 buffer big enough to hold several NTSC audio frames,
and then take a timestamp when
the buffer loops back to beginning?
Or do the buffers need to be separated out?
And then if I have different size buffers, do I need more than 1 audio
engine to accomodate this?
Also, how does an application or the HAL know whether I have 1600 or
1602 audio samples for it on a
given reqest for input audio?
Or the index of the 1st sample frame for a given request?
Thanks,
Tommy Schell
_______________________________________________
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