Standalone mode gives you more freedom to go anywhere with your I-CubeX setup ! Configure any of the I-CubeX digitizers with the Editor and it will remember the settings after power down.
12 Nov 2014: I-CubeX
Editor v3.51 incl. BlueMIDI v1.60 (Windows). The Editor installer will download & install Java 7 update 71, if needed. If you have Java 8 already installed, you don't need to install Java 7. Most drivers, incl. Virtual MIDI port drivers, need to be downloaded separately.
Check the download archive for older releases. A MacOS version is available. For source code, please contact our tech support. Not the right solution ? We have more software.
- Windows 8, 7, Vista or XP.
- Java 7 or higher.
- MIDIYoke, LoopMIDI or LoopBe30 virtual MIDI port drivers.
- A digitizer with firmware v4.1 or higher, including applicable drivers, is required. Some drivers are included in the Editor installation package.
Installation and user manuals, tutorials and tips
- Digitizer quickstart documentation can be found on its product page.
- USB-microDig quickstart documentation can be found on its product page.
- Wi-microDig quickstart documentation can be found on its product page.
- When you encounter problems configuring a Wi-microDig with the Editor via BlueMIDI, re-plug the bluetooth adapter (if possible), make sure the Wi-microDig batteries are fully charged, re-power the Wi-microDig and then restart the Editor.
- When using a wireless digitizer in standalone mode, setup communication through a virtual MIDI port using the "Connections" dialog in "Configure" menu, and BlueMIDI (configured using the same virtual MIDI ports). BlueMIDI is included in the editor installation package. When asked by Windows about pairing, enter "1" as the passkey.
- When using a wireless digitizer in host mode with a 3rd party software, communicate using just the Bluetooth serial port, or via the BlueMIDI application (included in the editor installation package) using a virtual MIDI port - no need for the Editor. If using multiple wireless digitizers (upto a maximum of 7) run a separate instantiation of BlueMIDI for each wireless digitizer.
- For MIDI mapping select any of the MIDI messages from the "Mapping" pull-down menu in the Sensor window. Set the MIDI device to output MIDI data to using the "Connections" dialog in the "Configure" menu.
- Before installing MIDIYoke on Windows Vista or 7, UAC (User Account Control) must be turned off (Windows Vista) or set to "never notify" (Windows 7). In Windows 8 install MIDIYoke by selecting Properties, Compatibility, "Run this program in compatibility mode for:", "Previous version of windows".
- If your MIDI interface isn't listed in the connections pane, add it by selecting your MIDI interface in the "Add MIDI Interface" dialog. Remove these new entries by deleting the files starting with "Custom..." in UsersAppDataRoamingInfusion SystemsICubeX editor.
- Virtual Joystick mapping is available if the Virtual Joystick driver is installed (select it during the editor installation). Select this mapping from the "Mapping" pull-down menu in the sensor window. Use any of the "VJ - Analog" channels for high resolution mapping and any of the "VJ - Digital" channels for binary mapping. The monitor values will change according to the selected mapping. Set the maximum joystick value using the "Joystick range" dialog in the "Configure" menu.
- When recording sensor data, the storage format is: "timestamp in ms", "sensor1 value", "sensor2 value", ... , "sensorN value", where N is the number of inputs of the digitizer, timestamp = 0 at the moment data recording is started in the editor and where the minimum sensor data value is 0 and the maximum is 127, unless pitchbend is selected as MIDI map in the sensor window in the editor, in which case the maximum value is 16383.
- To remotely start and stop sensor data recording for better time synchronisation with other software, check "Remote" in the "Recording" dialog (under "Window"), and run (in C:Program FilesI-CubeX editor) "StartRecording.exe" or "StopRecording.exe" from the DOS command prompt or from within the 3rd party software.
- To start the editor from the command line automatically after booting the machine follow the instructions in "Start editor on boot up.txt" in the folder where the editor is installed.
- The default browser has to be set in order to be able to click on links in the news section at the top-right of the editor.
- Debug information is available in the toolbar by clicking on the message window at the top right of the editor while holding down the CTRL key.
- Mapping: map sensor values to a virtual joystick for use in gaming and other applications, map sensor values to any MIDI channel voice type message ie. note-on/off, key-pressure, control-change, program-change, after-touch (all 7 bit resolution) or pitch-bend (12 or 10 bit resolution, but only available for at most 16 sensors - each one on a separate MIDI channel). Virtual MIDI driver routing for each digitizer. All mapping is stored in editor configuration files (.cfg and .icu).
- Sensor data processing: inversion (increasing sensor values result in decreasing MIDI data values), thresholds (the sensor values within the specified range are offset and scaled to the MIDI data output range), zooming (set the sensitivity of an input to a specific voltage range), averaging (reduce noise by averaging over up to 16 sensor values), differentiation (output only the difference between two successive sensor values), peak/dip detection (detect the largest/smallest value of up to 16 sensor values over time and output it, or a preset value), noise gate (output only when the sensor value changes more than a user-set difference from its current value).
- Gesture recognition: gesture onset detection (through peak or dip detection mapped to e.g. note-on event with velocity value corresponding to peak or dip value), post-onset processing (continuous averaging and/or differentiation, mapped to e.g. after-touch or pitch-bend messages), gesture end detection (sensor value above/below threshold, mapped to e.g. note-off event).
- Actuator output control (Digitizer and USB-microDig only): trigger/toggle (outputs turn on/off with one MIDI message or turn on with one MIDI message and off with the next one), power-up initialization (set the outputs to on/off upon power up), output mapping (outputs respond to note-on/off, control-change or key-pressure messages), threshold (set the MIDI value beyond which the output turns on/off.
- Configuration management: edit, save, load, name and manage configurations involving multiple digitizers, with integrated MIDI, USB & Bluetooth connections configuration, sensor presets for easy setup, real-time viewing and (remote) recording of sensor data to file, control of active sensing and running status, and LBNL, a factory reset option allows you to return all digitizer settings to its original settings when it was first shipped to you. Start the editor or BlueMIDI from the command line with the I-CubeX configuration file of your choice for easy installation automation.
- Compatible with MIDIYoke, LoopMIDI and LoopBe virtual MIDI port drivers
- Connection via BlueMIDI for Wi-microDig
- Useful default directories
- Data recording, remote or manual
- Use any MIDI interface with the editor
- Start editor from command line with configuration file (.icu)
- Last connection autosave and autoconnect features for BlueMIDI
- Support for USB-microDig(s)
We are aware of the following bugs/problems at this time:
- If you are running the Editor on Windows 7 with a USB-microDig and the Editor shows a popup window saying that the Editor failed to connect with a USB-microDig after having selected File | New or Configure | Reset | Configuration, upgrade Windows 7 with Service Pack 1.
Please notify us if you encounter bugs.