TRS MIDI latency or gate length issue (maybe)

[rubberband]

Hi Nerds,

I have an issue driving drum voices using TRS-MIDI with the new IO expander.  When I fill in the drum matrix with 16th note triggers no triggers play.  If I reduce the pattern to 8th notes everything works perfectly.  But essentially, any time I have two matrix triggers next to each other only the triggers with an empty matrix space immediately before them play.  E.g. if this is an 8 step loop:

00 x
01 x
02 x
03 x
04 _
05 x
06 x
07 _

only the triggers on step 00 and 05 will play.

-- edit -- I see it now, from the manual:
"MIDI GATL, MIDI GATM, MIDI GATH → Sends a Midi Note On of Note off with a velocity of 33%(L), 66%(M), 100%(H). A filled in field in the matrix sends a gate on which will stay on until the next empty field."

The issue for me is using the MIDI TRGL/M/H commands isn't really workable - on the Flame Fire they don't trigger the drums, and on the bitbox they don't reset the sample playback progress bars.

I've tried this with a Flame Fire drum module and a BitBox MK2.  Both are setup to use midi GATH triggers (and otherwise work great).  I can trigger both perfectly using a trigger pulse from the Nerd trigger outputs, or another module like an intellijel steppy.

Any ideas for a workaround?  Is there a setting somewhere to modify the behavior, or change the timing between high and low for a TRG message?

I have a triggers expander that will work in a pinch, but case space is at a permium at the moment.

[XORadmin]

There is no latency or gate-length issue. There is more an issue on how the receivers did their implementation and basically a lack of a trigger in the Midi specification itself!

Some receivers accept a Note on to react as a trigger (TRGx) and play the sample until finished, some need a Note On and a Note Off (where the Gate stays on as long as the sample should play) (GATx) and play the sample until gate off.
There might be a 3rd option which would be a Note On followed by a Note off directly which is not implemented in the drummatrix as in all user feedback it was working well with both GATx and TRGx. Also here it is not known if the sample would be cut off as well directly then = probably only a small zap of the sample start.

[rubberband]

There is no latency or gate-length issue. There is more an issue on how the receivers did their implementation and basically a lack of a trigger in the Midi specification itself!

Some receivers accept a Note on to react as a trigger (TRGx) and play the sample until finished, some need a Note On and a Note Off (where the Gate stays on as long as the sample should play) (GATx) and play the sample until gate off.
There might be a 3rd option which would be a Note On followed by a Note off directly which is not implemented in the drummatrix as in all user feedback it was working well with both GATx and TRGx. Also here it is not known if the sample would be cut off as well directly then = probably only a small zap of the sample start.

Thanks for the reply!  I'll try to work with it a little more but will probably just put the more triggers expander back in tonight.  Saving space is good, but reliability is better.  Plus, this way I can just unplug and rearrange (or shuffle with a switch) the outputs for fun too.

If I do come up with a solution (at least for the more popular BitBox module) for MIDI triggering I'll be sure to post it here for everyone to see.  I'm sure I've just configured something incorrectly and I'll figure it out eventually.