• 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
AudioUnitAddRenderNotify and AudioUnitRender mDataByteSize
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

AudioUnitAddRenderNotify and AudioUnitRender mDataByteSize


  • Subject: AudioUnitAddRenderNotify and AudioUnitRender mDataByteSize
  • From: Craig Bakalian <email@hidden>
  • Date: Sun, 8 Oct 2006 06:59:41 -0400

Hi,

I have just discovered that there are two buffers with a mDataByteSize of 2048 in a callback set up with AudioUnitAddRenderNotify. However, when setting up a AudioUnitRender and its callback the mDataByteSize is 128 with two buffers. So, if I use AudioUnitAddRenderNotify to capture data and store it in memory, and then pull on that data with an AudioUnitRender, weird stuff happens, unreliable stuff.
What is up with this?



Craig Bakalian www.ethinkingcap.com




_______________________________________________ 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: AudioUnitAddRenderNotify and AudioUnitRender mDataByteSize
      • From: William Stewart <email@hidden>
  • Prev by Date: Re: StereoMixer and Volume distribution
  • Next by Date: MusicTrackMerge?
  • Previous by thread: Re: StereoMixer and Volume distribution
  • Next by thread: Re: AudioUnitAddRenderNotify and AudioUnitRender mDataByteSize
  • Index(es):
    • Date
    • Thread