September 25, 2016, 02:23:31 pm
Welcome, Guest. Please login or register.
Did you miss your activation email
News: A maintenance is planned for Thursday, 15th of September. It should last 2 hours, starting at 10am french time.

Arturia Forums



Author Topic: Velocity response with FW update?  (Read 28 times)

brendanclarke

  • Newbie
  • *
  • Posts: 2
  • Karma: 0
Velocity response with FW update?
« on: September 22, 2016, 01:53:33 pm »
Seems like nobody replies to messages in 'General', so I'm reposting here...

After popping open the microbrute and seeing how signals are routed, it's clear that there is no technical reason that the synth wouldn't be able to respond to note velocity.

Both the LFO and Cutoff CV for Mod Wheel control are generated by the MCU, independent of one another. 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.

Since the microbrute's keyboard generates velocity, if the firmware were updated, velocity could be routed to the Mod Wheel destination that isn't being used by the Mod Wheel. Velocity depth could be controlled by external MIDI or from the software interface.

Note that this is different from the 'velocity hack' of routing velocity back in as mod wheel data in that the synth would be able to respond to both mod wheel AND velocity simultaneously.

 

Carbonate design by Bloc
SMF 2.0.11 | SMF © 2015, Simple Machines