Polymetric Trigger Matrix (individual track lengths)

[knights who say neve]

I didn't see any way to set the individual tracks in the trigger matrix to different lengths for polymetric grooves.

So here's the idea I came up with. A new FX called Break Mask, with two codes, BMLO and BMHI (I'll explain why there's two in a moment).

The idea here is to use the FX Value to set a mask for each track. 

A "1" means don't break, a "0" means break. 

So for example, "BMLO AA" would let tracks 1, 3, 5, and 7 continue, and break (return to step 00) tracks 2, 4, 6, and 8. 

Because, AA = 1 0 1 0 1 0 1 0

"BMLO 55" would do the opposite, letting 2, 4, 6 and 8 continue while breaking tracks 1, 3, 5, and 7.

Again because,  55 = 0 1 0 1 0 1 0 1 

(MSB = track 1,  LSB = track 8 to match the track layout on the page)

And of course, BMHI would do the same for tracks 9-16.

Possible?

[XORadmin]

That is not possible. It is not individual tracks but columns within a track. Inside a track your request would mean that I got another 16 tracks extra running (each with their own steplength ..well based on break). And I would need a master because else there would be no chance to match it with the main sequence.
I do have this with the audio track as they are 2 possbile groove settings within a track and it is a drama for maintaining and gets confusion with users from time to time.
So in short, I am not planning to go into that rabbit hole. Use the trigger outputs on multiple tracks to get similar results. I think it is already quite a luxury to control multiple triggers/gates from only one track and not losing a track for each trigger/gate.

[knights who say neve]

OK, fair enough. But using a track for each track length is not a great answer, esp. with only 8 tracks total available - typically with this sort of thing I'm assigning individual percussion instruments to have different lengths.

However: TRBL and TRBH, run from a table, would do what I need, because the tables can have a different length than the track.

Are there any plans to add tables to the More Triggers Screen? (There is a blank column available).

Or, to make TRBL / TRBH commands accessible from other types of tracks (and their tables)?

[XORadmin]

OK, fair enough. But using a track for each track length is not a great answer, esp. with only 8 tracks total available - typically with this sort of thing I'm assigning individual percussion instruments to have different lengths.

However: TRBL and TRBH, run from a table, would do what I need, because the tables can have a different length than the track.

Are there any plans to add tables to the More Triggers Screen? (There is a blank column available).

Or, to make TRBL / TRBH commands accessible from other types of tracks (and their tables)?

Tables are definitely planned.
Still…only 8 tracks. It could be much worse…like 8 tracks and only one trigger can be used per track..no difference in timing between tracks (and much more to tell) while here you got up to 16 (and more) outputs per track plus some CV and each track can run independently. 
Sorry, can’t give you everything ;-)

[knights who say neve]

You don't have to tell me, I've done my time in the old-school hardware sequencer trenches...RM1X, RS7000, EMU Command station, MPCs (still have my 4K). If the Nerdseq had all tracks locked together with one "playhead" like a multitrack tape, I wouldn't have bought it. I shall wait for the trigger tables.