> > Hmm, you never used Traverso I see ... at least not in the way it should
Understandable... we're open for suggestions and bug reports about those
issues of course!
> > But you are correct that the pan/gain 'indicators' have less precision
OK, makes sense. I'll stick with gain in/decrement steps then of 0.1 dB.
T at the moment doesn't smooth transitions of gain/pan values when the user
changes those when transport rolls.
is this much of an issue ?
Keep in mind that gain automation uses an interpolation for the gain value
calculated and applied per sample.
> > Right now gain increment steps are 0.05 dB for gain, and there are 200
yes, 201 positions, 100 steps in both directions and the central (zero)
If this kind of precision isn't needed, then I can change that to use the same
resolution as midi (128 steps) or perhaps a multiple of 128?
> > The use of sliders vs knobs in software imho still is a different issue
How do you move sliders with a mouse with sub-pixel accuracy ?
(maybe I'm misunderstanding the sub-pixel accuracy way of moving a graphical
Thing is that the 'pan/gain slider' in Traverso isn't used for changing that
value, instead you just 'activate' the 'change pan' key and then move the
mouse. The distance of the mouse movement is calculated with respect the 'old
mouse position' and from that value the pan/gain change is calculated and
For pan you keep the P key pressed and move the mouse, the whole track is
sensitive for that key. Similar for Gain, then you have to use the G key.
To please some stubborn users that insist on trying to click with the mouse on
that damn tiny pan/gain slider, it was added as a 'key action for pan/gain'
too, but it's considered bad practise :)
This 'virtual' slider equals a size of 600 pixels in Traverso, but is easily
changed into any value you want. So to pan hard left you have to move the
mouse 300 pixels to the left, and vice versa.
Linux-audio-dev mailing list