< Back to IRCAM Forum

Spat5 error if OSC message type is string

Spat
#1

We are trying to use Spat for an OSC controlled VBAP mix. Some OSC Message types however seem to be causing troubles. Right now, the following messages are failing for us:

spat5.oper: error occurred when processing "/panning/type "vbap3d"" 
spat5.oper: error occurred when processing "/decoding/type "passthrough"" 
spat5.oper: error occurred when processing "/source/1/mode "mono""

So far, we haven’t had success with an OSC Message of type “string”.
The patch initializes Spat to use 64 sources and 24 speakers and other OSC messages like spat5.osc.print: /source/34/direct/mute 0 seem to work just fine.

We use UnityOSC and Max 8.1.0 with Spat 5.1.5.

Any idea why string messages are causing these errors?

#2

Hi,

These messages are intended for spat5.spat~, not for spat5.oper.
Could this be your problem ? (and not be related to strings, actually)

Best,
T.

1 Like
#3

Hi,

that could be the problem, indeed. The relevant section of our patch looks like this:

grafik
grafik1108×366 120 KB

Would you recommend adding another udpreceive module with a different port number for messages intended for spat5.spat~ or is there an approach where we could send messsages to spat5.oper and to spat5.spat~ on the same port?

Thanks for the quick reply!

#4

I would rather recommend using one single [udpreceive], followed by [spat5.osc.route] or [spat5.osc.ignore] to redirect the appropriate messages to [spat5.spat~]. This should affect only a few messages (like /panning/type); all other messages probably go to [spat5.oper] first.

Also : in your patch, you dont need 64 patchcords from [thru] to [spat5.spat~]. Only one is necessary.
If you can (i.e. if you run Max8), you should try to use MC, that would make your patching a lot easier.

T.

1 Like