getting java script error

[high-solutions]

i'm getting a Javascript error as soon as i "connect" with obs:
A JavaScript error occurred in the main process:
Uncaught Exception:
Error: can't decode incoming message: invalid type tag in incoming OSC message, must start with comma
at Socket. (/Applications/OBSosc.app/Contents/Resources/app/node_modules/node-osc/dist/lib/Server.js:29:23)
at Socket.emit (events.js:315:20)
at UDP.onMessage [as onmessage] (dgram.js:910:8)

any idea if i did something wrong?
It is a great great super great app if it works, the osc syntax looks amazing to work with but i can't get past this error.

I'm even getting this error when no other OSC apps or OBS is running

[jshea2]

Hey! Are you on Mac or PC? Also, What application are you using? I had someone report the same exact issue using MultiPlay. We found out that that software sent bundled OSC messages. So OBSosc couldn’t decide it. He had the developer send OSC unbundled and worked fine.

On Sat, Feb 20, 2021 at 4:12 PM high-solutions ***@***.***> wrote: i'm getting a Javascript error as soon as i "connect" with obs: *A JavaScript error occurred in the main process:* Uncaught Exception: Error: can't decode incoming message: invalid type tag in incoming OSC message, must start with comma at Socket. (/Applications/OBSosc.app/Contents/Resources/app/node_modules/node-osc/dist/lib/Server.js:29:23) at Socket.emit (events.js:315:20) at UDP.onMessage [as onmessage] (dgram.js:910:8) any idea if i did something wrong? It is a great great super great app if it works, the osc syntax looks amazing to work with but i can't get past this error. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#4>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AQ4ANIDTK4UKJZYOQLV2M5DTABFX7ANCNFSM4X6MLALQ> .

-- Thanks, Joe Shea (402) 669-2651 joe.daniel.shea@gmail.com

[high-solutions]

Sorry, ofc i should have said I'm running on mac.

I'm using OSCulator and bitfocus companion (and also tested with qlab)
The strange thing is that if I close everything osc related I stil get this message but only on specific ports, so in the range 3333 to more or les 3380 (probably al in the 3000 or 3300 range).

When i switched to 7070 and 5000 it was gone. I will research some more this evening.

By the way, if i let OSCulator listen on port 3333 when obsosc is closed there is nothing coming in

[jshea2]

Hmm interesting.. I know if port 3333 is in use with another software, using 3333 in OBSosc can't bind

[jshea2]

I will test with OSCulator and Bit companion later. I've only tested OBSosc with QLab, Open Stage Control, and Isadora

[high-solutions]

Yeah but i'm not sure what could be running on port 3333, and its not only port 3333. But for now the issue is fixed. Only looking how to change the deffault settings for the port and password, but have to look in to that yet

[jshea2]

You can probably hard code change the defualt values in the HTML file located in...
Show Package Contents > Contents > Resources > app > src > index.html
Just change the "value" for the one you want and save. (OSC IN Port is on line 32)
Port: <label for="oscinport"></label> <input type="text" id="oscinport" value="3333" size="5">

[high-solutions]

Thanks! worked like a charm!