Reference > OSCAddress constants

Breaking change for 5.2.2

As of GP 5.2.2, OSC addresses must now be bracketed with single or double quotes. This breaking change was introduced as part of a larger change that fixes some previous problems where certain kinds of addresses were not recognized as valid. OSC addresses bracketed with single quotes must be legal and will be validated at compile time. OSC addresses brackets with double quotes will be validated at runtime. This is obviously slightly slower but it allows you to construct OSC addresses dynamically if required.

The address of an OSC message follows a specific format, a quote, a slash followed by alphanumeric characters, possibly repeated multiple times and terminated with another quote.

Examples:

•'/bpm'

•'/device/open'

•'/volume/page1/setvalue'

These are all OSCAddress constants and their type is OSCAddress.

As of GP 4.6, OSC addresses no longer need to be represented as strings with quotes on either side if they are being used with the new OSCAddress type. Note that legacy OSC system functions still require the use of double quotes.