Some Problem with MIDI CAT and Roto Control

Plugins & Modules
1

Hi there and @stoermelder ,

I have been running in to some issues using MIDI CAT and I would like to address those.I am not sure if these bugs happen only to me because of my set up or some things I do wrong along the way;

I am experimenting connecting Melbourne Instruments Roto Control with VCV. Roto Control has motorised knobs and buttons with LEDs, so I am using MIDI CAT for the feedback.

Everything works fine when I use MIDI CAT, I can control VCV from Roto Control and vice versa button lights works without the need of binding LEDs from MIDI CAT.

I use the MEM extension to store different midi mappings and when I toggle in between the two different mappings the knobs on Roto Control does not register the positions of the toggled map’s knobs on VCV, instead the knobs on Roto Control spins all the way to 127 and stay that way unless I touch either the controller or the mapped knob on VCV which causes a jump or drop in the midi signal. I have tried RE-send MIDI feedback with no success.

I am wondering if I am doing something wrong or there is a way around it, as I would be very efficient to have multiple mappings.

I am running Rack Pro 2.6.6 MacOs ARM64 Packone 2.1.0 on a MacBook Air M1 macOS Sonoma 14.5 ..

Thanks in advance

2

I will check if there is something wrong with the MEM expander. Just to verify: MIDI feedback works fine if you don’t use the MEM expander?

3

Ben thanks for the quick reply,

Yes midi feedback works fine until I press prev or next button on MEM, as soon as the mapping change, the faders on Roto control go to maximum value (127).

4

Thanks for reporting, this was indeed broken. If you know how to install plugins manually, you can grab the latest development build with the fix.

2 Likes
5

Thanks Ben, I will install it asap.

As I have your attention I would like to report one more issue : MIDI CAT saved presets does not load properly, the ins and outs are correctly addressed but the midi cc addresses are not there when saved preset is loaded. I use strip to work around this issue at the moment.

I realize also that MEM can only store mappings for one instance of the same module.

When there are more than one instance of the same module, after mapping the second instance when I go over store mapping in the menu, the store mapping context menu shows the “same name” as the stored mapping of the first instance which is already in the available mappings. This is due to both modules having the same name I guess.

As a feature request it would be great, if it would be possible to map and store more than one instance of the same module in the upcoming releases (maybe using “Module Instance ID”)

thanks again :folded_hands:

6

it’s working :smiling_face_with_sunglasses:

7

The idea for MEM was to re-use the same mapping for all instances of a specific module. This limitation allows a workflow to switch easily by key-press across modules, as it is unique and would would not be possible with multiple mappings. Won’t it possible for you to use two instances of MEM for different mappings?