Number of samples in clip/convert calls
Number of samples in clip/convert calls
- Subject: Number of samples in clip/convert calls
- From: Phil Montoya <email@hidden>
- Date: Fri, 11 May 2012 20:10:29 +0000
- Thread-topic: Number of samples in clip/convert calls
Is there a way to change or influence the number of audio samples that are sent in a convert or clip call?
Historically our hardware had multiple DMA engines and could devote one of the DMA engines to service audio. We are now looking at AV hardware with only a single DMA engine and are concerned about audio drop outs. We normally get 512 audio samples per clip/convert call which is about 10ms of time which is barely enough time to DMA an uncompressed HD video frame and not enough time if we are dealing with 2K or 4K video frames.
I was playing with HALLab and changed IO Buffer Size but that didn't seem to have any effect on the number of samples that are sent during a clip call.
We would like to get audio in 2048 sample chunks which we can DMA and then have 40ms to take care of other important timely deliveries such as video before the next audio chunk arrives. How do you tell the HAL to deliver audio in larger chunks?
-Phil
_______________________________________________
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