MIDI RX to control LEDs / button state?

Hey, two things:
1.) There is an event under system events called midi rx which holds the "old" way of midi event reactivity on Grid.
2.) There is a new callback based API for receiving MIDI.

In the "old" way, I created a sysex parser preset, where I used couple functions to parse incoming sysex data (sysex sent to Grid). This can give a starting point how to process input data and find a spot for implementing led value / color updates.

To check out the new callback style API, drag and drop the universal MIDIRX snippet to an empty element's action list (no actions present on an element) to see how a callback based rx code works.

Also here is the docs page for the new callback style API: https://docs.intech.studio/wiki/more/midi-rx-new/

I tried this out, and having a little bit of trouble understanding what's going on. I set up two callbacks under the "System" element code block, one for SysEx and one for "plain" MIDI, just so I can see how the variables are set when they come in.

I'm sending the (sysex) message 0xf0411000f7, and the MIDI monitor on the left is showing that the device is indeed receiving these messages, but they are not showing in the "System Exclusive Messages" area, and the self.sysexrx_cb callback isn't firing. Instead, the self.midirx_cb callback is firing with a partial message (it seems like).

This seems like incorrect behavior? Or am I doing something wrong?

still haven't been able to make this work - would anyone know why the sysex messages aren't being picked up?

I am also wondering about this!

@user @user I tried this and found that this is a bug in the grid-fw. When on Grid you use the midi action block in sysex format, the callback is triggered. But it is not triggered on USB received (external) sysex messages.

Made a firmware issue for it:
https://github.com/intechstudio/grid-fw/issues/281

Please add any remarks to the issue itself if possible. I suggested for my peers to do a preparsing of the sysex data, where the sysexrx_cb returns a a table of integers instead of a raw hex string.

@user thank you for confirming! Will look forward to a FW update!

Hi all, I am seriously battling to understand how all this works - Maybe (probably) I have completely underestimated the technical level needed to set-up these controllers. All I am trying to do is a very simple mapping of a Endless control on my VSN1 to an Ableton parameter (this is all done and working), AND have that also react to changes to that parameter internally from Ableton. So I can tweak the control in my live performance but when I then reset it to centre (=64) from Ableton, I need the Endless encoder value to reflect that change and the LED update accordingly. It looks the same as what is being questioned in this thread? Please let me know if I'm off piste and I'll raise my own thread.

Is there a laymans guide to how to set-up the above, the instructions I found online (https://docs.intech.studio/wiki/more/midi-rx-new/#example-en16) are WAY above my understanding. Or if there is an overview guide I should be reading 1st, please can someone point me at this.

I'm beginning to feel that these controller should probably come with a warning of the technical level needed for users to set-up...I'm seriously struggling.

I feel exactly the same. I was expecting the setup to be similar as the experience with Novation Components or the Faderfox editor, but it seems to be really designed for developers.

Not a complain towards Intech per se —the controllers feel awesome and the possibilities with Grid are immense—, but I have had the VSN1 for almost 2 months now and I can't make use of it as I wanted, and the screen is totally useless right now.

Again, it would be great to be able to contact with developers to help people like us with limited scripting knowledge.

@user, @user please open up separate #channel seeking support for your specific needs. We have some profiles / presets readily available for these and if not, it's easier to work on separate cases in separate threads.

Hi, is there any ETA for the sysex bug fix? I'm trying to use a sysex message to sync my EN16 with track colors in Ableton 🙂