Hi,
I'm trying to connect real time data in Houdini through websockets.
There's no websocket node in Houdini unlike in Touch Designer.
The closest I can get is the mocapstream node.
I'm able to connect through it but it errors out because I don't know what data format it accepts.
By any chance, does anyone have a sample data of it or at least what it looks like?
A json format with the respective values and keys?
How to Hijack Mocap Stream Node?
585 6 1- bentraje
- Member
- 16 posts
- Joined: Sept. 2019
- Offline
- edward
- Member
- 7722 posts
- Joined: July 2005
- Online
What data are you sending it? If it's some custom thing, then "Raw UDP Data" is the only option here:
(https://www.sidefx.com/docs/houdini/nodes/sop/kinefx--mocapstream.html [www.sidefx.com] )
(https://www.sidefx.com/docs/houdini/nodes/sop/kinefx--mocapstream.html [www.sidefx.com] )
Raw UDP Data
This can be useful for prototyping streaming from new devices. All it does is start a UDP server on the given port, and output the most recently received packet’s contents in the data detail attribute. This is a common protocol for mocap data, you could wire this into a python SOP to parse the data and output a skeleton.
Note that the node will likely recook slower than you are receiving the packets so this approach doesn’t work if you need to read every packet, or if there’s state to keep track of across multiple packets. To accomplish this, you can create a C++ plugin.
- bentraje
- Member
- 16 posts
- Joined: Sept. 2019
- Offline
edward
What data are you sending it? If it's some custom thing, then "Raw UDP Data" is the only option here:
(https://www.sidefx.com/docs/houdini/nodes/sop/kinefx--mocapstream.html [www.sidefx.com] )Raw UDP Data
Thanks for the response.
My bad on not specifying it. The above screenshot already uses RAW UDP Data but it still gives an "Error Receiving Data". Presumably because the data format is not as expected.
How do I go about it?
- edward
- Member
- 7722 posts
- Joined: July 2005
- Online
- bentraje
- Member
- 16 posts
- Joined: Sept. 2019
- Offline
No, I'm not sending data back.
Just receiving data from the websockets.
RE: RAW UDP DATA.
Okay. I messed this one up too. Sorry about that.
I'm using the RAW TCP Data. I thought they were the same as they were next to each other.
Just to confirm it's not possible to connect to TCP Data? Only in UDP Data.
I'm new to this so I'm not sure how to set-up a UDP Data.
All websockets tutorial seems to point out to TCP Data (i.e. requires a local host and a port).
With the UDP data, it only requires port. and when I tried to input the port on my server, it doesn't connect (i.e. waiting for connection)
Just receiving data from the websockets.
RE: RAW UDP DATA.
Okay. I messed this one up too. Sorry about that.
I'm using the RAW TCP Data. I thought they were the same as they were next to each other.
Just to confirm it's not possible to connect to TCP Data? Only in UDP Data.
I'm new to this so I'm not sure how to set-up a UDP Data.
All websockets tutorial seems to point out to TCP Data (i.e. requires a local host and a port).
With the UDP data, it only requires port. and when I tried to input the port on my server, it doesn't connect (i.e. waiting for connection)
- edward
- Member
- 7722 posts
- Joined: July 2005
- Online
Sorry, the Mocap Stream also has the Raw TCP option. Websockets is this whole thing on top of TCP that requires handshaking, which the Raw TCP option doesn't support (it can only receive from the device, not send to it).
I think that if you need Websockets, then it's either your own Python SOP (with Maintain State enabled) using some python websocket client to parse it. Or for speed, a C++ Mocap Stream plugin.
I think that if you need Websockets, then it's either your own Python SOP (with Maintain State enabled) using some python websocket client to parse it. Or for speed, a C++ Mocap Stream plugin.
Edited by edward - March 20, 2024 17:55:41
- bentraje
- Member
- 16 posts
- Joined: Sept. 2019
- Offline
-
- Quick Links