[gephex-devel] frei0r problem with the range of f0r_param_double

[Jean-Sebastien Senecal]

Hi all,

    We faced a similar problem in Drone. What we concluded is that no 
range should be forced at any time. This encourages experimentations 
from the user. The ranges should be seen more as some kind of "default 
values" within which the effect will be visible; outside of this range, 
the user is left on his own... but may discover new things.

    In some cases, the value has to stay in range: but in these cases, 
it it the filter's responsibility to clamp the value properly; the user 
should still be able to pass any value. So I'd vote for proposition B.

    JS

Martin Bayer wrote:

> Hi,
>
> the spec of frei0r says that the allowed value range for a double 
> parameter is from 0.0 to 1.0.
>
> For many parameters it is possible to map the needed range in that 
> interval, but some parameters that aren't bounded by a upper and lower 
> limit.
>
> E.g. the video delay effect "delay0r" has a delay time parameter. It 
> isn't possible to find a sensible upper boundary for the delay time.
>
> There are some other frei0r plugins that accept values outside of that 
> valid range. The current gephex version interpret this range 
> specification only as a gui hint for sliders and doesn't enforce it in 
> any way. It is possible (and for some plugins necessary) to pass 
> values outside of the specified range.
>
> I think we must eliminate this discrepancy between spec and usage:
>
> Solution A:
>
> Keep the current specification (MUST be in the range) and add an 
> additional parameter type (f0r_param_unbounded_double) for unbounded 
> double values.
>
> Solution B:
>
> Change the range specification from "MUST be in the range" to "SHOULD 
> be in the range". And add adapt the existing frei0r plugins to clamp 
> the values to the [0,1] interval if other values are useless.
>
> Any comments?
>
> Martin
>
>------------------------------------------------------------------------
>
>_______________________________________________
>gephex-devel mailing list
>gephex-devel at lists.gephex.org
>http://lists.gephex.org/mailman/listinfo/gephex-devel
>  
>