AudioParameter bug?


#1

Hi guys,

As it would be so strange how it could survive, maybe I'm wrong on this but:

  1. In your derived AudioParameter classes (AudioParameterFloat,AudioParameterInt,...) the "value" member variable stores non-normalized values
  2. All their "operator=" functions compare it to a normalized value before calling "setValueNotifyingHost (normalisedValue);"

Am I wrong or is it a bug?

 

Kevin


#2

Isn't that a bug I fixed a couple of weeks ago?


#3

I don't know, I'm currently working with Version 4.1

 

Just checked on GitHub and yes you fixed this bug, thanks!

(though it's still not part of the latest release)


#4

On a side note:

I know that the original VST paradigm was that all parameters are floats from 0.0 - 1.0. I'm guessing that it's no longer the case. 

Has anyone run into problems with parameters outside the [0.0, 1.0] range in any specific hosts/formats?

 

 

 


#5

It's always going to be a normalised range from a host's POV regardless of the plugin format, so yes - you need to keep it that way.

On the other hand, if you adopt the new parameter objects for everything, they'll let you work from a different range at an intuitive high-level, doing the necessary conversions for you.