Yeah, this is a cool idea. Here’s another way to do it - not necessarily the “best”, just depends on what you want to accomplish. Should work essentially the same with the added benefit that it will always play “one or the other” trig, never both, so no overlapping, can use different sounds if you want.
Let’s say for the sake of this example your retrig is “on the beat”.
Put a trig before the beat, but microtime it to fall “on the beat”. Put a conditional value on this one instead of the retrig.
Now put a trig “on the beat” and make this your retrig, but make the condition “NOT PRE”.
If you’re using random chance as your condition then all you have to do is make the “non-retrig” version ( the first trig) be the inverse random chance. Like if you want your retrig to have a 33% chance of firing, then put the non-retrig chance at 66%.
The only downside I think to this way is when using set conditions like 2:4, 3:3, etc. there might be some wonkiness depending on how you want it to work out. For example if you want the “retrig” to trigger on ONLY 1:4. Since you’re putting your condition on the first non-retrig, you can’t really do this, because it would result in: first non-retrig firing at 1:4, retrig version firing at 2:4, 3:4, and 4:4… if that makes sense… but what you might want is the opposite
Workaround in this particular case would be to add ANOTHER trig before the “non-retrig”. Make this new one a “trigless trig” (yellow), set IT to whatever condition you want to happen for the RETRIG note… then set the NON-RETIG note to “NOT PRE”, and set the RETRIG note to “PRE”.
Yeah confusing as hell, LOL… but definitely cool stuff to explore 