Euclidean Sequencer: Using Existing TRIGs

[igors48]

I noticed that the Euclidean Sequencer can do more than just “generate events (trigs)” as stated in the description.
The Euclidean Sequencer can also use already existing TRIGs when generating a sequence.
For example, if the first 5 TRIGs are set in Standard Sequencer mode, the Euclidean Sequencer will use them (in order) as shown in the image.

This also works in reverse.
If a PLOCK TRIG is set in the Euclidean Sequencer, the corresponding TRIG in the Standard Sequencer will be created or modified.
You can test this by toggling the Euclidean Sequencer on and off (without [FUNC]).

[garf]

Previously:

Euclidean Mode / Rhythms

Linking this picture below back to the link shared in the post above covering the idea of how the Euclidean steps relate to the ‘underlying’ seq steps, it should help visualize the words … Think about the specific case discussed here to serve as a example … It’s a simple case a 16 step pattern and you assign Pulse1=5 Think of the distribution of the Euclidean steps like a stretched ‘window’ into the underlying pattern … it is always stretched unless you have 16 active Euclidean steps lit in p…

[phading]

And how does it work with accent/slide trigs?
It’s not exactly like that (i.e. you can place accent on an ‘empty’ sequence) or what am I missing?

edit: sorry, I thought we were talking about rytm - syntakt might be different.

[igors48]

@phading

And how does it work with accent/slide trigs?
It’s not exactly like that (i.e. you can place accent on an ‘empty’ sequence) or what am I missing?

I’m not quite sure what “accent/slide trigs” are—are they the “trigless (yellow)” ones?
In any case, the Euclidean Sequencer just “generates events (trigs).”
If a TRIG (red or yellow) is defined for that step in Standard Sequencer, the parameters of that TRIG will be used.
If no TRIG is defined, the “default” parameters from the TRIG page and others will be used.

[alechko]

works without issues on rytm, the euclidean generates a second set of purple trigs, they are placed according to the pulses, you can have them slide, accent and mute independently, if you just move them around by shifting then they (accents, slides, etc.) move with the trigs, if you start changing the pulses then some might disappear or new unaffected trigs appear.

this is actually a nice way of having two sets of trigs on the same track, you can have regular trigs and euclidean live simultaneously and switch between them by enabling/disabling the EUC

[phading]

sorry, I didn’t notice we were on syntakt’s forum. Rytm might have a few differences.

mute and swing trigs never move with euclidean gen, I think their position is permanent.

slide and accent move according to their position in the sequence.
Accent on steps 13 and 14 will only be heard if you have 13/14 euclidean steps and will move to the last generated trigs, following their positions.

today I was expecting accent to be permanent in position like mute/swing trigs - I kinda wanted it that way for my use case always having accent on the 13th step, no matter what euclidean pattern was being generated. (and I got a bit surprised, took me a while to understand what was happening. It’s a slightly different result than with P-locks )
edit: correction, see next post

[phading]

@phading

I was expecting accent to be permanent in position like mute/swing trigs (…) [but] It’s a slightly different result than with P-locks

I didn’t really think this through, the Accent and Swing act exactly like any other P-locked parameter.

Wouldn’t it make more sense that accent had a fixed position just like swing and mutes?
It’s the only way it makes sense to me, but would love to hear workflow use cases where this current behaviour is useful - I do get a few ideas on how to use them, but it simply seems too confusing/unnecessary/incoherent… almost like an implementation oversight to me, or a programming compromise.
(talking about rytm here)