You'll need to be a bit more specific. If you are writing a user-space
driver, you don't have the IOAudio family's services available to you.
You are completely on your own with respect to buffer management. The
only constraints are the semantics of the HAL's API imposes.
On Dec 20, 2004, at 7:38 AM, Tommy Schell wrote:
Hi,
Suppose I have a CoreAudio driver which, instead of pulling data
directly from the hardware, received (and gave) audio data via
a user space firewire driver. That is, incoming data came from user
space down to CoreAudio driver, and outgoing data went
from CoreAudio driver up to the user space firewire driver. Would
that negatively impact buffer creation or management?
And then how exactly is a CoreAudio driver's ring buffer managed? How
does the data get wrapped around?
Does it all happen automatically behind the scenes?
If the data came from user space, would the ring buffer be effected?
How would I trigger an interrupt when the ring buffer wraps around (to
take a time stamp), if the CoreAudio driver isn't
dealing directly with hardware?
Thanks a lot,
Tommy Schell
--
Jeff Moore
Core Audio
Apple
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Coreaudio-api mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/coreaudio-api/email@hidden
