3 Mar
2003
3 Mar
'03
11:17 a.m.
i like the recently suggested new hints. i'd like to add the
following, which would allow hosts to do the right thing with
both SooperLooper and SC4, which are the first (only?) LADSPA plugins
to have control output ports, but use them in very different ways. its
almost impossible as it stands to build a GUI for them both that does
them justice.
--p
/* Hint LADSPA_HINT_OUTPUT_METER indicates that the value of output
control port is likely to be most meaningful to the user if
displayed as a meter. Can be combined with LADSPA_HINT_LOGARITHMIC
if the meter should use a log scale (e.g. dB).
*/
#define LADSPA_HINT_OUTPUT_METER 0x??
/* Hint LADSPA_HINT_OUTPUT_VALUE indicates that the value of output
control port is likely to be most meaningful to the user if
displayed as some kind of numeric value display.
*/
#define LADSPA_HINT_OUTPUT_VALUE 0x??
3 Mar
3 Mar
3:36 p.m.
On Mon, Mar 03, 2003 at 10:12:14 -0500, Paul Davis wrote:
/* Hint LADSPA_HINT_OUTPUT_METER indicates that the
value of output
control port is likely to be most meaningful to the user if
displayed as a meter. Can be combined with LADSPA_HINT_LOGARITHMIC
if the meter should use a log scale (e.g. dB).
*/
I dont like the wording of this, if the scale is dB's then it should
output dB's, I see what youre getting at, I just think is ambiguous.
- Steve
4 Mar
4 Mar
11:01 a.m.
On Mon, Mar 03, 2003 at 10:12:14 -0500, Paul Davis
wrote:
i agree. i didn't like the wording either. can we do better?
/* Hint LADSPA_HINT_OUTPUT_METER indicates that
the value of output
control port is likely to be most meaningful to the user if
displayed as a meter. Can be combined with LADSPA_HINT_LOGARITHMIC
if the meter should use a log scale (e.g. dB).
*/
I dont like the wording of this, if the scale is dB's then it should
output dB's, I see what youre getting at, I just think is ambiguous.
11:25 a.m.
On Tue, Mar 04, 2003 at 09:56:36AM -0500, Paul Davis wrote:
How about:
... Can be combined with LADSPA_HINT_LOGARITHMIC if the meter would be
more usefully rendered with a log scale, eg. to show a frequency.
not really clearer, but it aviods the dB example.
- Steve
On Mon, Mar 03,
2003 at 10:12:14 -0500, Paul Davis wrote:
i agree. i didn't like the wording either. can we do better? /* Hint LADSPA_HINT_OUTPUT_METER indicates that
the value of output
control port is likely to be most meaningful to the user if
displayed as a meter. Can be combined with LADSPA_HINT_LOGARITHMIC
if the meter should use a log scale (e.g. dB).
*/
I dont like the wording of this, if the scale is dB's then it should
output dB's, I see what youre getting at, I just think is ambiguous. 
3 Mar
3 Mar
3:52 p.m.
On Mon, 3 Mar 2003 10:12:14 -0500
Paul Davis <paul(a)linuxaudiosystems.com> wrote:
i like the recently suggested new hints. i'd like
to add the
following, which would allow hosts to do the right thing with
both SooperLooper and SC4, which are the first (only?) LADSPA plugins
to have control output ports,
The sum, product and branch plugins in 'blop' have control outs, too.
They're trivial though, and their purpose isn't the same - they're
pretty useless on their own.
but use them in very different ways. its
almost impossible as it stands to build a GUI for them both that does
them justice.
METER hint: Is this the same idea as the informative/data port
distinction that Steve mentioned? I'm starting to see the need for this
for similar reasons as for the CONTINUOUS_CONTROL hint (improved
automation). I've not used Ardour, though (don't have the need or the
hardware, yet :), so I'm not sure what it does with control-out ports
right now.
-
Mike
__________________________________________________
Do You Yahoo!?
Everything you'll ever need on one web page
from News and Sport to Email and Music Charts
http://uk.my.yahoo.com
10:44 p.m.
On Mon, 2003-03-03 at 10:12, Paul Davis wrote:
/* Hint LADSPA_HINT_OUTPUT_METER indicates that the
value of output
control port is likely to be most meaningful to the user if
displayed as a meter. Can be combined with LADSPA_HINT_LOGARITHMIC
if the meter should use a log scale (e.g. dB).
*/
#define LADSPA_HINT_OUTPUT_METER 0x??
/* Hint LADSPA_HINT_OUTPUT_VALUE indicates that the value of output
control port is likely to be most meaningful to the user if
displayed as some kind of numeric value display.
*/
#define LADSPA_HINT_OUTPUT_VALUE 0x??
Why have both? Couldn't the absence of one imply the presence of the
other? And if there are both, it also implies that there are third and
forth states of both and neither.
Taybin
4 Mar
4 Mar
5:08 a.m.
On Mon, Mar 03, 2003 at 09:36:09 -0500, Taybin wrote:
Why have both? Couldn't the absence of one imply
the presence of the
other? And if there are both, it also implies that there are third and
forth states of both and neither.
I think there is meter and/or text (ie. both if ou support both) makes
sense, and neither, ie. this isn;t menat to be rendered.
- Steve
10:38 a.m.
On Mon, Mar 03, 2003 at 09:36:09 -0500, Taybin wrote:
i don't think that both makes sense. i agree with taybin that just
"meter" or "value" as a flag will do. the underlying difference, i
suspect, will be between output control ports that are computing
"meter-like" values internally, and those that just show some kind of
state.
Why have both? Couldn't the absence of one
imply the presence of the
other? And if there are both, it also implies that there are third and
forth states of both and neither.
I think there is meter and/or text (ie. both if ou support both) makes
sense, and neither, ie. this isn;t menat to be rendered.
8089
days inactive
8090
days old
linux-audio-dev@lists.linuxaudio.org
7 comments
4 participants
participants (4)
-
Mike Rawes -
Paul Davis -
Steve Harris -
Taybin