Tons of Midi Controllers: Launch, E16, Faderfox, Fighter, …
Some have LED Rings. Some even Motorfaders.
But none are able to receive from an Elektron (e.g. Digitone II) the current value of a parameter.
Apparently because no Elektron is sending them out.
Example:
On Track 5, the Filter Cut-Off is 0.
On the Controller, I rase it from 0 to 64.
I change Patterns, Filter Cut-Off is now 32 on the Elektron.
The Controller still shows 64, and a parameter jump will occur.
Thus, “useless” for Elektrons, if you aim for this workflow and scenario.
(I’m not entirely sure, but I suspect that sending ALL parameter values when a pattern starts might throw the standard MIDI timing off a bit. With “Snap,” the parameters aren’t synchronized until the first match—at least there are no sudden parameter jumps
Configurable MIDI takeover modes would be a boon as well as bi-directional MIDI and/or CC61 parameter dumps. Though, I thought that ‘MIDI CONFIG => PORT CONFIG => ENCODER DEST’ set to ‘INT + EXT’ provided a pseudo-bidirectional behavior. Could be wrong. It just doesn’t help with initializing MIDI controller values to the current values on-device.
Workflows are wildly everywhere for many of us. I agree with your position on the pattern change sync up issue, but that doesn’t make a thing useless. I’ve implemented a variety of midi controllers over the years. Sometimes, that meant pages and saved states between devices that overcame various issues. Octatrack does the CC 61 broadcast, which is something I wish were everywhere in Elektron boxes for anything that deals in MIDI CC.
MIDI 1.0 is * checks notes * 43 years old. We’re living in a world of adapt and overcome until 2.0 eventually releases, and even then, it’s not going to suite everyone’s workflow the way they dream. Concessions abound!
I think it would just be the same amount of midi sent back as the controller is sending in the first place.
The Melbourne Instruments Roto Control does exactly this. It sends midi to your DAW, and also receives it. It’s motorized knobs jump instantly to reflect changes made in software.
Some hardware also does this. Koala has bi-directional MIDI feedback with the latest SP404. And Drambo and Loopy Pro (on the iPad) both do bidirectional MIDI feedback with the Launchpad Pro and other controllers. Drambo even works with the Roto Control.
I think that all midi-capable boxes should do the same. The Digis already send midi out from knobs and buttons. The only other thing needed would be to send all parameters when you switch screens.
I use my faderfox mapped to only MW controls on my digis, then use the ST MW macro for any parameters I want to play with. It’s not affected by pattern changes, so no issue. Workaround, but one that works well depending of your workflow
Edit. Also faderfox can use relative CC, didn’t try it yet on my digis but might be worth a try to see if it still jumps with it
O wow, I didn’t know that. I was sure (or actually hopping) that the digitone will send a snapshot of the parameters state when switching a pattern.
Thanks for the headsup, saved me some cash but nonetheless disappointing.
My wish is that Elektrons support relative cc messages. They’re often implemented as having a center value of 64, so if it received value 65, that means +1, and 63 means -1.
Faderfox already supports sending these, but Elektron needs to support receiving them (rather than jumping the value to absolute value 65).
If they add this, and then also a dedicated midi channel for Ctrl+All relative messages, we’d have everything we need to perform freely on a wide range of controllers!
