7 Feb
2003
7 Feb
'03
9:20 a.m.
On Friday 07 February 2003 10.19, Tim Hockin wrote:
This is to avoid having later "extended" versions of plugins that just
let you use a wider range for some parameters. Many algoritms
generate interesting results with parameters outside the ranges that
may seem logical at first.
Hard ranges tell hosts and users that the plugin is expected to blow
up or crash if you give it values outside the range. A soft range
basically means "The author didn't think values outside this range
were very interesting, but they won't make Bad Things happen."
If we allow
hard ranges (not really neccesary, as LADSPA shows)
then the host should enforce them.
Remind me why we want soft ranges? I'm more of the mind that all
ranges are hard ranges, except for {pos/neg} infinity.
If a control is going to the effort of specifying a range, don't we
want to respect it ALWAYS.
A soft range is a *hint* as to the range in which you'll probably find
the most interesting/useful settings. With only hard ranges and
infinite ranges, you'll have to assume that useful values are in the
[0, 1] range, or whatever - which might work as well, of course.
//David Olofson - Programmer, Composer, Open Source Advocate
.- The Return of Audiality! --------------------------------.
| Free/Open Source Audio Engine for use in Games or Studio. |
| RT and off-line synth. Scripting. Sample accurate timing. |
`---------------------------> http://olofson.net/audiality -'
--- http://olofson.net --- http://www.reologica.se ---