Hey guys, here’s the update which adds MIDI Mapping to pipe arguments!
It is still an early iteration of the functionality and it will get improved over time, but we think it’s at a good stage to show it to you guys and hear your opinion and feedback on its usability, what’s missing and how you’d like to be able to use it, so we can know where to focus next!
1.03 Editor downloads
To update the Midihub firmware, switch it on while holding down The Button. In the firmware upgrade mode, all the LEDs should be lit up. Then connect to it with the editor, go to Device->Flash Firmware, pick the downloaded bfw file and hit OK.
* All stored presets will be removed during the firmware upgrade process * - you’ll have to back it up manually by loading each preset and saving them to disk with different names, a ‘data dump’ function to automate this, and to automatically do that during firmware update is planned to be done before the public release.
- MIDI Mapping of pipe parameters.
- Fixed an issue where data could go through in a pipeline when there’s no Output port at the end to the symetrically matching output of what the input was.
- All pipes now have a ‘bypass’ argument (only editable via MIDI mapped controls at the moment). If ‘Bypass’ is set to yes, the pipe is skipped without any processing. If the Input pipe is bypassed, entire pipeline is switched off. If an output pipe is bypassed, the data is not sent to the output port, however, the processing of the data still happens until it reaches the output. (So it’s more efficient to bypass inputs)
- View->Show Tab Bar option on Mac should be gone this time. @thetechnobear
- Properties panel added, which lists all of the selected pipe’s arguments and allows mapping / unmapping MIDI messages to the arguments. (Filter pipe arguments are not mappable, but its ‘Bypass’ is)
- The values still have to be edited via right click or double click on the pipe icons, future versions will have editing implemented via the Properties panel and the dialogs will be removed.