Reworking MIDI RX, how midi sent to Grid is processed

Grid
21

hi first post & sorry if this is the wrong topic for my q !

checked the docs & did a quick search of the forum but couldn’t quite grok a clear answer (I don’t own any of the hardware currently) – it currently possible to receive sysex messages and store the parameter values to a variable ?

the use case I’m imagining is incrementing a bunch of different sysex parameters (with different values) using a single encoder. so being able to poll absolute data (via sysex dump) → sum with delta value → send absolute value back to device. possibly also displaying data on LEDs.

reading through the rest of the topic it sounds like there might currently be some stability issues implementing my idea but I’m curious if it’s an intended supported use case or if reception is CC-only : )

22

Hi, MIDIRX currently doesn’t do anything with SysEx packets.The parsing of SysEx packets with MIDIRX is a planned feature however.
So stay tuned?

23

Hi! I have made a preset which can be used on any modules while putting it onto the system (utility) button element. It’s called “sysex buffer v1” on profile cloud.

I have tested it with sysex strings through SysEx Librarian, worked ok!

@narayb, happy to show this for you, in short: sysex is usable with midi rx, just need coding.

1 Like
24

Hi guys,

I was wondering if maybe the MIDI action:

image
image1032×286 27.7 KB

if each element could have maybe an additional RX tab? So setting midi feedback maybe is more immediate and easy for people don’t use code.

Or - if putting in there is a little more difficult for design or consistency reasons, just have a MIDI Action, name MIDI RX, or MIDI IN, here?

image

Where you basically going to set normally the same parameters than MIDI output.

What do you think?
Cheers.

2 Likes
25

@antblanca This is an idea we have been thinking of - a good idea for sure. I don’t want to spoiler anything at this point, but have some news to share here:

There are 2 threads where development of Grid Firmware and Editor changed recently:

1.) @narayb as project manager started to work on a full UX overhaul, based on the past 2-3 years accumulated frustrations with Editor editing experience.

2.) We’ve hired a firmware developer, so after he can pick up the pieces where @suku was overwhelmed, both Knot and the Grid firmware can get the attention they deserve.

With the changes to our team personnel wise and with the change of priorities, I’ll share a roadmap for 2025 this december in a separate thread.

3 Likes
26

Did I miss the 2025 roadmap post? Would be very curious to hear about the firmware overhaul as resolving the midirx issues are critical to what many of us expect from the Grid modules.

27

Hi! We did not forget about sharing a roadmap with you all. We still have important topics to talk through in relation with Grid like:

  • Longer config length (400 char+)
  • MIDI Rx stability for most common use cases (discussed also in this thread)
  • Potentiometer and fader (analog control element) value reading speed / more data on quick sweeps
  • Faster page changes

In the first 2 month of 2025, we are focusing on VSNX modules, in order to make the first prototypes usable and development for the screen can begin. Beside the new module(s), we are introducing mechanical switches to the lineup, so our development resources going towards that as well, like the new control elements can be used / identified in the Editor.

The UX overhaul is also in progress, carried by @narayb.

About key firmware related developments, we can share more after February.

1 Like