Geek asks and answers

Should I use WebRTC or Websockets (and Socket.io) to communicate OSC

I am working on an application that will send OSC control messages, which, as I understand it, a packet of a datagram, from a web page to an OSC receiver (server), such as Max / MSP or Node or any other,

I know that UDP is commonly used because speed is important for the real-time / audio visual control performed with OSC (which is also the work that I will do), but I know that other methods can be used.

Right now, for example, I am sending OSC from the browser to the node.js server (using socket.io) and then from the node.js server to Max (where I end up wanting the data), also using the .io socket. I believe this means that I use websockets and the delays / delays were not bad.

I am curious, although now that WebRTC is absent, if I will post the future of my work there. In all of my work with OSC, I always used UDP and only used the Socket.io/Websockets connection because I did not know about WebRTC.

Any advice on what I should do. In particular, I'm interested in

1. How could I send OSC messages from the browser directly to the OSC server (instead of going through the Node server first)

2. If I have to stay with the Node / Socket.io / Websocket method to send OSC data or Should I look in WebRTC?

+3
source share
2 answers

This is not a question of any particular technical problem, but a problem of discovery. And pretty much an opinion is based.

But I will try to present my thoughts, as others may be useful.

  • If the OSC server supports WebSockets or a WebRTC connection, you can use one of them directly for it.
  • , , , . : http://caniuse.com/rtcpeerconnection, "" .
  • WebRTC . , UDP, , UDP , () .
  • , , WebRTC . , , .

UDP , // , "" , , , "" . WebSockets , , "" - , , .

+3

- Websocket ( OSC) - :

osc-js, UDP/Websocket:

+3

More articles:


All Articles