Regarding the Row probability issue

[OcttisTony]

Regarding the Row probability issue, 
the situation is this: 
for the current row, I have set FX1 track clock Div 2 and Fx2 prow to 0 probability, and for the next row, I have set FX1 to clock value Div 4 and Fx4 prow 64. It seems that the playback should be disabled with clock div 2, and then the next row should be played at the speed of clock div 4, right? Because the next row has been restored to active, but I found that it will still run with clock div2 until the next row, then it can respond to the track clock. 
I want to know, is this the principle of Tracker? 
Or do I have any settings wrong?
Thank you for any help.

[XORadmin]

Fx are executed from 1 to 4. In your case fx1 for the div4 is not executed and right after that the row probability is back to 100%. So the clock change didn’t happen but the rest of the row will play.

In general there is an order of playback (and that is not a tracker thing but general). The orders are listed on the end of the pattern screen descriptions.

[OcttisTony]

So here is my problem, because the row probability reset must be set in FX4 to exclude the row probability of zero, in other words, this cannot achieve what I want to do. I want to set the probability of the first row to zero when there are two rows with different clocks, and immediately reset the probability of the second row and run second row's own FX CBPB clock. That’.


One more thing to add, I realized that the problem is that we don’t have music step probability (cv/note + trigger). I thought of many ways, but still failed to achieve my idea. It should be that I don’t understand the function of nerdseq. But I thought of some solutions, such as a source map, cv note + trigger, but if both are not at 0 or 64 probability, misaligned triggering will occur. If I simply use auto trigger, I will lose the different trigger values I set in steps. I am really distressed, because the music step probability I mentioned can be excluded from the FX column. Indeed, if the clock is often changed in FX, this is obviously a fatal point. Why do we only want the probability of music steps, but lose the entire row of FX, patch and table functions at the same time?

Thanks for your help.

---

This happened so suddenly. I tried using xmap 2xx and it turned out that I could exclude the row fx clock from the row probability. It was amazing. I want to cheer for your great invention. I obviously didn't understand why it could be excluded. I just kept trying. Now I can disable steps with row probability without affecting the step clock!

[OcttisTony]

The situation has changed again. Although I can now get a row probability switch that does not affect the FX clock, I cannot adjust the row probability value. The method I thought of is to use mapping to set a few probabilities that I like to use in variable storage locations. This method will work, but it feels really clumsy and will occupy a certain proportion of variables. The key point is that it still cannot be excluded from the step's fx clock. I have also tried various mapping methods and still failed. I can't figure out why only using a row probability x map without a source can exclude it from the clock. Why? I'm also wondering if you could put the condition for the PROW 64 probability reset on FX1? Or is it simply (just my opinion) to add the probability of musical steps?

[XORadmin]

The situation has changed again. Although I can now get a row probability switch that does not affect the FX clock, I cannot adjust the row probability value. The method I thought of is to use mapping to set a few probabilities that I like to use in variable storage locations. This method will work, but it feels really clumsy and will occupy a certain proportion of variables. The key point is that it still cannot be excluded from the step's fx clock. I have also tried various mapping methods and still failed. I can't figure out why only using a row probability x map without a source can exclude it from the clock. Why? I'm also wondering if you could put the condition for the PROW 64 probability reset on FX1? Or is it simply (just my opinion) to add the probability of musical steps?

I think the definition of musical steps is a bit the problem. For some it is the Note+Gate. But it could also be 2x note and gate or only the notes while the gates are independend. It's a bit tricky.

As for your mapping. You would need to show it to me so I can see what is going on.

Maybe it's worth to take also a look into the conditional execution

[OcttisTony]

This is my mapping for CV + Trigger probability

00 TRCK TR 6
01 CALC T&H 00-02 > CV NOTE CV 6
02 TRCK TRK6 NOT1

My idea is this. My example is TR6. I hope to use Trigger to trigger Track and Hold, so that I can control the note probability at the trigger to trigger a new note only when the law is triggered, and keep the previous note when the law is not triggered, and then send it to CV6. I don't know why it still can't succeed. Is my idea wrong?

Why would I want to do this? As I have found, row probability works very well most of the time, but the problem is that it will absolutely disable the entire row, which is a problem because a lot of FX stuff is not based on adjusting sound content, and if I have time-based stuff in FX, and I disable the entire row, everything will fail. I can't believe how difficult it is to achieve step-based muting, rather than the entire row.