Re: Fwd: Re: [Traverso-devel] Thoughts on plugin strategy

[Remon]

Hi,

> >> I had a suggestion to let the layers be toggled on/off individually, so
> >> one can choose to see waveform only, waveform+pluginboxes,
> >> waveform+plugins+curves, or waveform+curves.
> >
> > Makes sense, and is what I have in mind, except the last one. A bunch of
> > curves on a wave form, it doesn' mean anything to the user, right ?
>
> I think it does! The user could want to align a change in the curve with
> a change in the audio, and seeing the waveform can help a lot (depending
> on what kind of audio it is...)

Ah now I understand. Point is of course, which curves do you want to be 
visible?
Btw, the audio waveform will _always_ be visible, and as pointed out by 
Nicola, it could be handy for gain/pan curve to be always 'slightly' visible 
in Edit Mode, perhaps that's what you mean too ?

> > Not sure what you mean here ?
> > If it is about the problem that [ D ] in effects mode potentially could
> > move clips, where you wanted to move an effect plugin, don't worry!
> > The key actions can be configured on a 'per mode' and 'per object' basis.
> > So, moving audioclips would only be possible in Edit Mode, and won't do
> > anything in Effect mode....
>
> Yes, I understand that. I was just thinking along the terms of layers
> instead of modes: that maybe one wouldn't need to have separate modes,
> but only toggles to enable/disable the different layers. which would
> mean that both clip and curve view could be active at the same time.

Ah, but Traverso works layered allready. Each item is 'stacked', and a key 
command is validated for use from top to bottom object.
So _all_ objects are _always_ active, that is, as long as the mouse is upon 
them.
However, my problem was that in a specific mode, certain actions should be 
ignored on certain objects. This has been solved  about a week ago, with an 
improved keymap.xml format and InputEngine handling :)


Greetings,

Remon