How Events Work
The “Rndmz note” event, like all events that modify pattern values, changes the value of note
dynamically .
The stored value in the pattern is not changed.
When a pattern step with the “Rndmz note” event enabled is played, the following happens inside P3 :
1. the note value is read from the pattern
2. the gate status is read from the pattern
3. the aux A value is read from the pattern
4. because aux A is assigned to “Rndmz note”, P3 generates a random number between zero and
the stored value for aux A, and this random number is added to the note value
5. if gate is on, the note is sent
Some extra steps are not described there to keep it simple – obviously the velocity, length, and so on
are also read from the pattern, but you should get the idea.
You can enable and set a different value for aux A on whichever steps you like, and a different random
number will be generated and added to note on each step.
Try setting aux A on some other steps – some with a small value of only 1 or 2, others with larger
values.
You will hear the different amounts of random variation on each of the steps you modify as the pattern
plays.
It may seem a little uncontrolled, and indeed, out of tune.
This is once place you might find the Force-To-Scale feature useful – you can randomize note values,
but use FTS to ensure they play in key.
Random Masks
There are events like “Rndmz note” for each of the other numeric pattern values – velocity, length,
delay and auxes B, C and D.
All will add a random number between 0 and the aux value to the chosen pattern value.
For the status values, gate, tie, Xd and the aux enables, the randomize events are a little different.
To Next Page
Loading...
