Rayzoon Technologies LLC

[ECC83]

Hi,

I'm having problems automating per-rhythm variables (as opposed to, say, global parameters like velocity, which works fine)

I'm finding that I have to use continuously varying automation data (eg, using the sine draw tool) in order to ensure that parameter values are preserved across a rhythm change.

Is this correct?

Cheers
ECC83

[Ralph [RZ]]

What parameter are you talking about specifically?
_________________
Ralph Zeuner
Rayzoon Technologies LLC
http://www.rayzoon.com

[ECC83]

As an example, say "cymbal chance (power play)"

Lets say I have an 8 bar section, with four patterns, repeating twice, ie ABCDABCD

I want the cymbal % to be 0% for the 1st 4 bars, 100% for 2nd 4 bars

I have it set at 0% for each pattern in the rhythm editor.

If I draw a simple line automation envelope in SX, set at 0 for bars 1-4 and then 100% for bars 5-8, then what will happen is that the parameter (in this case cymbal %) will switch to 100% for bar 5, and then back to 0% in bar 6, when the pattern changes to B, since the value in the pattern is 0%

If I use contiuously varying automation, then I get the results I expect. Thinking about the way the parameters work within different rhythms, this sort of makes sense - but it does make creating the automation tracks a little messy!

I've also tried this on the "always ride" parameter, with the same result.

For global parameters, such as velocity, mutes, etc, I have had no problems.

[Ralph [RZ]]

Yes, parameters that are in the rhythms themselves will be set to those values when the rhythm changes. There just is no other way. It would be even messier if Jamstix had to track past automation values and then somehow make an assumption if you want to switch the values or not. An ini switch would be a solution but again it just makes JS more complex.

I think adding nodes to the envelope is the best solution for now.
_________________
Ralph Zeuner
Rayzoon Technologies LLC
http://www.rayzoon.com

[ECC83]

Thanks Ralph!