Releases

12 Jan 2010: I-CubeX editor v3.29c incl. BlueMIDI v1.30 (MacOS X Snow Leopard 10.6 on Intel).

12 Jan 2010: I-CubeX editor v3.29c incl. BlueMIDI v1.30 (MacOS X Leopard on Intel).

Check the download archive page for older releases, including for PowerPC. A Windows version is available. For sourcecode, please contact our tech support. Not the right solution ? We have more software.

System requirements

• Editor v3.29c and BlueMIDI v.130 require MacOS X 10.5 (Leopard) or 10.6 (Snow Leopard) on Intel.
• Editor v3.25 and BlueMIDI v1.30 require MacOS X 10.5.x (Leopard) or 10.4.x (Tiger) on Intel/PPC.
• A digitizer with firmware v4.1 or higher, including applicable drivers, is required.


• The microDig and Digitizer require a MIDI interface, eg. a MIDISport interface, with drivers.
• The USB-microDig requires a USB interface and drivers.
• The Wi-microDig requires a Bluetooth interface, eg. the BluetoothAdapter, with drivers.

Installation and user manuals, tutorials and tips

• Digitizer quickstart documentation can be found on its product page.
• microDig 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.
• Note that 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.

More tips:

• 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.
• When using a wireless digitizer in standalone mode, the editor will setup communication through Bluetooth using the "Connections" dialog in "Configure" menu. Click "Search for device(s)", then connect to your device(s). When asked by MacOS, enter "1" as the passkey for pairing. Occasionally, the window for pairing is behind the editor window. Press Tab while holding down the Command key 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.
• 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.
• When recording sensor data, the storage format is: "timestamp in ms", "sensor1 value", "sensor2 value", ... , "sensor32 value", where 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.
• 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 Command key.

Features

• Mapping: 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).
• 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 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 & Bluetooth connections configuration, sensor presets for easy setup, real-time viewing and 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.

Recently added features:

• Support for USB-microDig(s).

Known bugs

We are aware of the following bugs/problems at this time:

• The editor v3.29 (MacOS X 10.6.x / Snow Leopard) may be unreliable wrt. Bluetooth, due to MacOS bugs. We are currently looking into the issue to try and find a workaround.
• With respect to the mechanism for minimizing sensor windows, storing information with sensor position in combination with a loaded image is not functional. The sample .icu files will not work properly because of that.
• The radio button may not work correctly in the connection dialog.
• On Leopard, the end user may not be notified that Bluetooth is not on or not available.
• On some machines, you need two device searches before actually getting a list of devices (e.g. on a PPC using a Kensington Bluetooth adapter).
• Connecting to the Wi-microDig fails on Snow Leopard 10.6.3
• The field for entering the MIDI channel number may be collapsed into a vertical bar on the right of the text "Channel" (in bottom of the sensor panel) so that it seems there is no field to enter the number. However, if you select the vertical bar (using the mouse) and then type two backspaces (to delete any number that would be shown in the field if it weren't collapsed), then type the MIDI channel number you'd like to use and then press enter (or click another field), it will be entered into the field anyways and stored into the digitizer.

Please notify us if you encounter bugs.