• 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: Paremeter changes by the user
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Paremeter changes by the user


  • Subject: Re: Paremeter changes by the user
  • From: Aristotel Digenis <email@hidden>
  • Date: Fri, 18 Jun 2004 21:07:29 +0100

Thank you Brian and Bill,

Good point, about calling the GetParameter function in the rendering and therefore having the latest value on a per sample basis. However I have chosen to go with the SetParameter when a slider is changed because I will actually be doing some calculations on that incoming parameter before its use in the render stage. I was also a bit confused with the two SetParameter functions, one that takes 2 arguements and one that takes more. I now have it working just fine.

Out of curiosity, calling the GetParameter function for the parameter on every sample would take more processing power than having the value set only when the slider is moved?

Thanks!!!



William Stewart wrote:

Aristotel

This is quite correct - unless you are doing something when the parameter values changes, you only need to get the parameter when you are doing rendering, so don't need to overwrite SetParameter...

Bill

On 17/06/2004, at 2:31 PM, Brian Willoughby wrote:

There may be no need to have a variable that is updated. You could
simply
wait until the render call and set a local variable by calling
GetParameter().
Depending upon which CoreAudio effect class you use, this
technique will even
support sample-acurate parameter changes, because render will be
called with
smaller buffers as the parameter changes.

The only truly necessary class variables in AudioUnits are state
variables
which need to be maintained between render calls. All parameters
can be loaded
into local register variables using GetParameter() before
beginning the
processing loop.

Brian Willoughby
Sound Consulting


Begin forwarded message:

That is starting to make things clearer but I still have a few
questions
I would like to understand. Since the UI calls the SetParameter
function
automatically. So this would mean that I need to override/redefine
the
SetParameter function so that there is a switch command to check
which
parameter has been updated and update the coresponding variable.
_______________________________________________
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.


--
mailto:email@hidden
tel: +1 408 974 4056

__________________________________________________________________________

Culture Ship Names:
Ravished By The Sheer Implausibility Of That Last Statement [GSV]
I said, I've Got A Big Stick [OU]
Inappropiate Response [OU]
Far Over The Borders Of Insanity And Still Accelerating [Eccentric]
__________________________________________________________________________




--
Aristotel Digenis
email@hidden
http://www.digenis.ws
_______________________________________________
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.


  • Follow-Ups:
    • Re: Paremeter changes by the user
      • From: Marc Poirier <email@hidden>
References: 
 >Paremeter changes by the user (From: Aristotel Digenis <email@hidden>)
 >Re: Paremeter changes by the user (From: William Stewart <email@hidden>)
 >Re: Paremeter changes by the user (From: Aristotel Digenis <email@hidden>)
 >Re: Paremeter changes by the user (From: Brian Willoughby <email@hidden>)
 >Re: Paremeter changes by the user (From: William Stewart <email@hidden>)

  • Prev by Date: Start MusicTrack at arbitrary times?
  • Next by Date: Re: Paremeter changes by the user
  • Previous by thread: Re: Paremeter changes by the user
  • Next by thread: Re: Paremeter changes by the user
  • Index(es):
    • Date
    • Thread