Thread Rating:
  • 1 Vote(s) - 5 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Trig Condition and/or Row Condition
#1
Brick 
FXs that could be super great are TRIG CONDITION and/or ROW CONDITION

Being an intensive user of Elektron Sequencers I can say that this feature makes using probabilities and randomness much more interesting.

It is the fact that, instead of having isolated elements that are triggered (or not), we now have the power to link several events together.
We can imagine much more musical and complex scenarios for the creation of rhythms for example (or melodies):
For example, if the snare drum on step 13 has a probability setting of 90%, we can set a following break (let's say on steps 14,15,16) composed of several elements (Kick, Snare, HiHat...) which will be triggered only when the snare on step 13 is not playing (10%)!

Scenarios are endless.
It's simple but to set up a grid of mutually exclusive or conclusive events (across any of the tracks) could be a neat way to make sequences with randomness and probabilities more exiting.


We could decline this idea for the Nerdseq in this way:

The TRIG CONDITION parameter can set the following trig conditions:

[PRE YES] is true if the most recently evaluated trig condition on the same track was true.
[PRE NO] is true when PRE is not.
[1ST YES] is only true the first time the pattern play (when looped).
[1ST NO] is true when 1ST is not.
[PRE TRACK-2 YES] is true if the most recently evaluated trig condition on Track-2 was true.
[PRE TRACK-2 NO] is true if the most recently evaluated trig condition on Track-2 is not.
[PRE TRACK-3 YES] is true if the most recently evaluated trig condition on Track-3 was true.
[PRE TRACK-3 NO] is true if the most recently evaluated trig condition on Track-3 is not.
and so on...

Maybe it's more solid to think of ROW condition in the Nerseq ? Or maybe we could have both ? 


On the Elektrons there is also a FILL condition witch can be activated by a buttons combo (great fo live uses).
Here we can think to attach this concept with the Automator !
Reply
#2
Please see the countless requests about trig conditions and my replies on these. In short, it is not possible to keep track of every position in every pattern on how many times the sequence passed by plus the type of event that every position is set to...that would need like the double/triple and even more amount of pattern memory.
PLEASE use the search function if something have been asked or discussed before.
Every (unnessesary) forum support means less time to develop! But of course, i am here to help!  Smile
Reply
#3
(06-01-2022, 09:21 AM)XORadmin Wrote: Please see the countless requests about trig conditions and my replies on these. In short, it is not possible to keep track of every position in every pattern on how many times the sequence passed by plus the type of event that every position is set to...that would need like the double/triple and even more amount of pattern memory.

Sorry if I bored you, I searched in the forum with keywords "trig" "conditions" etc... And I found few requests yes.

But not empathised enough on the power of a "what happened before" is true/false then true/false.

In terms of rhythm construction, this changes absolutely everything, we are no longer in a simple isolated random event, which is not very interesting and apart from making chaotic variations (cause we do not have much control on WHEN it happens), that quickly becomes boring. Here we have grouped events!

This is a very modular and clever way of thinking sequences.
It is not for nothing that we make this request to you many times, so I must insist (cause there is only solutions) Smile
Reply
#4
Oh no I’m not bored. Sorry if it sounds a bit harsh, not my intention.
I just want to say that it is not possible.
PLEASE use the search function if something have been asked or discussed before.
Every (unnessesary) forum support means less time to develop! But of course, i am here to help!  Smile
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)