‘Two Way MIDI’ module for Modul8
What does ‘Two Way MIDI’ do?
Two Way MIDI is a module that enables Modul8 to send a midi signal back to your midi device. Two Way MIDI will keep your midi device updated with the values from Modul8 so that you avoid annoying ‘jumps’ when the current setting of your device doesn’t match the values of Modul8. Two Way MIDI is downloaded from the ‘Online Library’ menu item within the Modul8 application.
Whenever you touch a control in Modul8 or switch to another layer Two way MIDI will update your MIDI device with the current values.
Who can use this module?
This module is only relevant if you have a midi device that is designed to receive MIDI as well as send MIDI. Typically these devices will have motorized faders or 360 degree (endless) knobs with LED displays. Examples of such are Novation MIDI controllers and Behringer BCF2000.
How do I get started with this module?
Before you start please clear your current midi map. This is not a must but it is recommended to avoid unexpected results when trying out the module. You can save your current midi map by selecting Mapping -> Import/Export -> Export MIDI map. Then remove the map by selecting Mapping -> Edit MIDI map -> Clear map. Please do this for ‘Focus’ as well as ‘Position’ and ‘Layerset + Position’ modes.
1. When you first start the module you’ll see a list called ‘MIDI Device’. Please start by selecting your MIDI device from the list. The module should now be able to communicate with your midi device.
2. Try turning a knob on your midi device. You should see some text appear at the very bottom of the module window. Eg. ‘receive: ch1 cc3 127′. This is information about the midi your device is sending to the module.
3. Now try mapping something. Click Edit, click something in the Modul8 interface. If a text appears in the ‘action’ field (e.g. ‘ctrl_layer_alpha’) you can map it to your midi device. Simply turn a knob and it is mapped.
4. Click another Modul8 control or map multiple MIDI knobs to the same Modul8 control if you wish
5. Click ‘end edit’ when you are done mapping. You should now be able to control Modul8 with your mapped knobs. Also if you change the Modul8 control the change should be reflected on the MIDI device
Will this module work with my device?
The module is currently in beta and has only been tested with the Novation Nocturn and the Behringer BCF2000 MIDI controllers. It is designed to work for all devices that are able to receive MIDI, so it needs to be tested. Please get in touch if you have tested it with other devices.
What version of Modul8 do I need to use this module?
So far this module has only been tested with Modul8 v2.6 but it may work with older versions. Please get in touch if you have tested the module with an older version of Modul8.
What MIDI values are sent for the different Modul8 controls?
0-127 for all scalers and sliders and knobs.
For layerset buttons 0-7 is sent.
For Media set pages 0-7 is sent. (8 for the ‘sp’ page)
And so on 0,1,2,3…. for all special elements like radio buttons etc.
You can see what midi values are being sent out from Modul8 by touching a Modul8 control (one that has been mapped). Look at the very bottom of the module window. A message will appear e.g. ‘send: ch2 cc34 127′. The last number is the midi value. ‘ch’ is channel and the next is ‘cc’ for control change or ‘n’ for note.
How do I set up a button on my MIDI device to select layer sets in Modul8?
Look for a setting on your MIDI device to create a ‘Step’ button. So that first time you press the button it sends 0, next tme 1 etc. with a max value of 7.
You can also set a rotary knob with a minimum of 0 and a max limit of 7.
If this is not possible with your device it is possible to use the regular Modul8 midi mapping (the Mapping menu in Modul8). See ‘Can I use this module together with the regular MIDI mapping in Modul8′.
How do I set up a button on my MIDI device to select media sets in Modul8?
See above. Same method as when mapping layer sets.
Does this module work with all controls in Modul8?
No, there are some major limitations unfortunately. First of all ‘Two Way MIDI’ is not able to work with any of the controls in any of the other modules. Secondly there are also a few features in the main Modul8 interface that does not work with ‘Two Way MIDI’ (e.g. create/duplicate/delete layer).
However there is a workaround. You can use the regular MIDI mapping in Modul8 together with the module to overcome some of these limitations (your only challenge is to keep track of what you have mapped where).
What is the difference between this module and the regular MIDI mapping in Modul8?
– Module sends and receves midi. Buiit in mapping only receives
– Built in mapping has ‘focus’, ‘position’ and ‘layerset + position’ modes. Module only has ‘focus’ and ‘position’ mode.
– This module treats layer set buttons, media set buttons and other radio buttons as groups instead of separate buttons. E.g. you can map one rotary knob or button to flip through layer sets.
Can I use this module together with the regular MIDI mapping in Modul8?
Yes, it is possible to use this module and the built in MIDI mapping (the mapping menu). The same control can even be mapped in the built in MIDI mapping and in the module at the same time – but I don’t recommend this – I recommend only using the built in MIDI mapping for controls that are not covered by this module.
What are the ‘focus’ and ‘position’ buttons for?
These are buttons for switching between two modes of midi mapping. They are identical to the ‘focus’ and ‘position’ mode of the regular MIDI mapping in Modul8.
In ‘focus’ mode you map the dial to the active layer in Modul8. E.g. you map a dial to the movie speed in ‘focus’ mode. If you go to another layer your dial will change the speed of the selected layer.
In ‘position’ mode you map to a specific layer. E.g. the movie speed of layer 3. If you change focus to any other layer your dial will still control the speed of layer 3.
Why is there no ‘layerset + position’ mode?
The regular Midi mapping in Modul8 has ‘focus’, ‘position’ and ‘layerset + position’ mapping modes. This module only has the ‘focus’ and ‘position’ modes. I have made this decision as I see no advantage of building this into the module. If you need this mode just use the regular midi mapping for this.
Are my MIDI mappings kept next time I start Modul8?
The module has two options for where to save your MIDI mapping ‘Default’ and ‘Project’. When you make a mapping in ‘Default’ mode the MIDI mapping will be kept inside Modul8 and be active next time you start Modul8. If you select ‘Project’ mode and make a MIDI mapping the mapping will be kept inside the your Project file and so the MIDI mapping will be active next time you open that project.
Please be aware that if you edit the module code in the Module editor, you will loose any ‘Default’ map you might have.
Can I have a different MIDI mapping for each project?
Yes. Just choose ‘Project’ mode before you make the mapping.
Can I export my MIDI mapping?
Not directly no. You can however reuse your mapping with a small workaround. E.g. if you want to use your MIDI mapping from project A in Project B: Open project A. Project A will be in ‘project mode’ if it has it’s own MIDI mapping. Click ‘copy to default’. Next open Project B, make sure the module is in ‘default’ mode then click ‘copy to project’.
Also if you wish to back up your default mapping you can create a new blank Modul8 project and click ‘copy to project’. Your default mapping will now be saved inside the project file. You can recover your mapping at a later date if you need it by opening the project and clicking ‘copy to default’.
What happens if I have made a default MIDI mapping and then open a project that has it’s own mapping?
This is not a problem you can freely switch between your default and your project mapping. Just be aware if you are in default or project mode before clicking ‘edit’ and making additional mappings.
Can I use multiple MIDI controllers?
The module is only designed to be used with one MIDI device at a time. There may be workarounds to using multiple controllers but this has not been tested.