XOR Userforum

Hi There,

I was wondering if it is somehow possible to create something like a clock divider on the More Triggers 16. Like having the MT16 assigned to one track (1-8) and have 9-16 for simple divisions.

Of course one could set up a trigger 'each' 4th step, 6th step, 8th step etc. This works a long the divisions fit the track length i.e. length 48 (decimal) can fit (/2, /3, /4, /6, /8, /12, /16, /24), which is generally fine, but one needs to set the track length for the whole 'expander', unless you assign the MT16 to two tracks and have a length of 64 on 1-8 and 48 on 9-16.

When looking at triplet divisions, clock speed needs to be considered as well. I'm looking for doing polyrhythms.

Is it feasible with tables maybe? Or did I miss a fairly straight forward function completely?

Cheers,
Airell

If you simply want different clocks I would go for a Doepfer A-160-2 Clock Divider.

If you want to do polyrhythms inside the NerdSEQ as in have the NerdSEQ play several lines that adhere to differing clocks etc. I would set each of the tracks to a differing clock by means of FX SCLK. See also Page 32 of the manual.

Kind regards,
Michael

I have an A-160-2, and that one is limited in doing triples and dotted divisions and you must choose 'division modes'. The simple divisions are easy to get from the drum grid like I said.
I barely use the out 9-16 and if that would somehow could do divisions (in stead of placing triggers in the grid), I could get rid of the A-160-2 and the CV.OCD which have the following divisions: "24ppqn, 1/32, 1/16T, 1/16, 1/8T, 1/16D, 1/8, 1/4T, 1/8D (dotted eight), 1/4 (beat), 1/2T, 1/4D, 1/2, 1/2D, 1 (bar)".

Setting different tracks (for 1-8 and 9-16) using a different clock/length is what I try to do now. It's just I'm trying to figure out if there is a way to use 9-16 'on the same track' (not loosing one) by maybe using a table or some kind.

A possibility is to use the MT16 for basic divisions, the A-160-2 for 'uneven divisions' and the CV.OCD for dotted and triples (via the TRS midi expander).

I have not yet understood what problem you wish to solve [read: so far it sounds as if you are asking for theoretical options with no real problem to solve]
Maybe you could elaborate a bit on the usecase?!

Just for my understanding:
CV.OCD means the 4ms QCD (Quad Clock Distributor)?

When you want the Trigger 16 Expander to provide a set of predefined clock divisions (as a special mode) I suggest you create a feature request. The more detailed the better.

Actually what you could do is to add a sequence in the track (set to 1..8) using TRBH (which is set a binary value for outputs 9..16) which at least would provide you dividers:
TRBH 001
TRBH 002
TRBH 003
TRBH 004
....
Alternative you could also use TRBH 001 and after that the FX+* command with 001 which will always add 1 to the last FX value = same result, easier input.

(07-10-2022, 07:14 PM)mgd Wrote: [ -> ]I have not yet understood what problem you wish to solve [read: so far it sounds as if you are asking for theoretical options with no real problem to solve]
Maybe you could elaborate a bit on the usecase?!

Just for my understanding:
CV.OCD means the 4ms QCD (Quad Clock Distributor)?

When you want the Trigger 16 Expander to provide a set of predefined clock divisions (as a special mode) I suggest you create a feature request. The more detailed the better.

The CV.OCD is an external 'midi to cv converter' with 4 CV and 12 trigger outs, just like the Mutant Brain. You are also able to output all different kind of divisions of the midi clock to the trigger outs. This way you can have many musical divisions of the clock: 24ppqn, 1/32, 1/16T, 1/16, 1/8T, 1/16D, 1/8, 1/4T, 1/8D (dotted eight), 1/4 (beat), 1/2T, 1/4D, 1/2, 1/2D, 1 (bar) .

Mainly what I want 'to solve' is would like to have a trigger every 12 steps. This can be done with a "1/2D" (dotted half note) division, which means 1.5x the note length of 1/2. (1/2 = every 8 steps x 1.5 = 12 steps). For instance 1/16 is every step (a 16th note), 1/4 is every 4th step (a quater note), so every beat in 4/4 time signature.

Now this can be done setting a trigger in the Drum Matrix every 12th step, but... 64 is not dividable by 12, so you always have smaller jump of 4 steps. When setting the length of a pattern it to 48 it will have any division possible without breaking the divisions (divide by 2, 3, 4, 6, 8, 12, 16), but now it falls short of 64, introducing new challenges.

Setting up the More Triggers to have 1-8 out on one track and 9-16 on a second solves this. The length can be set to 64 on the first, 48 to the second.

I just wondered if there was a different way to not occupy a second track just for this 9-16 'clock divider' which need to be set to a length of 48.

Being able to set output 10 to '/5' and it would fire at 1,6,11 etc... every 5 trigs or /13 every 13 trigs would be an ideal way to set up, but I don't think that is possible...(?)

---

(07-11-2022, 10:18 AM)XORadmin Wrote: [ -> ]Actually what you could do is to add a sequence in the track (set to 1..8) using TRBH (which is set a binary value for outputs 9..16) which at least would provide you dividers:
TRBH 001
TRBH 002
TRBH 003
TRBH 004
....
Alternative you could also use TRBH 001 and after that the FX+* command with 001 which will always add 1 to the last FX value = same result, easier input.

Ok, thanks. I'll have to try this out and see how it works. Right now I can't imagine what this does exactly... seems like magic to me

(07-11-2022, 07:38 PM)Airell Wrote: [ -> ]XORadminActually what you could do is to add a sequence in the track (set to 1..8) using TRBH (which is set a binary value for outputs 9..16) which at least would provide you dividers:
[quote pid='8750' dateline='1657534688']
TRBH 001
TRBH 002
TRBH 003
TRBH 004
....
Alternative you could also use TRBH 001 and after that the FX+* command with 001 which will always add 1 to the last FX value = same result, easier input.

Ok, thanks. I'll have to try this out and see how it works. Right now I can't imagine what this does exactly... seems like magic to me
[/quote]

Oh, that's neat

I just understood that using TRBL and TRBH and the FX columns I can program whatever gate pattern I wish for. Especially with the FX+* and/or FX-/ that creates interesting possibilities.

AFAICT these always create gates (as opposed to trigger). Is there a way to force the outputs to behave as triggers instead of gates?
Possibly separately for TRBL and TRBH?

Some examples in the manual regarding these would be nice.

I suggest to add that 1 and 9 are the LSB (least significant bit). While that is easily found out by trial and error I think it should be mentioned.

I don't get it..

What is the TRBH/TRBL fx doing?
I don't get any "clock divided" Trigger out of the Trigger 16 Outputs..

Can someone please explain?

(08-21-2022, 03:30 PM)kaspar Wrote: [ -> ]I don't get it..

What is the TRBH/TRBL fx doing?
I don't get any "clock divided" Trigger out of the Trigger 16 Outputs..

Can someone please explain?

TRBH and TRBL are setting all 8 outputs of the higher/lower byte at once. I'll try to explain using TRBL for outputs 1-8. TRBH is doing the same only for outputs 9-16.

Assume you want 1 to be high, 2,3 and 4 low, 5 and 6 high, 7 low and 8 high.
Binary that would be 1 0 0 0 1 1 0 1 (outputs 1-8). However the TRBL/TRBH commands have the LSB (==Least Significant Bit) as outs 1 and 9 respectively. So you have to reverse the order:
Binary that would be 1 0 1 1 0 0 0 1 (outputs 8-1). In Hexadecimal that is B1.

Now let's add FX+* to this. We start by TRBL 01 (output 1 -> on, outputs 2-8 -> off).
Next step use FX+* with 01. That changes TRBL 01 into TRBL 02 (effectively switching output 1 -> off, output 2 -> on and leave the rest unchanged).
Next step use FX+* with 01 again. That changes TRBL 02 into TRBL 03 (effectively switching output 1 -> on, leaving output 2 -> on and leave the rest unchanged).
Next step use FX+* with 01 again. That changes TRBL 03 into TRBL 04 (effectively switching output 1 -> off, switching output 2 -> off, switching output 3 -> on and leave the rest unchanged).
And so on.
For the 64 steps of a pattern the state of the outputs 8-1 will be:


Note that these are NOT triggers bit gates and that's essentially what a clock divider does.

Hope that clarifies things a bit. If not feel free to ask and I'll try to elaborate a bit firther.

Kind regards,
Michael

Update: You could as well start with TRBL 00, then the first bit pattern will be 00000000 and the last will be be 00111111 and all the rest remains the same.

(07-10-2022, 11:26 AM)mgd Wrote: [ -> ]If you simply want different clocks I would go for a Doepfer A-160-2 Clock Divider.

If you want to do polyrhythms inside the NerdSEQ as in have the NerdSEQ play several lines that adhere to differing clocks etc. I would set each of the tracks to a differing clock by means of FX SCLK. See also Page 32 of the manual.

Kind regards,
Michael

Can you do that in live ? I mean is it possible to use the input cv assigned to the FX SCLCK to change the clock on the fly.
I look in the manual but I don't figure out to do that