31–40 of 128 posts
I'm not very familiar with WebRTC & how the browser pulls video usually, in what way is this better? Also, what benefits does WebRTC give over other protocols?
What other protocols do you know that offer low latency almost real time video and all that in the browser? There is RTSP but that does not work in browsers.
I'm not very familiar with WebRTC & how the browser pulls video usually, in what way is this better? Also, what benefits does WebRTC give over other protocols?
I've seen a few WebRTC server implementations pop up recently but the only clients I have seen are web browsers. Does anyone know of any WebRTC client implementations apart from the browser? Or am I misunderstanding the WebRTC architecture completely?
How the world has changed that running something on a raspberry pi counts as "embedded". I was expecting this to be on some microcontroller...
And in the same vein : settopboxes are considered embedded. TiVo's are.
Right now, I am not aware of any cheap ip camera that can stream its H264 video to a regular web browser, with sub 500 ms latency. All manufacturers seem to have moved to an app, I guess they can show an RTSP stream in that way.
Older ip cameras had MJPEG which you could view in the browser, but that is really inefficient w.r.t. bandwidth.
I've seen a few WebRTC server implementations pop up recently but the only clients I have seen are web browsers. Does anyone know of any WebRTC client implementations apart from the browser? Or am I misunderstanding the WebRTC architecture completely?
The official one, pion (go) and webrtc-rs (rust) can all be used on both sides.
Earlier quoted context omitted.
... how is STUN pure p2p ? you still need to have a STUN server somewhere no ?
You can just use google stun servers they are free to use
Earlier quoted context omitted.
... how is STUN pure p2p ? you still need to have a STUN server somewhere no ?
STUN is just for punching holes in your NAT router, and also discovering what is your public IP address. Both things will be needed for the other peer to know where to reach you. And the other way around. Once this NAT thing has been done by both parts, and the actual communication has started directly P2P, STUN is not needed any more.
Earlier quoted context omitted.
WebRTC with STUN is pure p2p where ffmpeg it requires a rtmp or rtsp server
... how is STUN pure p2p ? you still need to have a STUN server somewhere no ?
I think the question of what's "pure" p2p is somewhat academic. If your app uses DNS, is it p2p, isn't DNS just a distributed p2p database? Does p2p require that every aspect of your app right down to discovery is distributed among nodes running your app? Is it cheating to use an existing DHT? etc.
This would be interesting to integrate into https://github.com/openmiko/openmiko which is a firmware for the T20 based ip-cameras. Right now, I am not aware of any cheap ip camera that can stream its H264 video to a regular web browser, with sub 500 ms latency. All manufacturers seem to have moved to an app, I guess they can show an RTSP stream in that way. Older ip cameras had MJPEG which you could view in the brows…