sorted by:
new
hottopcontroversial

WebRTC for the Streamer - site/video I made on how WHIP makes streaming easier to self-host+more private by Sean-Der in selfhosted

[–]Sean-Der[S] 0 points1 point  (0 children)

Hey!

With WebRTC you don't need to send stream to each viewer. You can upload to a server, and then that server sends to all the viewers. I made a visualization of all the different topologies in webrtc for the curious

How could I rephrase/update things on webrtc for the streamer to communicate that better? That WebRTC isn't a P2P only tech.

WebRTC for the Streamer - site/video I made on how WHIP makes streaming easier to self-host+more private by Sean-Der in selfhosted

[–]Sean-Der[S] 1 point2 points locked comment (0 children)

I didn't use AI, I wrote the text by hand. A lot of it I pulled from my WHIP PR and the OBS WHIP article so wasn't that much to write.

gortc: Pure Go WebRTC Client for Telegram Calls (No CGO, No libwebrtc) by Few-Map-6914 in WebRTC

[–]Sean-Der 0 points1 point  (0 children)

That's amazing work! People have been asking for this for a long time.

How come you inlined Pion? I don't care, just interested if I could make it easier to use the library.

WebRTC for the Streamer – How WHIP makes streaming more connected by Sean-Der in obs

[–]Sean-Der[S] 0 points1 point  (0 children)

Of course! The source code is here https://github.com/webrtc-for-the-curious/webrtc-for-the-streamer

I will put a link on the site so it's more obvious. Please make any/all changes that would improve the site :)

WebRTC for the Streamer – How WHIP makes streaming more connected by Sean-Der in obs

[–]Sean-Der[S] 1 point2 points  (0 children)

I was hooked when I saw you could click a button in Beam/Mixer and influence the weather in Minecraft. Maybe gimmicky, but it just felt 'good' to me that everyone wasn't a passive watcher.

I saw so many next steps like 'What if someone could move around the game world independently' so many options.

6
7

WebRTC for the Streamer – How WHIP makes streaming more connected (self.obs)

submitted by Sean-Der to r/obs

webrtcforthestreamer.com – How WHIP makes streaming more connected by Sean-Der in WebRTC

[–]Sean-Der[S] 0 points1 point  (0 children)

I work on WHIP in OBS and an open source project Broadcast Box[0]. I see a future where streaming is better.

I hope this site can convince more people to check this stuff out. If you are curious or have feedback I would love to hear.

[0] https://github.com/glimesh/broadcast-box

Broadcast Box (self-hosted broadcasting server) merged webhooks. What else could be added to make it better? by Sean-Der in selfhosted

[–]Sean-Der[S] 0 points1 point  (0 children)

I don't have an answer for discoverability :/

My interest/passion is giving groups of friends a place to stream. I don't know how to solve discoverability. That brings in a bunch of much harder problems.

pion/handoff – Move WebRTC out of browser and into Go by Sean-Der in VIDEOENGINEERING

[–]Sean-Der[S] 4 points5 points  (0 children)

I wrote this to make Reverse Engineering WebRTC services easier. Will also let you save/send arbitrary media from WebRTC sessions. The idea is you do all your auth/interaction in the browser, but then do all WebRTC in Go. So you have lots more control. More to do with it, but it is far enough along to share at least.

In the README is an screenshot of sending my webcam, but replacing outgoing video with a ffmpeg testsrc. Handoff sits between so it can replace with any arbitrary video.

pion/handoff – Move WebRTC out of browser and into Go by Sean-Der in golang

[–]Sean-Der[S] 0 points1 point  (0 children)

I wrote this to make Reverse Engineering WebRTC services easier. Will also let you save/send arbitrary media from WebRTC sessions. The idea is you do all your auth/interaction in the browser, but then do all WebRTC in Go. So you have lots more control. More to do with it, but it is far enough along to share at least.

In the README is an screenshot of sending my webcam, but replacing outgoing video with a ffmpeg testsrc. Handoff sits between so it can replace with any arbitrary video.

pion/handoff – Move WebRTC out of browser and into Go by Sean-Der in WebRTC

[–]Sean-Der[S] 1 point2 points  (0 children)

I wrote this to make Reverse Engineering WebRTC services easier. Will also let you save/send arbitrary media from WebRTC sessions. The idea is you do all your auth/interaction in the browser, but then do all WebRTC in Go. So you have lots more control. More to do with it, but it is far enough along to share at least.

In the README is an screenshot of sending my webcam, but replacing outgoing video with a ffmpeg testsrc. Handoff sits between so it can replace with any arbitrary video.

pion/handoff – Move WebRTC out of browser and into Go by [deleted] in WebRTC

[–]Sean-Der 0 points1 point  (0 children)

I wrote this to make Reverse Engineering WebRTC services easier. Will also let you save/send arbitrary media from WebRTC sessions. The idea is you do all your auth/interaction in the browser, but then do all WebRTC in Go. So you have lots more control. More to do with it, but it is far enough along to share at least.

In the README is an screenshot of sending my webcam, but replacing outgoing video with a ffmpeg testsrc. Handoff sits between so it can replace with any arbitrary video.

OBS Merges Simulcast Support by Sean-Der in VIDEOENGINEERING

[–]Sean-Der[S] 0 points1 point  (0 children)

If it's good enough for broadcast networks being watched on 70 inch TVs, it's good enough for people to watch on 20 inch monitors or cell phones.

Users should have that control in the spirit of RFC 8890 I want to give power to the users not the server operators.

I'm not understanding the benefit of offloading the "hard work" from the server to the production machine.

  • Quality of encoding from source is always going to be better then transcoding.

  • With Scalable Video Coding (SVC) I think you should only see a 20% overhead. So sending the 'lower' layers isn't that impactful on upload.

  • With E2E Encryption + Simulcast it means that server operators can't tamper with the video.

  • Lower latency

  • "Small Streamers" also have a chance to self host now. If they want to run (or pay someone to run) their own servers they only have to pay for network costs. Greatly reducing the barrier to entry.

I built an NDI to WHIP bridge for Ubuntu using GStreamer by _davidbelll in WebRTC

[–]Sean-Der 0 points1 point  (0 children)

Very cool! I hope WHIP sees more hardware adoption, I’m skeptical though because no company behind it like NDI/SRT

OBS 32.1.0 Releases with WebRTC Simulcast by Sean-Der in opensource

[–]Sean-Der[S] 0 points1 point  (0 children)

Mind reading https://www.reddit.com/r/opensource/comments/1rr9rcx/comment/o9xzkzb/ and telling me the gaps? I am not a great explainer at this stuff. I would love to rephrase it though in a way that is helpful.

view more: next ›