Just some minor suggestions (since you asked for it O:-) ):
LOL
- The clip editor is cool, but I think the spin boxes should go down
to sub-second precision (milliseconds or sec:frames), otherwise it is
impossible to set the clip to it's full length using the spin box
(unless it happens to be a round number).
Yeah, I think so too, but I had some problems making it work... Will look into adding msec support or frames, needs to think a bit about it.
- How about a read-only field showing the end position of the clip
(calculated from start and length) in the clip editor?
Anyone ?
- I would swap the entries 'length' and 'start' in the clip editor.
The order 'start', 'length', ('end') would be more intuitive IMO.
OK, I purposly did it this way, but if you think that the other way around is more intuitive, sure
- Default values for fade strength and bending are (still?) wrong.
The values should be:
Fade-in: strength = 0.5, bending = 0.0
Fade-out: strength = 0.5, bending = 1.0
I tried to fix it, but I didn't succeed. Initializing m_bendFactor
and m_strengthFactor in core/FadeCurve.cpp with these values didn't
change anything. (Maybe we should also use bending = 1-bending to
display the fade-out bending value.)
A fade shape (fast) is set as default, with mode long now. perhaps that is something we shouldn't do (setting the default shape) so the bend/strength values will be honored (now they get overwritten with setting the shape)
P.S. I just noticed that the dialog warning when the project was
renamed sometimes pops up for no reason. I can't provoke it, it just
happens about every 2nd time I start Traverso (on OS X, with a newly
created project).
Too bad... Seems the filewatcher emits signals for no reason ?
Hmm, maybe it should be disabled for
0.41 until we find out how to make it work more robust then.
P.P.S. I will add a section about external processing to the manual.
This seems to be a powerful feature that should be mentioned in the
documentation.
OK, great!
Regards,
Remon