This Module is currently available.
Specs are approved by the manufacturer8-input CV/Trigger to MIDI converter
CVMx is a utility module allowing MIDI messages to be sent in response to incoming CV and/or gate/trigger signals. It's a really flexible module, and opens up possibilities like:
Controlling CVMx uses a single rotary encoder with a push-button to navigate the UI.
In the overview screen, rotating the encoder scrolls a cursor up and down the display, highlighting each of the lanes in turn.
short press of the encoder will change to edit mode for the currently-selected lane. This allows the user to be able to configure the behaviour of that lane (see Operation below for the list of possible actions).
edit mode is left by scrolling to the EXIT field at the bottom of the display and making a short click.
Starting from the overview screen, a long press of the encoder will change to the settings mode where the current configuration can be saved, or a previously-saved configuration can be loaded (selection of the active memory is independent of the save/load button).
settings mode is left by scrolling to the EXIT field at the bottom of the display and making a short click.
CVMx has 8 inputs (labelled a thru h) each of which we call a lane. The configuration of each lane contains the following parameters:
CVMx is highly configurable, and has 32 configuration memories, which can be saved and recalled at will. In addition, lane configurations can be dumped and received using System Exclusive messages. A WebMIDI-based editor is also in development which will be able to remotely configure lanes.
In settings mode it is also possible to save the memory to an external device via System Exclusive (SysEx) messages. Choose DUMP to begin transmission.
Reception of a SysEx dump (from another CVMx, or from a previously-dumped file) is started by selecting RECV and connecting a MIDI stream (via mi/mo or the MIDI thru socket of the mb/1 for example) to input h. When reception has successfully completed, CVMx will return to the overview screen.
The SysEx data is formatted like this:
0xF0 0x00 0x22 0x13 0x00 0x02 0xF7
This breaks down as follows:
SysEx start: 0xF0
Tangible Waves preamble: 0x00 0x22 0x13
Wonkystuff sub-id: 0x00
CVMx product ID: 0x02
data: lane configuration bytes are split into 4-bit nibbles (Further details TBA)
SysEx end: 0xF7