Re: [Traverso-devel] Reports about latest CVS

[Remon]

Hi,

> > Just in case, not a cursor that stays there all the time, only a small
> > helper during [ X ]
>
> Just tried it, and sure it's much better!

Yeah, I figured, let's just implement it, then we really know if it it's gonna 
work out or not, and I love it too! :D

> Also, I just got an idea: What about a special double-edge drag action,
> [ E R ] or something like that, that moves not only the clip-edge at the
> cursor but also the edge of the other clip. That is, if the edge pointed
> at was one clips end-edge, then also move the next clips start-edge, and
> vice versa. In this way, it's really easy to adjust a cut position if
> you didn't get it right the first time! I think it would be quite cool
> feature, and rather easy to implement I guess?

Good one, realized it just yesterday that this would be extremely handy!

> I have now tried the latest CVS, and here's some reports:
>
> * fade outs doesn't show in the actual waveform, as fade ins do.

Yes, known problem, but thanks for reminding 

> * Song gain isn't displayed anywhere so you don't know what gain the
> song currently has. There could be a display of it in the VU-meter box,
> perhaps?

Yeah, I know. Not sure where to display it yet. VU-meter (playback 1) should 
be the one then, but no-one expects it there ?
Needs some more thought...

What I have in mind is a special 'overview' track, which displays the whole 
song, rather common in daw, right ?
It gives us an area where Song is the first 'context item', and the 'panel' 
could display gain, pan for the Song, which equals effects for 'master out'
It also gives the opportunity to easily add plugins to master out.


> * Is 'selections' gone?

Selections was only used for removing Clips, and there is << R >> for clips 
now too.
So, since selections didn't serve a (real) purpose anymore, and has some 
problem, we figured, disabling it for now is the better option.

> * It would be nice with a normalize toggle when exporting, so that the
> full 32 bits are used while normalizing, instead of having to normalize
> the resulting 16 bit file afterwards. One could then also easy implement
> a "check for clipping" feature.

I'm a little confused, you mean calculate the normalize factor for exported 
audio, and write that the the wav header ?

> * When selecting "remove node" in the popup-menu with the mouse when in
> Effects mode, the clip is removed instead of the curve-node!

Hah, that one is for Ben!


Please, add the feature requests to the bug tracker on savannah, so they don't 
get lost!

https://savannah.nongnu.org/bugs/?func=additem&group=traverso

Thanks for the report!

If you do happen to have some time for the theme you had in mind, now is still 
the time to get it included!

Greetings,

Remon