We can output OSC to multiple addresses easily and quickly with minimal setup time. Giving all the particular functionality that the receiver will expect to see.

Within the OSC tab we use the ‘+’ to create the destinations, those will be the audio engines or other OSC capable devices we want to connect to, and provide positional data to. 

Above, we had added 4 audio engines and their relevant target IP address and port number. The destination name can be changed freely.

We can enable/disable each using the checkbox.

Message Prefix / Message Postfix

The OSC string / message can be written freely (prefix and postfix) or choose a destination preset from the drop-down. This allows us to connect easily to the engine, server of familiar brands or OSC standards such as ADM, see below – 

In almost all cases, the people you wish to connect with should be able to tell you the string/message they expect to see.

ID as 1st Argument

Any OSC string is a series of arguments, some destination devices will expect to see the OSC as the first of those arguments. This checkbox enables that, as you can see in the below example – The OSC monitor shows us this first argument is ID 11, followed by the usual arguments you’d  expect to see, in this case the XYZ integer values.

Mode

A simple toggle between 2D and 3D, the overall majority of immersive audio will be 2D.

Type

This allows us to toggle between Float values or integer (absolute metres) we’ll be sending out. Float values offer a higher resolution value.

Limit between

This is limiting the output between ‘value 1’ and ‘value 2’. If your target is at -5m but the audio engine doesn’t accept any input below -2m, then FM can limit the output to -2m. You can do that in other places, like the target limits, but it would impact global tracking, not just the OSC output for audio.

In general, leave those OSC limits empty, we doubt any audio engine would encounter real issues if their input is outside of a specific range. 

Destination’s Origin

If the origin for Follow-Me & the origin for the audio world are not the same. This setting allows us to match the audio origin by entering a position for that OSC output origin. If Follow-Me arrive to site after the audio team, you can either make our shared/global origin match theirs during Follow-Me setup, or simply use a different Follow-Me origin position and use this setting for the OSC connections.

Destination’s Scale

Follow-Me will output absolute values in metres for absolute positioning. Should relative positioning be needed, we can scale the destination to provide that position. It should be a value between 0 and 1. For example, x = 0.5 and y = 0.2.

Rotation

Follow-Me works using this coordinate orientation system (black dot is the Origin) –  

Other systems can sometimes work using alternative coordinate orientation such as d&b – 

So we can use the rotation to orientate correctly, so in the above d&b example we enter 90 degrees in the Z rotation field to rotate the X-axis pointing into the audience.

With all our information entered we create mappings using the ‘+’ as seen below, the ‘OSC Connection’ name can be changed freely –  

We can give it an OSC-ID so it can be identified at the destination end.

Highlighting that particular mapping, we can then choose from the relevant drop down to which Target or Tracker to assign it to. Assigning it to a Target (rather than a Tracker) will allow you to takeover manually if something goes wrong assuming you have Follow-Me mouse console(s) in the system.

After this, simply start OSC and the destinations should be seeing the data – 

The Setup tab can allow you to start OSC on StartUp – 

We recommend the free ‘Protokol’ app by Hexler to monitor and check your OSC is setup and outputting correctly – PC, Mac, Tablets and Smartphone compatible.

Have a great install & reach out to us if you need help!

Your Follow-Me team.