Hi all, I read there are problems with midi rx functionality so I just wanted to make sure before buying.
My use case will be simple: 1 en16 for now and later another one. I want to use it with presonus studio one to control plugins. In studio one when I map a new controller I have the option to tell it to transmit the value back to the midi controller so I know studio one will be sending values back
What I don’t know is will en16 receive back properly? I saw a few posts explaining how to setup rx functionality but it just seems very complex to me and time costuming and I don’t even know if it will work properly since reading about various problems
Normally DAWs uses the mackie control protocol for this task , which is nice and easy to setup. I think Intech team is looking into it. You can find more info here:
That’s of course the much better solution, but I guess it would be way to complicated to program and have it work with the different grid modules and the different configurations of modules everyone will want to have. That’s why a simple solution like sending absolute midi cc and receiving back the value would be a much more elegant solution. It should have been like that by factory. Like 99% of midi controllers are. Send and receive.
But thanks anyway! It’s good to know it’s possible to receive back the value cause with absolute midi cc the endless encoders are useless if they don’t receive back from daw
We have two-way communication and are working on improving its performance, this is what we refer to as MIDIRX.
We also have relative mode encoders and other ways to avoid parameter jumps.
We also have MCU protocol setups in the cloud that you could use for traditional control surface type usage.
And off course all of the above is mix and match and customizable.
My advice would be, if you’re still unsure if Grid is for you or not. Try Grid out, and if you dislike its shortcomings, use the 30-day return window that we offer to return them.
Grid is not like other controllers out there. Some people like that and some other might not.
Hey thanks for reply, part of the reason I like en16 is that just not like other controllers your see!
I saw a video of yours, many not you but someone from intech controlling lightroom with the module with the faders through midi2lr. But I noticed there was a delay between the fader and lightroom, like lightroom needed time to catch up. If that a limitation of the RX protocol? Or is it a thing of the past now?
I’m unsure about that specific example, because that Lightroom control scenario is working through a compatibility layer of MIDI2LR.
But I’m also pretty sure that MIDI2LR isn’t using MIDIRX in any of our videos. That’s because our showcases are usually just that, showcases. Basic templates you can use to start with in a specific workflow.
We rarely have the time or the setup to do very specific showcases and MIDIRX is anything but a basic thing in Grid right now.
What MIDIRX can do: send out messages to Grid that can be used for LED control (slow) and basic variable control (spotty).
What MIDIRX can’t do: keep multiple element values and LEDs up to date while you’re recording automation in a multi-module setup with 8+ tracks in a DAW (too many variables for now).
We’re trying and are going to improve the speed of MIDIRX. That’s not a question of whether it will happen.
But generic use-cases like MIDI2LR and MIDI-learn/map based control in DAW and basic control surface control is all possible as I described above.