• 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
Does AudioUnitGetParameter have a cached value?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Does AudioUnitGetParameter have a cached value?


  • Subject: Does AudioUnitGetParameter have a cached value?
  • From: Rick Sustek <email@hidden>
  • Date: Thu, 7 Jun 2007 17:56:33 -0700

The behavior I am seeing seems to indicate that it does.

From within view code,
when AudioUnitSetParameter is called, subsequent calls to AudioUnitGetParameter return the value which was used in the set call.


Normally, this is what one would expect. Except in a special case I am working on, in which the audio unit rendering layer rejects the value being set. Thus, they become out of sync. If the rendering layer sends a notify event, then things become synced, and AudioUnitGetParameter will return the value as it actually stored down yonder.

I see no mention of this in the documentation, but my observations indicate that there is indeed some caching going on.

Any help appreciated!

Thanks,
-Rick

_______________________________________________
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: Does AudioUnitGetParameter have a cached value?
      • From: Rick Sustek <email@hidden>
  • Prev by Date: Re: Audio Unit Presets and undo
  • Next by Date: Re: change default system output device
  • Previous by thread: Re: change default system output device
  • Next by thread: Re: Does AudioUnitGetParameter have a cached value?
  • Index(es):
    • Date
    • Thread