I have a simple 16 step sequence with eight notes running up a scale (C D E F G A B C). Each row has a trigger setting of 40 and I have auto-gating turned off. I am triggering a Qu-Bit Surface and there are no other parameters on the sequencer rows.
When I add PROW in the fourth FX column for each row that has a note/trigger and put in percentages that are lower than 100, my expectation was that the that entire row would either fire or not (i.e. I would get a CV change and trigger or neither). The actual behavior is that I will sometimes get a CV change without a trigger or a trigger without a CV change. When I remove the triggers and turn on the auto-gating, I still get CV changes without a trigger (but not a trigger without a CV change). Firmware is 1.27C.
Is this the expected behavior of PROW?
(06-22-2023, 12:11 PM)sllopes Wrote: [ -> ]I have a simple 16 step sequence with eight notes running up a scale (C D E F G A B C). Each row has a trigger setting of 40 and I have auto-gating turned off. I am triggering a Qu-Bit Surface and there are no other parameters on the sequencer rows.
When I add PROW in the fourth FX column for each row that has a note/trigger and put in percentages that are lower than 100, my expectation was that the that entire row would either fire or not (i.e. I would get a CV change and trigger or neither). The actual behavior is that I will sometimes get a CV change without a trigger or a trigger without a CV change. When I remove the triggers and turn on the auto-gating, I still get CV changes without a trigger (but not a trigger without a CV change). Firmware is 1.27C.
Is this the expected behavior of PROW?
No, PROW does indeed fire the whole row or not. I am pretty sure that you got another probability still activated here (check in the current values screen of the track). Also you set the probability on one step and set it to another value on another step. It stays on it's value until you change it again.
No other probability settings. I've checked the current value screen while the sequence is running and the CV and trigger probabilities stay at 64. If there is some other probability affecting them, I cannot locate where that is happening.
I understand the value of the PROW will remain until changed, but that is not my concern. My issue is that it seems like the probability values are being rolled independently for CV and triggers (and my guess would be the other parameter on the row) with PROW. That is the behavior I am experiencing.
Here is a project file:
https://drive.google.com/file/d/16WjoK-E...sp=sharing
Hey thanks for the Project and I got to confirm your issue!
Just checked in the code and indeed for some reason this happens cause of an incorrect check. Strange that it hasn't been reported before since it always has been like this with the row probability.
Will be fixed in the next version!
Thank you so much! I thought I had to be doing something wrong or just didn't have the right understanding (hence the thread title) since, like you said, I didn't see it being reported and it's been out for so long. Really appreciate you looking into it!