Why are triggers in MS instead of musical divisions?

[fadeddata]

Just what the thread subject says. It seems like it would make more sense to be fractions of the row length with something like 10 being 1/16 of the row length and no repeats. While something like 52 would be 5/16 of the patterns row length and 2 repeats. And F0 would be just "ON" for the duration of the row.

[mgd]

I do not find it as obvious as it seems to appear. For me it comes down to the distinction between triggers and gates. I'm aware they are often interchanged in their use and they are similar. But at the end of the day I want triggers to be short and their duration independent of my music timing. For gates I'm 100% percent with you. Their duration should be related to the music in almost all cases I can think of.

Which kind of canonically leads to some form of feature request to have gates with musically determined duration on top of the current trigger oriented options.

Does that make sense?
If yes I'd repost it under feature requests.

Kind regards,
Michael

[XORadmin]

Practically it doesn't really matter in most cases:
If you trigger a drum, it doesn't matter. If you fire an envelope it doesn't matter. If you play notes without anything, then the durations are so short anyway that it would be difficult to hear the difference anyway (except for if you sequence in 10 BPM) . And if it would be really needed, then you might want to involve tables, or use the kill command.

FE is already gate on and 00 Gate off.
Gates can be set and reset in any duration, on any step that is much more flexible than having only fixed gates for like a quart note, half a note 137 step long gates etc.

In the new version that you saw most probably that some more features have been added to the trigger column. There are 2 trigger types which are 1 step and half a step long. I decided to not add more since i think the random and ratch function are much more important than gates over multiple steps that you can do anyway already.

[fadeddata]

It totally matters to my ears. I’m often using the repetitions and have to figure out the milliseconds of the BPM. And if I change the BPM the whole things will sound weird. Especially for fast snare drum programming. At the moment I end up just using tables now, but when I first was learning I tried triggers. To be honest I don’t really use triggers from the pattern editor for repetitions anymore.

[XORadmin]

It totally matters to my ears. I’m often using the repetitions and have to figure out the milliseconds of the BPM. And if I change the BPM the whole things will sound weird. Especially for fast snare drum programming. At the moment I end up just using tables now, but when I first was learning I tried triggers. To be honest I don’t really use triggers from the pattern editor for repetitions anymore.

I am not talking about ratcheting, but triggerlength.
Ratcheting is a different thing and indeed must be based on the tempo. Take a look at the new version again and i think you will find what you are searching for.

[fadeddata]

Looking here:
https://xor-electronics.com/forum/showth...hp?tid=987

Which functionality are you referring to?

[XORadmin]

Looking here:
https://xor-electronics.com/forum/showth...hp?tid=987

Which functionality are you referring to?

"Values in the trigger column bigger than E0 got a special function now for even and odd ratcheting, random triggers, random 'ratches', random gates based on the random ranges."

[fadeddata]

Hah! Wow, what a surprise, this is exactly what I was looking for.