Note: This version is not anymore compatible with Tiger or PowerPC computers.
OSC improvements:
- OSC routes are now independent of the target device.
- A table now shows the OSC devices detected on the network. This is useful for example to see if TouchOSC is correctly connected.
- It is possible to register manually an OSC message by typing its address. Check “Manually Create Message …” in the Routings menu.
- It is possible to edit a copy of a OSC routing that has been created automatically after back-mapping.
OSC routing improvements:
- The OSC route editor has been improved.
- use the asterisk character in a rewrite address to replace this character with the input address. For example, suppose you want to prefix every incoming messages with “/blue” type in the rewrite address “/blue*”. If the message “/1/fader1″ has this OSC route assigned as an event, its address will be rewritten as “/blue/1/fader1″.
- As an experimental feature, it is now possible to send OSC messages whose argument is a string selected from a list. This can be very useful to update labels in TouchOSC. Let’s consider a message named “/1/fader1″ sending values from 0.0 to 1.0. If you create an OSC route, and change the routing arguments to something like (Sine,Square,Tri,PWM) an OSC message will be sent with the argument being “Sine” for values going from 0 to 0.25, “Square” for values going from 0.25 to 0.5, “Tri” for values going from 0.5 to 0.75 and “PWM” for the rest.
- Import and export of a set of OSC Routes, the same way as Key Combos. You can also import a TouchOSC file, by using the Import menu or by dropping it on the OSC Routes table.
Back-mapping improvements:
(Back-mapping is the name given to the automatic configuration process that sets up the bi-directional communications between two devices.
For example, let’s consider a message with address “/1/fader1″ that is configured to send a MIDI Control Change. If the same MIDI Control Change is received, it will be configured to send OSC messages back to “/1/fader1″.)
- if multiple events are configured with the same target, multiple back-mappings are created. For example, if you use TouchOSC and have two faders “/1/fader1″ and “/2/fader10″ that are configured to send events to MIDI CC 1, when this same control change is received, the two faders will be updated as they should.
- new MIDI back-mappings are supported :
- Control Changes (improved)
- Pitch Wheel
- Channel Pressure
- As a bugfix, the scalings are now taken in account properly. It allows for example allows to use the X/Y control of TouchOSC in vertical orientation.
MIDI Improvements:
- In the scalings window, Input and output scalings are displayed on a 0-127 range to match MIDI’s units.
- OSCulator can now send and receive MIDI from physical ports without the use of additional software.
- New Event: “Channel Pressure” located under the “MIDI Note” type. It corresponds to the MIDI message with status byte 0xD0. Note: on some programs like Live, it is mistakenly recognized as Aftertouch.
- Raw MIDI data registered in the main window can be routed to any available physical or virtual MIDI output.
Miscellaneous changes:
- The preference option “Start Wiimote discovery upon launch” is now set to off by default.
- Added a checkbox to enable sending of the Wiimote battery status.
- A list of pre-canned commonly used keyboard combos has been added to the “gear” menu in the Key Combo Parameters view.
- Renamed “Latched Enable” to “Enable”.
- Renamed “Toggled Enable” to “Enable Toggle”.
- Renamed “Latched Trigger” to “Enable Combine”.
- Renamed “Timbre” in MIDI Note w/ Params to “Aftertouch”.
- KeyCode Helper window now displays with keyboard shortcut Command-Shift-K.
- You can flip between Routings and Scalings pages with Command-F.
- Copy / Paste on the main window has been improved.
- Some care has been given to the table headers sorting.
