Visual Productions forum

Products => CueCore, QuadCore, IoCore, TimeCore & B-Station => Topic started by: soprani on November 26, 2014, 05:44:59 PM

Title: OSC Path limitations
Post by: soprani on November 26, 2014, 05:44:59 PM
Hi

Want to ask about limitations on pathname for OSC Messages.

I have a couple of IoCore
Firmware 1.09
vManager 1.3.72

What i want to achieve:
on GPI in, i want to send an OSC message, that per se is no problem.
The problem that ruins my project is that the receiver of the OSC message requires a path  (adr) longer than 14 characters that seems to be the limitation.
The path for this device is /control/xxx/play with a float of 1.0, whirr xxx is anything, but has to be at least one character, like this path for example.
/control/a/play      ==   15 chars :(

Is there a reason for the 14 character limitation.

This is for controlling a Visionmixer for TVShow, Next week. ;)

Best regards
Olle Soprani
Swedish Television
SVT
http://svt.se
Title: Re: OSC Path limitations
Post by: Maarten Engels on November 27, 2014, 03:23:34 PM
Hi Olle,

We have recently expanded the OSC string length limitation to 22 chars (this is as far as we can go memory wise). Please upgrade your IoCore to firmware v1.32 or higher.

Please use vManager v1.3.79 or higher to perform the upgrade. This release is available from ftp://haarlem.visualproductions.n/releases (ftp://haarlem.visualproductions.n/releases).

cheers,
Maarten
Title: Re: OSC Path limitations
Post by: soprani on November 29, 2014, 08:58:53 PM
Great!

That made my day.

/olle
Title: Re: OSC Path limitations
Post by: soprani on January 11, 2017, 09:50:24 AM
Hi

Just to follow this up. This made it possible for us to use the ioCore as a vital part of the Graphics/Voting flow in Eurovision Song Contest 2017 in Stockholm.
 :)
/olle
SVT