ReaLearn: Add controller preset for Softube Console1 mk2

[helgoboss]

This thing gained a lot of tracktion.

Generic MIDI mode

When the Console 1 On-Screen-Display is not running, this thing works in generic MIDI mode.

For the most part, that MIDI mode is pretty straightforward: Almost all buttons and encoders transmit. LEDs and peak meters can be controlled. One caveat is that this device tries to be clever:

• By default, all encoders send absolute (sigh) and very coarse-grained MIDI messages
• Fortunately, the encoders keep sending 0 when repeatedly turning counter-clockwise and 127 when turning clockwise, so that relative control can actually be done (even as part of the controller preset, via Allow control transformation to output relative values #800).
• However, the internal value of an encoder is updated when it receives feedback, to avoid parameter jumps with absolute control. While this sounds good at the first sight, it's actually terrible. It destroys simple absolute-to-relative implementations that based on control value diffs.
• The LEDs are updated automatically directly on the device. It can be overwritten by subsequent feedback. But that can lead to slight flickering.
• The "Fine Adjust" button doesn't send any MIDI but turns the coarse-grained adjustment of the encoders into a fine-grained one

In MIDI mode, the "Fine Adjust" can't be accessed, sorry.

Native mode

• When the Console 1 On-Screen-Display is running, this thing sends sys-ex messages. Even for the "Fine Adjust" button! - The LEDs and peak meters are still controllable via normal MIDI messages. Good!
• The "On" button is not really usable. It sends different messages on each press.
• Drawback: As soon you use Softube plug-ins, the happy hour is over. They take control and are controlled by the Console 1 directly. I didn't find any way to switch that off.
• And as far as I can see, there's no way to bring the Console1 into native mode without starting the On-Screen-Display. I checked the traffic and I couldn't detect any magic sys-ex. The Softube Software seems to use some proprietary USB (non-MIDI) communication to switch it to native mode. I even asked Softube about this but got no response so far.

I create a controller preset nevertheless. For relative control, this is the best mode (as long as you don't use any Softube plug-ins)! No glitches. And "Fine Adjust" button works (probably more important than "On" button).

[helgoboss]

Okay, a final statement (also posted that in the REAPER forum):

I studied the Console 1 mk2 in detail and created 3 ReaLearn controller presets for it (available in upcoming ReaLearn version).

• Native mode
• MIDI mode with absolute control
• MIDI mode with relative control

The controller presets are neutral, so they don't define yet what each button does or what the LEDs/meters show. You can use the main compartment in ReaLearn for that.

• Native mode is - hands down - the best mode in terms of flexibility:
• True relative control without glitches
• True momentary buttons
• LED feedback without glitches
• Button "Fine Adjust" is available and can be customized

There's one caveat: The Softube On-Screen-Display software must be running AND you can't use Softube plug-ins (as they would interfere). I wish Softube would provide a way to put Console 1 into native mode without having to start the On-Screen-Display. Then this mode would be perfect.

• The MIDI modes are crippled due to the way Softube implemented MIDI control. Most problematic:
• The buttons only act as toggle buttons, which makes momentary usage or ReaLearn features like "Fire mode" impossible to use.
• The encoders send absolute messages. They can be turned into relative ones, but it doesn't work perfectly.
• The button "Fine Adjust" is not customizable.

I really wonder why Softube crippled the MIDI mode so much. Any modern DAW has support for relative control and software-powered toggle modes.

Plus, one addition: For native mode, I added simulated encoder acceleration, based on the speed of turning the encoders. This is achieved via control transformation in the encoder mappings.