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.
15 Jan 2013: I-CubeX
Editor v3.33 (MacOS X).
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.
- Editor v3.33 requires MacOS X 10.9 (Mavericks), 10.8 (Mountain Lion), 10.7 (Lion) or 10.6 (Snow Leopard) on Intel.
- Run Connect to use a USB-microDig or Wi-microDig with the Editor.
- A digitizer with firmware v4.1 or higher, including applicable drivers, is required.
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.
- 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.
- The Editor v3.33 Bluetooth connection feature has been disabled. Instead, use Connect to represent the Wi-microDig as a virtual MIDI port and then access the Wi-microDig via the virtual MIDI port in the Editor.
- When setting up a wireless digitizer with Connect you may be asked by MacOS for a passkey when pairing: enter "1".
- When you encounter problems configuring a Wi-microDig with Connect, re-plug the bluetooth adapter (if possible), remove and re-install the device entry in the Bluetooth menu, make sure the Wi-microDig batteries are fully charged, re-power the Wi-microDig and then restart the Editor. Rebooting your computer, if you haven't done so recently, will also avoid problems.
- When using wireless digitizers (upto 7) with a 3rd party software, communicate using just the Bluetooth serial port, or via the Connect application using a virtual MIDI port - no need for the Editor.
- 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 by 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.
- See also Apple's Bluetooth FAQ.
- 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 last but not least, a factory reset option allows you to return all digitizer settings to its original settings when it was first shipped to you.
- Mountain Lion support.
- Mapping to MIDI ports in the connection dialog.
- Connection via virtual MIDI port for Wi-microDig.
We are aware of the following bugs/problems at this time:
- Once a Wi-microDig has been connected to the Editor using a BlueMIDI MIDI port, it's not possible to connect a different Wi-microDig to the same BlueMIDI port and then use this same BlueMIDI port in the Editor. The Editor has to be restarted to connect to the different Wi-microDig via the BlueMIDI port.
- Wrt. BlueMIDI v2.01, the IAC driver has to be "offline" (see the MIDI window in the Audio MIDI Setup application, in the Utilities folder) for the Editor to recognize BlueMIDI ports. Other MIDI drivers can confuse the naming of available MIDI ports in the "add midi interface" dialog in the Editor.
- If BlueMIDI v2.01 is not started from the Applications folder, only one BlueMIDI port can be created. If multiple ports are needed, make sure to copy BlueMIDI into the Applications folder.
- Wrt. BlueMIDI v2.01, on MacOS X 10.7 (Lion), Cycling '74 Max may not update the available BlueMIDI ports if BlueMIDI is closed and re-opened while Max is open. Multiple of the same BlueMIDI ports will show as available, while only one will actually function.
- When BlueMIDI v2.01 is connected to a Wi-miniDig, the name of the device will be displayed as "Wi-microDig".
- The end user may not be notified that Bluetooth is not on or not available.
- On some machines, you may need to wait until two Bluetooth device searches have completed before actually getting a list of available Bluetooth devices.
- Wrt. 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 due to this issue.
Please notify us if you encounter bugs.