vvoois
(vV)
January 5, 2010, 9:56am
1
engine:
“Previous sequence position” ?
hmm, not here.
the value is copied from the sequnce that plays when dblclicking.
maybe i dont understand the term “sequnce position”.
you mean the sequence editor on the left?
make a automation with many nodes (best is randomize it).
open the automation editor and look at the automated parameter.
when renoise plays a pattern, in the automation editor is a small line (representation of the playcursor).
let renoise play the automated pattern in loop. look where the last node- position would be and
create a new pattern. open automation editor and doubleclick the parameter… cut and double click again.
do you see it?!
Yes sorry, i notice, i had to add more envelopes and nodes in all patterns to make that obvious and follow mode has to be turned off.
taktik
(taktik)
January 5, 2010, 10:10am
2
Yes, it gets the parameters !current! value. Thats the rule. I see that this does not always what you want in this case, but creating ramps over multiple patterns should probably be solved in another way?
vvoois
(vV)
January 5, 2010, 10:31am
3
taktik:
Yes, it gets the parameters !current! value. Thats the rule. I see that this does not always what you want in this case, but creating ramps over multiple patterns should probably be solved in another way?
If that’s the rule, then i should rectify it once more… (It is still a bug but on my side)
documentation
Creating ramps over multiple patterns more likely being solved easily with the script engine.
taktik
(taktik)
January 5, 2010, 11:28am
4
Well, I understand the problem. Also we don’t have scripting now, and scripts are not a general excuse not to change something.
I’ve changed this, so that it queries the last automation value, when present, else uses the parameters current value. Lets see if this makes things better…
vvoois
(vV)
January 5, 2010, 11:56am
5
taktik:
Well, I understand the problem. Also we don’t have scripting now, and scripts are not a general excuse not to change something.
I’ve changed this, so that it queries the last automation value, when present, else uses the parameters current value. Lets see if this makes things better…
Aha, nice… the documentation already had been adjusted