Probability Functions Changed?

[XORadmin]

Ah yes thank you!

In the first place i thought that this is not good and a bug.
But then i tried myself and playing around with it and some logic i know it is correct! Nothing really wrong here.

So what happens:
You have notes filled in here! The Probability for the trigger only looks at the trigger column and doesn't care about the Note column and so the other way around. What happens here: The Probability for the trigger is indeed turned on when you turn it on. When the trigger plays, all is fine, it was not a probability situation. Also the next trigger below just plays as it should be.

If the first trigger (from the trigger column!!!) doesn't play cause of the probability, then the gate is still being set because of the note autogate function!!!
So the trigger which then always plays is then either a trigger from the trigger column or if the probability happened a gate from the note column.
And if the gate was set, then of course the new note and trigger below doesn't take effect, because the gate was already on! So the probability is already off again, but no effect because you change from a gate set to also a set situation.

You can either include a Kill000 on the step where the probability is or remove the note and all will be fine.
Also, you can turn the probability also on the same step on where you want the probability to take effect, no need to turn it on one before.

I have to say that this is worth a discussion if this makes sense or not. The probabilitys are especially for columns only. And the trigger column is in the most cases seperated from the note column. I remember the idea that either the Kill000 or if something is filled in in the trigger column should always overrule the autogate. But it is not implemented yet for the trigger.
I will start a poll if this should be the general behaviour or not....

Thanks for the report.