Differences

This shows you the differences between two versions of the page.

--- osc-support [2021/12/14 17:02] – [Enabling and Configuring OSC] shane
+++ osc-support [2023/05/08 18:59] (current) – external edit 127.0.0.1
@@ Line 19: / Line 19: @@
 To enable Unify to listen for OSC commands, the least you need to do is to check the "Enable" box.
-If you wish, you may also adjust the //portNumber// and/or //ipAddress// settings. You must **disable** OSC (un-check the "Enable" box) before editing these values, then **re-enable** (check the box again) to accept the changes, and finally **re-start Unify** for the changes to take effect.
+If you wish, you may also adjust the //portNumber// and/or //ipAddress// settings. **You must //disable OSC// (un-check the "Enable" box) before editing these values, then //re-enable OSC// (check the box again) to accept the changes, and finally //re-start Unify// for the changes to take effect.**
   * The default //ipAddress// "0.0.0.0" (shown as "ANY IP") configures Unify to listen on ALL available network interfaces.
     * If you want it to listen only for //local// connections, from other programs on the //same computer//, change this to "127.0.0.1".
@@ Line 25: / Line 25: @@
   * On most computers, the default //portNumber// 9001 should not interfere with any existing network services.
     * If you need to change it, you'll need to determine a suitable port number, between 1024 and 65535.
-  * Changes you make will only take effect after you save and close the file, then re-open Unify.
+  * Changes you make will only take effect after you quit Unify, then re-start Unify.
+**On Windows**, the first time you re-start the Unify stand-alone app after enabling OSC, a pop-up window will appear, asking you if it's OK to allow network access:
+{{::osc-2.png|}}
+The recommended setting (allow Unify to communicate on Private networks only) should already be selected. Click the **Allow access** button to confirm it.
 ===== OSC message types =====
@@ Line 81: / Line 87: @@
 Note the reversed byte-order, and how 3-byte MIDI messages are encoded as 4-byte integers. (2-byte MIDI messages are encoded the same way, but the ''byte3'' value will be 0.)
+==== OSC messages to embedded Unify instances ====
+**As of Unify v1.9**, it is possible to direct OSC commands to specific embedded Unify instances. The required path syntax is similar to that for sending parameter-update messages to plug-ins, but the word //unify// is used instead of //plugin//, and this is followed by the OSC command to be sent to the Unify instance.
+For example, to send the command ///master/mixLevel// to an embedded Unify instance on layer INST1, the full OSC path would be ///inst/1/unify/master/mixLevel//.