On Fri, 10 Mar 2000, Alexander König wrote:
> Without knowing the value range I cannot proivde any useful GUI to the
> plugin. Or if I could and just don't know how, someone tell me please :)
I don't understand how this became a GUI discussion. If you don't
know anything about the possible range of a control port, how can you
use it? As floats are not normalized to any specific value range, this
is even a bigger problem. I might want to control a plugin port with
a joystick, oscillators, GUI-knob, whatever... in every case, I need
to know the possible range.
Btw; Having a "toggle" port would also be useful.
> Every control port could have one of these:
[...]
> struct PortValueHints
> {
> float MinValue;
> float MaxValue;
Determinating these is suprisingly difficult. What's the MaxValue
of an amplifier plugin? With my own API, I decided to replace these
with "default_range(A,B)" (not absolute limits, but default min and
max values) and "is_valid(A)".
> float DefaultValue;
This is good to have.
> float ValueStep;
Hmm, not so sure about this, but might be useful.
> same as without. If the app cares it can try to provide some useful
> automatically generated GUI for the plugin if it wants to.
Or MIDI-CC control, oscillators, pitch->control_data, joystick, mouse,
..., this is definitely not GUI-specific.
--
Kai Vehmanen <[EMAIL PROTECTED]> -------- CS, University of Turku, Finland
. http://www.wakkanet.fi/ecasound/ - linux multitrack audio processing
. http://www.wakkanet.fi/sculpscape/ - ambient-idm-rock-... mp3/ra/wav
