Releases

10 May 2008: I-CubeX editor v3.31 incl. blueMIDI v1.55 (Windows)

If you encounter any problems with this version you can try I-CubeX editor v3.15 incl. blueMIDI v1.50 (Windows)

Check the Download page for older releases. A MacOS version is also available.

If you are interested in modifying the editor or if you need source code to develop software tools to deal with I-CubeX sensor data, please contact our tech support.

Improvements in this version

• Support for USB-microDig(s)
• Improved connection dialog, eg. when searching for Bluetooth devices, found devices get listed more rapidly
• Automatic pairing with a Bluetooth device (ie. pairing no longer requires entering "1")
• BlueMIDI is compatible with new definition of MIDI yoke
• Routing to a virtual MIDI port is no longer exclusively to BlueMIDI or MIDI yoke ports
• Better splash screen and I-CubeX editor icon

System requirements

The editor v3.3x and blueMIDI v1.5x have been confirmed to run properly on Windows XP and Vista. A digitizer with firmware v4.1 or higher is required.

Installation notes

On Windows Vista, BEFORE installing the editor with blueMIDI (ie. when you plan to use a wireless digitizer) please do the following:

1. Run "MSCONFIG" from the Run-menu (Win+R).
2. Go to the "Tools"-tab and select "Disable UAC".
3. Press "Launch". Close the CMD-window.
4. Restart your computer and install the editor.

Manuals, tutorials and tips

We will soon post more supporting documentation for the USB-microDig.

For the Wi-microDig, here are (Windows / MacOS X) quickstart docs to get you up and running with the Wi-microDig. For the microDig and Digitizer, use the v2.5 editor manual.

A few essential notes wrt. this version of the editor:

• When using a wireless digitizer in standalone mode, the editor will setup communication through Bluetooth using the "Configure | Connections" dialog. Click "Search for device(s)", then connect to your device(s). When asked by Windows, enter "1" as the passkey for pairing. Occasionally, the window for pairing is behind the editor window. Press Alt-tab during the "Connect to Device" process to make it appear.
• 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.
• MIDI mapping: Select any of the MIDI messages from the "Mapping" pull-down menu in the sensor window. When using a wireless digitizer set the MIDI device to output MIDI data using the "Configure | Connections" dialog.
• Virtual Joystick mapping: 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 "Configure | Joystick range" menu item.
• 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 "Msg2ICubeX /start" or "Msg2ICubeX /stop" from the DOS command prompt or from within the 3rd party software.
• Debug information is available in the toolbar by ctrl-clicking on the message window at the top right of the editor.
• When you encounter problems configuring a Wi-microDig with the editor, 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.

Features

• 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.

Known bugs

We are not aware of any bugs/problems at this time. Please notify us if you encounter any.