Recording fader movements to automation problem
Posted: Thu Jul 28, 2016 7:46 pm
I have noticed that when recording fader movements to automation, the movements are recorded alright on the first pass (albeit with some latency, which is to be expected on android). However, on the second third etc. passes the movements do not "overdub" properly, that is to say the movements from the second or third pass of recording will be mixed with the movements from the first pass rather than overwrite them.
This results in the fader jumping all over the place.
Its not just a problem in GStomper, Ive noticed that renoise also has this problem..
Ive been using LFOs more these days because the results sounds smoother than the live fader movements recordings.
Maybe it would be good for GSTOMPER VABeast to have a graphical automation lane than could be opened for each fader, various curves, liner, points, cubic interpolation available etc.
This results in the fader jumping all over the place.
Its not just a problem in GStomper, Ive noticed that renoise also has this problem..
Ive been using LFOs more these days because the results sounds smoother than the live fader movements recordings.
Maybe it would be good for GSTOMPER VABeast to have a graphical automation lane than could be opened for each fader, various curves, liner, points, cubic interpolation available etc.