trig conditions TRC are brilliant, like 8:8 and 6:8 etc…
no other people are doing that like Elektron, they have percentage chance thats cool but not like TRC… when you are dancing in a club or even just listening at home you always count in your mind this naturally.
i would love to see negative TRC like fill and neighbor for 8:8 etc…
anyone else have realistic creative ideas?
TRC is a signature elektron thing,
having oppisite TRC would be awesome i know the work around and use it often but it wastes trigs. some type of note trc would be game changing on the note page too, it needs to work as simply as trc though
There’s a handful of things out there that do it, and the reason why I nagged about adding the modulo mode in the first place was because I loved using it in nanoloop
(And nanoloop has the inverse too, which I’ve always missed dearly on the Elektron)
I hope Elektron expands upon the idea though, I always wanted to see a second page added for Trig that would break up the logic and probability to allow for more options and layers to the behaviors.
OP-Z does it in a very clever way where you can stack the logic etc, really cool sequencer but it gets a bit fiddly without the screen.
i do have a trap beat bopping right now that i made on the digitakt
that is all mostly chance and it sounds good and it doesnt ever repeat.
though still love trc much more and think is a better concept
Note conditions would make me so happy. For instance, put down up to four notes on a single trig, then set a percentage for each of those notes being chosen monophonically (50% C2, 20% F2, 20% G2, 10% C3), with the main/regular TRC determining whether or not ANY of those notes fire on that step. If Elektron can implement this whilst being locked to a scale and reacting to transpose commands, even better.
same but it has to be easy to use
reeloys conditions on conditions is enough for me to think about it for a while - 1:3 + 1 :2 =selected note or it equals the original note…
does that make sense? on the first of 2 times out of the 1 in 3 times the note plays it will be the chosen note
knowing how the TRCs are logged/implemented within the devices/sysex I can honestly say I do not see this changing from a binary either On/Off Trig thing … it was one of my first thoughts (ooh, different notes, gonna suggest that) when testing these before they dropped, but a dev soon extinguished any hope of that idea
for sure they could redo the whole concept, so it’s not quite ‘OB for OT?’ level impossible, but I’d temper any excitement about this ever changing by confirming that it’s not as simple to change/implement from the current approach as it is to dream of the possibilities (although seemingly conceptually easy)
No harm chatting about it either, but maybe don’t hold your breath