• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
CoreAudio driver's buffer management
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

CoreAudio driver's buffer management


  • Subject: CoreAudio driver's buffer management
  • From: Tommy Schell <email@hidden>
  • Date: Mon, 20 Dec 2004 08:38:40 -0700

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

_______________________________________________
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


  • Follow-Ups:
    • Re: CoreAudio driver's buffer management
      • From: Jeff Moore <email@hidden>
  • Prev by Date: Midisport and sysex
  • Next by Date: RE: Midisport and sysex
  • Previous by thread: RE: Re: Midisport and sysex
  • Next by thread: Re: CoreAudio driver's buffer management
  • Index(es):
    • Date
    • Thread