Rayzoon Technologies LLC

[acabreira]

There´s one thing in JS 2 that I consider kind of a step backward, it´s about the automation. In JS 1, in Cubase, for example, when you added an automation track, every time you updated the curve you´d see the value field behind the parameter field updated with its meaning in JS. When you want to automate things like tom direction or snare ghosts, as you draw the curve you don´t know what you´re setting, unless you write down a table with the values. or have JS window open, but then it covers the arrangement space. It would be fine that parameters that use a different scale than 0 to 127, or at least those containing specific values rather than continuous ones used automation the old way. I find sort of strange power values that go from 10% to 127%. One or another case you might want to use the same controller for two or more parameters, but I think what you lose is not compensated by that, and you can even do it drawing inverted curves. For those like me that don´t edit in realtime, it´s a little bit messy.

[Ralph [RZ]]

I understand what you're saying but the main driver behind this is that the automation parameters change with the styles and drummers and VST automation can't hack that.
_________________
Ralph Zeuner
Rayzoon Technologies LLC
http://www.rayzoon.com

[acabreira]

Ah, I understand what you´re saying. Nevermind, I´ll get used to it

Thanks.