traverso-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Traverso-devel] Curves (aka envelopes?)


From: Jonatan Liljedahl
Subject: Re: [Traverso-devel] Curves (aka envelopes?)
Date: Fri, 26 Jan 2007 12:47:55 +0100
User-agent: Thunderbird 1.5 (X11/20051025)

Hi there Remon!

Remon wrote:
> Hi again,
> 
> I knew I forgot at least one thing to throw into the wild:
> 
> Curve support, or like it's called, envelopes is functional, and since 2 
> days, 
> real time thread save, without locks, which took a bit time to get right :-)
> (or in other words, up till now the curve had some quirks which could result 
> in either bogus on screen or in your headphones hehe)
> 
> < F2 > to switch to CurveMode < F1 > back to Edit Mode.
> 
> (ehm, I think I've asked this more or less before btw?)
> 
> Anyway, when going into CurveMode, what do you like to see right now?
> 
> A Gain curve created by default? Also one for Pan? Any other kind of curve ?
> How to select the 'active' Curve?
> 
> If no curve should be created by default, how to add the one of your choice ?

Just press a key to add a new curve, which brings up a menu to assign
the curve to a specific parameter (gain, pan, or any of the tracks
plugins control inputs).
The menu could perhaps also be accessible also after the curve is
created (another key press) if one would like to reassign it to another
parameter.. But it would probably also be OK if one curve is bound to a
specific parameter, so that the user does "Add curve for filter1
resonance control" and that's it.

> I would like to point out the way I have in mind for Plugins, the plugins for 
> a Track/AudioClip will be diplayed more or less like in [1]
> (sorry, the only lv2 plugin I have that works is the simple amplifier, but 
> one 
> can get the idea, no?)
> 
> I've something similar in mind for Curves. By doing so, they can share the 
> same code for organizing, placement, moving the order (doesn't make sense for 
> curves maybe?), and so on, this would apply for the gui code.
> By making it a Plugin, one can use the bypass feature, and anything else that 
> a Plugin offers, anyone on this one ?
> 
> Looking forward to your comments,

I'm not sure I understand this. As I see it, plugins are something very
different from curves. Plugins displays as boxes in a specific order,
with ability to open properties dialog for each plugin where one can set
constant values for all it's control inputs, etc...
Curves displays as curves :) and each curve can be assigned to gain, pan
or a control input for _any_ of the tracks plugins.

Say for example that you add a filter plugin and a delay plugin, then
the user could create 3 curves to control gain, the filters cutoff
frequency, and the delays delay-time. _or_ the user would not want to
control the delay-time but set it to a constant value, which would be
done in the properties dialog for that instance of the delay plugin.
(it could work like this: if a curve exists for that control input, then
ignore the constant value set in the props dialog (shade it out to show
that it's ignored)).

An idea: perhaps the gain and pan should also be implemented as plugins?
either "built-in" plugins that appears as ordinary plugins, or actual
lv2 plugins. This way one automagically have the ability to change
pre/post-fader operation of plugins by reorder them (for example, one
might want a compressor plugin _before_ the gain, and a reverb _after_
the gain: [compressor]->[gain]->[reverb])

Something to also keep in mind is that one might have multiple instances
of the same plugin on the same track, then they should be named like
"gain1" and "gain2", so that one knows which is which when assigning
curves to control inputs.

Have a nice day!
-- 
/Jonatan - http://kymatica.com




reply via email to

[Prev in Thread] Current Thread [Next in Thread]