Hai all,
I'm new to Pd (just a couple of days) but already found out how to communicate with my iPad based TouchOSC surface using Pd.
The next step would be to connect to OBS via Websocks and start switching scenes there.

Therfore I need a Pd patch to send eg. 'SetCurrentScene' messages to and receive eg. 'SwitchScenes' messages from OBS.

I found a low level udpclient object at the iemnet library that might do the trick. How ever, I'm no websocks specialist and have no clue how to do the communication with OBS on such a low level.
Further the OBS websock interface requires authentication....!?

Alas, what I would like to have is a wrapper abstract or like that provides an interface like we have with oscparse / oscformat that can be used to commuinicate quite easily using the netsend / netsreceive objects.with OSC devices.

Anybody around that can help me out with that challenge?

Cheers
Harlekin

@Harlekin There is a free "man-in-the-middle" app for windows and osx that will connect to the OBS websocket (also dealing with authentication) and make OSC ports available....... which you could then use with [netsend] and [netreceive] on the local network....... https://obsproject.com/forum/resources/osc-for-obs-app.1222/
That's probably the easiest solution given the OBS websocket protocol is proprietary.
The OBS websocket can be set as open...... by not setting a password.... but the proprietary protocol would be a headache when building a Pd external.
David.

@whale-av Right, I was in contact with the author of OSC4OBS already and we have extended the OSC4OBS node based JS like code to work nicely with TouchOSC.
However that code is rather limited and I was looking to get TouchOSC working with Pd directly to avoid extending this interface even further.
I have no idea how difficult it would be to write an external to connect with OBS.
There are very good python libraries already that handle all the OBS websocket stuff and one of those may be used to create such an external instead of building one from scratch using only low level IP protocols...
Cheers
Harlekin

@Harlekin If you want TouchOSC to control OBS you don't need Pd....... just connect TouchOSC directly to the ports of osc4obs and make your remote.touchosc layout file.

If you want to do some other processing in Pd then connect TouchOSC to Pd directly (in and out)...... and then connect your processed control from PD to osc4obs directly (in and out).
osc4obs facilitates that by creating separate OSC in and out ports.
You will have to do that also if you want to use TouchOSC and Pd in an either/or situation as osc4obs only has one set of osc ports and is making a tcp connection with OBS.

OBS websocket is a tcp connection and so it is possible that osc4obs is requiring tcp for the OSC connections...... in which case remove the -u flag from [netsend] and [netreceive] in my examples below.
It could also be expecting ascii instead of binary in which case remove the -b flag (but I doubt that)....

Externals for Pd are written in C so if you are adept there is some help in Pd/doc/6.externs .....
Basically you need to make a websocket client that replicates osc4obs with outlets and inlets instead of the osc ports.

BUT... you could try the iemnet [tcpclient] first (NOT the [udpclient]...!).... and that should work.
Just replace both [netsend] and [netreceive] with the one [tcpclient]...... connect it to OBS and look at the output using a [print] object.
If OBS is on the same computer the connect message will be [connect 127.0.0.1 4444(
Remove the password from the OBS websocket unless you find that a password can be added to the [connect( message for [tcpclient]...... before or after the port number? preceded by "password" or "passwd"?...... guesswork...... and [tcpclient] might well not accept a password as it is not mentioned in the help file.
Once you are looking at a print of the received messages the problem will be to decode the proprietary message format (it will not be OSC)....... it might be easy.... or not.
If lucky there will probably be the ascii strings you are looking for or a decimal representation of them somewhere in the message.

If you go the osc4obs route then it is quite easy to use [oscformat] and [oscparse] in vanilla instead of creating an external.......
...... vanilla osc.zip

P.S. try to avoid integers within the OSC address (header) as they arrive in Pd as symbols at the output of [oscparse] ....... and are then difficult to route. So what/ever/6 data is best avoided if possible and what/ever/six data is easier to deal with in Pd...... but I have included a solution in the zip file above.

Be careful in TouchOSC to avoid message feedback (much like midi feedback)......... and the same applies in Pd. In Pd you can include "set" at the start of a message (without the quote marks)...... which will set a message in the next object or message box but not send it onward until that object or message is banged.
David.