Launch Control XL3 Bi-directional midi feedback

Hello, I’d like to get LCXL3 to map parameters in my MPC live 3, basically create a couple of custom templates to control some VSTs / MPC parameters. But I need to make sure it works the way I need it to:

If values on encoders are all set to 0 and I load a preset on my VST, will the LCXL 3 receive midi values from VST/MPC + adjust brightness of the LEDs accordingly? Same if I change value on MPC, will the value on LC update and match in real time? When I change the preset in VST, will all the values be sent to LCs encoders to match? - I know its all the same question/behaviour, I just want to be clear.

I don’t mind using midi cables if necessary, I just need the controller work as described.

Thank you!

I think there is no bi directional midi in standalone.
I would love it, for my launch control and for a apc mini or a launchpad.

Please do a feature request for it, i did.

Most depressing part is that Akai could be making bank on this, by using a proprietary protocol and implementing it on their APC devices. Maybe they fear cannibalizing sales of MPC models with lots of Qlinks and Qlinks label displays.

the problem with 2 way communication is that each manufacturer is handlig data (text data, colours etc) in a completely different way and sometimes on completely non-control related ports and channels - in other words there is no standarisation. For example to light up a pad on some controllers you just need to send midi cc specific to that pad and another cc on a different channel specific to the colour you want that pad to light up, so if uyou want this pad to blink you have to send constantly on/off messgaes. On let's say push however you just need to send short "blink" cc command which will blink the pad according to the tempo and time division selected by that cc or sysex, some devices respond to sysex only and use cc for controlling purposes only, it all depends on the controller really. On top of it they would have to give you access to internal private/public ports and routing capabilities and since everything is managed by alsa (including mpcs own internal control surface and its discovery) things can go sideways quickly if any random Tom and Jerry start messing about. Not saying it's not doable for a regular user even with current state of things