@Timo LoopA does not use the Virtual BLM16×16+X protocol to communicate with MatriX. But you can use the the Virtual BLM 16×16+X software to talk with a SEQ v4+. For both SEQ v4+ and LoopA, all communications going to the MatriX are sent via the dedicated BLM port.

Best regards,
Peter

Thank you Peter, but does that mean I could still try out the BLM implementation with the Virtual BLM16×16+X app if split the BLM port and connect the Virtual BLM16×16+X via a midi interface to it?

Hawkeye
I’ld like to make something myself that displays the current clips in a session (and what is active).
I miss this during live performances.

The Matrix itself is way too big for that purpose, I am already pushing it with the space I need when I play somewhere
So I want to use this a very small (7×7 cm) led matrix for this.

If it is not the same protocol as the VirtualBLM16×16+X then how can I figure out the protocol used by the MatriX?

@Timo, that will unfortunately not be easy - LoopA and MatriX perform handshaking before any data flows, and all follow-up communications are packed and optimized.
Best regards,
Peter

thanks, that’s a bummer!
Is there a possibility for me to look at the midi implementation? (discreet if desired)

Awesome, I think that sounds very doable.
I will report back as soon as my din8-> din5 pcb and a proper cable has arrived.

I made this little board to split blm to midi in/out (I have spares available if anybody wants) and I got to work in max/msp

Upon the load of a song the current data is sent out in sysex packages, this contains (among other things, that I didn’t bother to check yet):

• the one that starts with 2 contains set wide info, including name, occupied patternslots and mutestates (sometimes these values are packed together in one byte).
• The sysex package starting with 3 contains the currently active scene, active track and trackname.
• The (various) packages starting with 4 contain all the note and cc data of the currently selected pattern.

Here is that data clumsily visualised in max :

This data is only sent once upon loading.
So the big questions right now are:

• How do I request an update of the current state?

• How do I start/stop patterns, or trigger a whole scene?

• How do I mute?

• How do I select a track? (and also start/stop/record would be awesome to know how to control).

  
  

  I think that’s about it, not really interested in editing remotely, just performing.

Well done! I had the impression that getting the info out of LoopA which clips are available and what is playing back was your primary requirement (see your above post) - i can help you parse the status packets that you get, but for more remote control i think you need to go through the full handshake procedure, which we cannot document.
Status packets should be resent, when you select a new track/clip on LoopA.

Best regards and have a good weekend,
Peter

Yes, my primary requirement is the parsing of the status packet and keeping that up to date.
However, the status update are note resend when selecting a new scene/track/clip on loopa, only on file load. Is there a sysex message I can send to force this resend?

Yes, my last post went further, it was so much fun that I would like to set the scene or individual tracks with button presses instead of the encoder. It would be awesome if you could share that as well. Is the reason not to share it complexity? or protection of your work?

Hi Timo, yes - it’s closed-source because of IP protection. The info packets should be sent on session load - my initial impression was that you just want to get “some more info” out of the unit when a scene was loaded, which i think you can do now? Any further live control and status requests are not possible without a MatriX.

Best regards,
Peter

I am sorry to hear that you want to keep it closed.
And I am sorry to hear that there is no way to keep the visualisation updated (it only can show the state it was in upon load).