.I think that we don’t speak about the same thing (or my english is worst than I thought !).
I don’t speak about the values that must be sent BEFORE the recording starts, but about the values that ARE recorded and that doesn’t follow the knob movements at the begining.
Look at this :
In the first curve it must be a linear movement from 50 to 100.
Result : it begins by 0, jumps very fast to the good value and starts to record the following ones, but after 1/4 of second it jumps to the min value (the knob too !) and I have to continue the gesture from the “new” value.
The two other curves come from another plugin (RaySpace) which has a very slow GUI refresh rate. The values must have gone from top to bottom for the first one, and must have started about 80 for the second.
Result : the two curves are wrong and I have to redraw them by hand.
With plugins which have no GUI or when it is very simple, it is less annoying, because we get only the first jump from the default value to the current value (like at the begining of the first curve).
—
Concerning which values must be sent between curve sequences, it is another storry.
My preference, as I have told you one year or two, is to keep the last previous value in the same track, like with MIDI in standard sequencers.
The best would have to have an option :
– use default value
– use last previous value on track
– use current plugin value
It is always the best when the user have the choice 😉
