To send parameter names would require some special processing specifically for the Launch Control XL, because there is no general MIDI 1.x standard for exchanging text. Text is usually done via manufacturer-specific SysEx, but other schemes exist.
Midi 2.0 does have a spec for exchanging this kind of information, but there are very few devices that support Midi 2 property exchange (which can theoretically work over Midi 1.x IIRC).
Looks like it would be technically possible to create a MIDI-CAT clone that uses this Novation sysex system API for a deeper integration with VCVRack, along similar lines to my Electra-One (Orestes-One) and TouchOSC (Pylades) controller modules. It seems to allow some control of what text is rendered in its display, and also supports relative encoders for smoother control changes.
Thanks @pachde and @adadcalledrichard – I feel like a bit of a fool now , for some reason I thought MIDI-CAT coudl already handle this and I was brushing up against an edge case – Now I can see I’lm demanding brand new features!
I’m not much of a coder so I would have to spend some time with Claude to try and get it working. I did however just buy this controller because I imagined it working this way, so I guess rather than spending money on Claude I’m happy to offer some sort of bounty to get it up and running?
Just a quick info: MB got an experimental “v2 mod” with support for custom tags and different selection drop downs. Not sure if I will keep it, but maybe some of you want to try it out.
Oh yes, please! I had that in as a feature request for ages with support. Much appreciated, as that fuzziness in the VCV module browser drives me batty regularly.