• 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: AU parameter display flags
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: AU parameter display flags


  • Subject: Re: AU parameter display flags
  • From: William Stewart <email@hidden>
  • Date: Tue, 15 Feb 2005 16:47:03 -0800


On 15/02/2005, at 4:24 PM, William Stewart wrote:

I think this is consistent: (had to take the picture out) - but basically, this is what I see when drawing a generic UI from this

Display Square = the param value of 0.5 is transformed to a linear value of 0.25 (the slider's about a quarter of the way across)
Display Square Root - the param value of 0.5 is transformed to a linear value of 0.7071 (the slider's about 2.3 of the way across)

HTH

Bill

On 15/02/2005, at 12:14 PM, Marc Poirier wrote:

On Feb 14, 2005, at 7:19 PM, William Stewart wrote:

This is consistent with the way we use Log/Exp...

So, the idea here is that the parameter value is squared to a linear value with the Display Squared flag

"Display the parameter's value by TRANSFORM_IT function on that value" kind of thing.

In which case, "the parameter's value" is the "linear value" or the literal value? In other words, is it done in AUParameterValueFromLinear() and undone in AUParameterValueToLinear(), or done in AUParameterValueToLinear() and undone in AUParameterValueFromLinear()? That's what the difference here is. You can't directly scale the literal value since it could range anywhere, you would at least need to normalize it, and so anyway, I had thought the idea was apply TRANSFORM_IT to the linear value and then mapping it to the literal range/limits. That's what gives the response's feel to a general control (e.g. slider on a GUI, lines in automation drawing, etc.).

This is how DisplayLog has always been interpreted, so we wanted to be consistent with that.

So far as I can tell, that's not the case. Unless I am just getting mixed up here, the behavior that I see is that DisplayLog is transforming in AUParameterValueFromLinear() and un-transforming in AUParameterValueToLinear(), whereas the rest are transforming in AUParameterValueToLinear() and un-transforming in AUParameterValueFromLinear(). That's why I brought this up. But maybe I am just getting lost...

thanks,
Marc


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

________________________________________________________________________ __
"Much human ingenuity has gone into finding the ultimate Before.
The current state of knowledge can be summarized thus:
In the beginning, there was nothing, which exploded" - Terry Pratchett
________________________________________________________________________ __

_______________________________________________
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
References: 
 >AU parameter display flags (From: Marc Poirier <email@hidden>)
 >Re: AU parameter display flags (From: William Stewart <email@hidden>)
 >Re: AU parameter display flags (From: Marc Poirier <email@hidden>)

  • Prev by Date: Re: in & out Callbacks
  • Next by Date: quick and dirty way to play some data?
  • Previous by thread: Re: AU parameter display flags
  • Next by thread: Tone Generation
  • Index(es):
    • Date
    • Thread