• 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
Re: Opinions sought: AudioUnit Rendering
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Opinions sought: AudioUnit Rendering


  • Subject: Re: Opinions sought: AudioUnit Rendering
  • From: email@hidden
  • Date: Wed, 6 Mar 2002 16:46:17 -0600 (CST)

I believe the point of setting mDataByteSize and supplying 0s for
frames in the buffer that don't have valid output was so that old code
would not have to be changed to check if it got all the bytes it asked for
- it always would. You'd only have to change your old code if you wanted
to take advantage of this new feature, otherwise it'll work just as it
always has and in that way it is the same as the other suggestions.
Therefore I don't see the reason why it would not be backwards-compatible.
I would strongly vote for this option as I think it is the simplest
solution that is close to the actual data model. In my internal audio
sources I use this same functionality and I would assume it wouldn't be
alien to other developers.


Ben


On Wed, 6 Mar 2002, Doug Wyatt wrote:

> While this sort of protocol has its uses, in this case it would be a
> seriously non-backwardly-compatible change to the existing AudioUnit
> API. It would require that all existing AudioUnits check to see whether
> they actually got all the data they asked for, though the existing API
> contract for RenderSlice is that the AU must provide as much data as was
> asked for. So we can't do that.
>
> Doug
>
> On Tuesday, March 5, 2002, at 11:19 , Douglas Wright wrote:
> > I prefer to have the byte count set to the number of valid samples in
> > the
> > buffer. The buffer can still be there and full of zeros for units that
> > don't check. For units that do, units that would be expensive to leave
> > on
> > and who's authors take the time to figure this out, they can handle 0,
> > or
> > any other number for that matter, up to the actual size of the buffer.
> > So
> > if a sampler unit finishes playing back a sample half way through a
> > buffer
> > and the rest is filled with silence, it can indicate that as well as
> > cases
> > where the entire buffer is silence.
> --
> Doug Wyatt
> work: email@hidden (CoreAudio)
> personal: email@hidden http://www.sonosphere.com
>
> "Better to look like an idiot than to be one."
> -- dsw
> _______________________________________________
> coreaudio-api mailing list | email@hidden
> Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/coreaudio-api
> Do not post admin requests to the list. They will be ignored.
_______________________________________________
coreaudio-api mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/coreaudio-api
Do not post admin requests to the list. They will be ignored.

References: 
 >Re: Opinions sought: AudioUnit Rendering (From: Doug Wyatt <email@hidden>)

  • Prev by Date: Re: Opinions sought: AudioUnit Rendering
  • Next by Date: Re: Opinions sought: AudioUnit Rendering
  • Previous by thread: Re: Opinions sought: AudioUnit Rendering
  • Next by thread: Re: Opinions sought: AudioUnit Rendering
  • Index(es):
    • Date
    • Thread