ZEBRA midi assignation is a nightmare

[parricide]

(again why isn't there a search load for those Zebra2.midiassign.txt ? save preset assignation does not look crazy.

It's on our ToDo list, but it hasn't reached a top priority slot, yet.

The reason MIDI Learn is "hidden" behind the Cogwheel is simple: For years we had right-click assignments on knobs. But then people accidentally assign MIDI CCs to parameters, often without noticing. So then they reopen their projects and the sound is different. There were days when we had two or three users running into this. Changing the assignment to the way it is now has changed the situation. No more accidental MIDI Learns. I'm sorry that it makes the workflow more difficult for you, but it has solved a very serious problem.

ive never known people to accidentally "MIDI learn" parameters. im not saying youre wrong, you guys have done much more research than me
if they do that accidentally thats their own fault i say

It used to come up in the forum all the time... someone would say something like "Zebra is broken, the filter keeps jumping to a value I didn't set!!"

i guess if you dont know youve clicked it then its a difficult issue to diagnose. i wonder why people arent posting about it happening in other instruments with a right click MIDI learn

[Urs]

i wonder why people arent posting about it happening in other instruments with a right click MIDI learn

I'm sure they do, but the forum topic is never "I accidentally MIDI learned...". The forum topic is always "Plug-In is suddenly broken" or "I get drop outs" or "strange behaviour", "knob jumps erratically", "always silent".

OTOH maybe our plug-ins are generally quite complex, and thus accidental MIDI learns are perhaps more hidden than on plug-ins with a simpler layout.

But really, we used to get this on a weekly basis. We have hardly gotten any of that at all ever since we introduced the new system.

I'd be open for a right-click alternative as an option, if we also figure out some other things, e.g. visual feedback and stuff. But any of that needs to fit in our update cycle, which hasn't been overly fast in recent years (mostly due to vast changes such as the new preset browser).

[parricide]

I'm sure they do, but the forum topic is never "I accidentally MIDI learned...". The forum topic is always "Plug-In is suddenly broken" or "I get drop outs" or "strange behaviour", "knob jumps erratically", "always silent".

OTOH maybe our plug-ins are generally quite complex, and thus accidental MIDI learns are perhaps more hidden than on plug-ins with a simpler layout.

But really, we used to get this on a weekly basis. We have hardly gotten any of that at all ever since we introduced the new system.

I'd be open for a right-click alternative as an option, if we also figure out some other things, e.g. visual feedback and stuff. But any of that needs to fit in our update cycle, which hasn't been overly fast in recent years (mostly due to vast changes such as the new preset browser).

visual feedback makes sense, even a slightly different colour or tint to the control that has MIDI learn applied would make it clear and wouldn't clutter the GUI.
why do people have to make your job more difficult