+- XOR Userforum (https://forum.xor.eu)
+-- Forum: Products (https://forum.xor.eu/forumdisplay.php?fid=3)
+--- Forum: NerdSEQ (https://forum.xor.eu/forumdisplay.php?fid=6)
+---- Forum: General Questions (https://forum.xor.eu/forumdisplay.php?fid=17)
+---- Thread: Row probability strange behaviour (/showthread.php?tid=968)
Row probability strange behaviour - jlamores - 01-17-2021
Let's say I have a pattern with 64 steps. I set a Row probabilty value of 34 for step 14, and in step 15 I set the row probability to 64 (the maximum value).
I don't know why, but sometimes the sequencer doesn't read the probabilty of step 15 and continues to the end of the pattern with value 34.
What's happening?
I don't have any other FX used in this pattern.
RE: Row probability strange behaviour - XORadmin - 01-17-2021
Yes this is the correct behaviour. The probability is also for the step 15 and it is for sure possible that it is indeed not processed caused by the probability.
The row probability is for the whole row generally. But there is always the last FX column excluded to be sure settings can always be changed. So for a modular track FX 4 will always process and excluded from the row probability.
RE: Row probability strange behaviour - jlamores - 01-17-2021
So using FX4 for Row probability is always best to obtain the expected results.
Thanks. I knew there had to be something I was not considering. :-) More than happy with my new Nerdseq.
RE: Row probability strange behaviour - XORadmin - 01-18-2021
(01-17-2021, 03:07 PM)jlamores Wrote: So using FX4 for Row probability is always best to obtain the expected results.
Thanks. I knew there had to be something I was not considering. :-) More than happy with my new Nerdseq.
Sure. Even most important if you have a row probability with a very low percentage. Because else you wouldn't be able to reset this again except through the current values screen. Of course it is also wanted that it is like this because then one can have also random kind of probability settings.
RE: Row probability strange behaviour - grib - 01-19-2021
So is this a way to have more than 4 FX on a row? for subsequent rows set PR = 0 and FX4 to some additional effect? Would the extra FX be evaluated in row order, after the last FX on the non-PR0 row?
I don't necessarily think that would be super useful but good to file it away just in case
RE: Row probability strange behaviour - XORadmin - 01-20-2021
(01-19-2021, 10:16 PM)grib Wrote: So is this a way to have more than 4 FX on a row? for subsequent rows set PR = 0 and FX4 to some additional effect? Would the extra FX be evaluated in row order, after the last FX on the non-PR0 row?
I don't necessarily think that would be super useful but good to file it away just in case
I don't know what you mean exactly? There is only as many FX in a track row available than the tracktype and in this case for a modular track these are 4.
The discussion here is about the probability setting for a whole row.
RE: Row probability strange behaviour - grib - 01-21-2021
Ah, sorry. I hadn't experimented with PROW and I thought it behaved differently. I thought if PROW was 0 it would actually skip the row (so that the row pointer would not stay on it for a clock pulse but just immediately go to the following step).
When I set up a test pattern to verify this, I found that the clock pointer still stays on the row for a pulse, but the contents of the row (except for FX4) are treated as a noop.
RE: Row probability strange behaviour - XORadmin - 01-21-2021
(01-21-2021, 01:57 PM)grib Wrote: Ah, sorry. I hadn't experimented with PROW and I thought it behaved differently. I thought if PROW was 0 it would actually skip the row (so that the row pointer would not stay on it for a clock pulse but just immediately go to the following step).
When I set up a test pattern to verify this, I found that the clock pointer still stays on the row for a pulse, but the contents of the row (except for FX4) are treated as a noop.
Exactly. Row probability. These never 'jump'.
