gwpt Thanks a lot for the suggestions!
The MIDI controller idea is indeed already on the future MatriX software wishlist (not for the next revision, as it will take quite a lot of work).
The suggestion to add a sequencer to MatriX has also already been made, but there are some drawbacks to this approach:
a) MatriX has no direct MIDI ports and would need a separate output interface to attach synths. But adding that would take away the BLM ports that are necessary to attach MatriX to our common sequencers.
b) A non-quadratic (wider-than-high) display to show the sequences (other than the 128×128px OLED on MatriX) would be helpful - then it’s just easier to see what is going on.
c) Other user interface elements (i.e. rotary encoders) would be most helpful to configure all sequencer parameters.
Both LoopA and SEQ v4+ address points a) - c). Or in other words, MatriX has been deliberately designed as an extension to existing sequencers that bring all of the required I/O, i.e. MIDI ports, wide screens and encoders.
So for that, i think MatriX will always perform best as an extension to the existing sequencers (or in the future maybe as a separate MIDI controller).