traverso-devel
[Top][All Lists]
Advanced

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

[Traverso-devel] some observations


From: plutek-infinity
Subject: [Traverso-devel] some observations
Date: Wed, 28 Jan 2009 11:49:15 -0500

hi remon and the gang!

i've been playing with the latest cvs here, and was intending to
migrate an album project to traverso, just to see how far we can push
things in terms of productivity -- trying to do real work is a great
way to discover stuff about a piece of software. unfortunately, i
quickly ran into some stumbling blocks, some of which are fatal for
the way i work.

here are my findings:

*** lack of internal busses
*** lack of sends
*** lack of inserts
*** internal connections not exposed to jack

these all relate to my need to run convolution reverb (using
jconv). there is currently no way to route tracks to external
processes, like jconv, except through the master output bus, and no
way to return signals to tracks within traverso except through the
hardware i/o. this could be remedied by simply exposing ins/outs to
jack not only at the master bus level, but also for each track. that
way, we could use an empty track as a bus and/or we could send/return
signals arbitrarily to external jack processes.

or am i missing something?

*** lack of track automation

we have gain envelopes for clips, but we cannot automate gain or pan
at the track level. this means that if i have some clips with gain
envelopes in a track and i want to fade over the duration of all the
clips, there's no way to do it except to try to adjust all the gain
envelopes progressively lower. yes, we do have per-clip global gain,
independant of the envelope (which is very nice), but it is still
difficult to implement gain changes which span clips or don't correspond to 
clip boundaries.

*** lack of track gain grouping

say we have a group of instruments balanced against each other, and we
want to change the level *as a group*. this requires either track
grouping or routing through a submix bus, neither of which currently exist.

*** lack of plugin automation
*** can't choose pre/post fader for plugins

*** rubberband-box clip selection

it is currently very tedious to select large numbers of clips for a group.

*** split across all selected clips
*** drag ends of all selected clips

any plans to implement other functions besides move and delete, for
clip groups?

anyways, the improvements already implemented recently are a huge step
forward, so i don't mean to be negative! i just found that, when it
came down to doing actual work on a project, i couldn't yet do it in
traverso.

cheers... and keep up the great work!

-- 
.pltk.




reply via email to

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