stoermelder's Idea und Development Thread

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).

1 Like

Had a quick look at the device’s documentation here: https://userguides.novationmusic.com/hc/en-gb/articles/27840466544402-Launch-Control-XL-3-programmer-s-DAW-mode

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.

1 Like

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! :sweat_smile:

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? :wink:

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.

5 Likes

The only gripe I have with the v2 mod is I’ve got plugins from 400+ brands that overflow the bottom of the screen.

1 Like

I did not expect that, but I added a scrollbar for such extreme cases :slight_smile: I think it is still better than the default drop down.

4 Likes

:+1:

Thanks for the meta module tag. Life saver

1 Like

I’m implementing a ton of new features for the MB module, just a quick overview:

  • “v2 mod” browser variant with better drop-down menus
  • Custom tags for user-defined module grouping
  • Ability to add/remove predefined tags (only within MB)
  • Auto-tagging for custom tags using a curated list (based on the module name & description)
  • Auto-tagging using 4ms as external data source for MetaModule
  • Fuzzy search, also using descriptions (similar to the default module browser)
  • Option to adjust the fuzzy search threshold (to make results more accurate)
  • Option to switch “Favorite” storage to Rack (MB has its own favorite system, as it exists longer than Rack had favorites)
  • Option to enable/disbale highlighting favorites
  • Model magnifier loupe option

I am happy to hear any of your feedback (and: I have no plans to implement a completely new module browser, but you never know).

6 Likes

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.

1 Like