not holding my breath just trying to bring creative ideas to the table…
im happy with how my Elektron groove boxes are at the moment anything else is a bonus!
Hmm, maybe to keep things as simple as possible, keep the note always on, but it’s either this note or an alternative note. So, either C2 or G2, for example. Alt note TRC. I’m not holding my breath on it either. But thanks for the extra info ![]()
I’d like “last” the same way there is first, ie something that happens or doesn’t happen before a pattern change.
asking for last to be a condition is like predicting the future man, how is the machine going to know its the last time?
That could be done with “fill” couldn’t it … that’s the origin of a fill … a lead-up to a change. I can see why you’d want to automate it though.
Could be done not as last but as upon pattern change, so once the user presses a button to change a pattern it arms the condition.
I submitted a long time ago this idea : having the second number lower than the first.
Example 1
9:1 means the Trig arrives after the 8th iteration (it plays on the 9th) and then, it plays on the 10th, 11th, 12th, …
Example 2
9:4 means the Trig arrives after the 8th iteration (it plays on the 9th) and then, it plays on the 13th, 17th, 21st, …
This will allow a Sound to arrive later in the song without using Track Mutes. Digis and Models would love this as they don’t have Song Mode.
That’s all I mean by last.
And I think that I’d like this in addition to fill because I tend to use fill as a way to have variation within a pattern as opposed to just transitioning between them.
conditions on conditions seems natural…
everyone has conditions on conditions
The 9th beat is the 1st. Or the 17th beat is the 1st. It depends how many Bars you have.
the most comforting amount of repetitions to me is 256 steps or 16 bars ,
so beyond that ive lost count
I just dropped in to see –
I didn’t say it but I would like Elektron to extend beyond 8. Like 17:1 or 33 :4 or whatever.
a trig that reverses the play of the track? Fwd / Rev or Ping Pong???
The Five12 Vector sequencer offers something similar to this. There are three layers to its “chance operations”:
- What type of operation (e.g., skip, unskip, mute, unmute, jump to step, randomly change note pitch) would be executed
- The probability that the operation will be executed
- How often the probability is calculated (all the time, only even pattern loops [i.e., 2:2], only odd pattern loops [1:2], every third pattern loop [3:3], or every fourth pattern loop [4:4])
It’s really powerful. Especially having the unmute and mute options allows the “NOT play for A:B” behavior that @darenager wants (and which I often want; I use @sezare56’s hack for this on Elektron seqs).
NOT-x:y is also my #1 hope for TRCs, and it seems like it should be feasible without causing any UI overhauls.
I want one that happens if you have a pattern change queued up. Sort of like the reverse of first. Would be great for automatic transitions.
Don’t tempt me… 
I know I have posted this somewhere here before, but it still fits like hand in glove in a topic like this.
And it is an awesome song!
Not really a trig condition idea, but somehow i miss that “fill” function of these old “electronic organs” of the 80s 90s.
what I mean is something like a “neighbour” (fill) pattern that replaces the original pattern anytime in real time.
there are workarounds, I know.
but it was so easy back then…