May 31, 2020, 12:33:16 pm
Welcome, Guest. Please login or register.
Did you miss your activation email

Arturia Forums

Author Topic: Feature Request: Route Velocity With Software Interface  (Read 1191 times)


  • Apprentice
  • Apprentice
  • *
  • Posts: 3
  • Karma: 1
Feature Request: Route Velocity With Software Interface
« on: September 12, 2016, 12:17:38 pm »
Would it be possible to add the ability to route velocity to the destination that the Mod Wheel is not currently using? For example, if the Mod Wheel destination is set to 'cutoff', velocity would control LFO depth and vice-versa.

I've been working on a couple mods, and I noticed that both the LFO and Mod Wheel Cutoff are generated by the MCU, independently. When the Mod wheel is set to 'LFO depth', the +/- 5V LFO generated by the MCU is attenuated, and the cutoff control signal is always 0V. When the Mod Wheel is set to 'Cutoff', the LFO is transmitted at the full +/-5V, and the 0-10V Cutoff signal is generated. Unless I'm missing something, I don't see a technical reason why both these things can't be controlled at the same time.

Since the microbrute's keyboard generates velocity, and the MCU of course can receive velocity MIDI data along with pitch bend, mod, and notes, I think the only change that would need be made is in the MCU code. A switch would need to be put in the software interface to turn the feature on/off, and a control to set the level of velocity depth.

Since both those CV signals are generated on the MCU (LFO and 0-10V for mod wheel to cutoff), you could get a lot more fancy with combining mod wheel/velocity depth amounts to 'cutoff' and 'lfo depth', but a basic ability to route velocity in this way would be extremely useful and, I think, fairly easy to impliment.
« Last Edit: September 12, 2016, 12:57:25 pm by brendanclarke »


  • Apprentice
  • Apprentice
  • *
  • Posts: 14
  • Karma: 2
Re: Feature Request: Route Velocity With Software Interface
« Reply #1 on: September 29, 2016, 05:59:53 pm »
I support the HELL out of this. And I agree that there is no technical reason (as far as I can tell) why the velocity signals shouldn't be able to be routed as described- I think that this is such a clean and elegant solution that should be able to be implemented fairly easily.

Please Arturia ... it is time to just publically release the software/code. It is clear to all of us that our complaints and requests are falling on deaf ears. The entire community would benefit ... just LOOK at the success of the Volca series simply by releasing the schematics.

Regardless, this feature would be invaluable to me (and many others, I presume) as it would give the unit even more potential in a live setting (or otherwise).

Thank you for your continued support.


Carbonate design by Bloc
SMF 2.0.13 | SMF © 2016, Simple Machines