Live data from Hacker News

FFmpeg merges WebRTC support

git.ffmpeg.org

81–90 of 204 posts

Re: FFmpeg merges WebRTC support

#81
post #34

I know there are JavaScript ports of FFmpeg and I would love to use them. But so far, I never got it working. I tried it with AI and this prompt: Make a simple example of speeding up an mp4 video in the browser using a version of ffmpeg that runs in the browser. Don't use any server side tech like node. Make it a single html file. But so far every LLM I tried failed to come up with a working solution.

You know there's ... documentation, right?

LLM is my eyes. LLM is my ears. LLM is my documentation. I am LLM.

Re: FFmpeg merges WebRTC support

#82

I am so incredibly excited for WebRTC broadcasting. I wrote up some reasons in the Broadcast Box[0] README and the OBS PR [1] Now that GStreamer, OBS and FFmpeg all have WHIP support we finally have a ubiquitous protocol for video broadcasting for all platforms (Mobile, Web, Embedded, Broadcasting Software etc...) I have been working on Open Source + WebRTC Broadcasting for years now. This is a huge milestone :) [0]…

Your work in this area has been phenomenal. Thank you! I use broadcast-box all the time.

Re: FFmpeg merges WebRTC support

#85

Earlier quoted context omitted.

You’re basically asking people to do your homework for you at this point…

He said it is a matter of copy+paste, not work. I don't think so as I did not get it to run. And if he really can accomplish it with copy+paste, why wouldn't he demonstrate it?

Because he doesn't want to do that for you for free I guess :)

"Tap with a hammer: $1. Knowing where to tap: $9999."

Re: FFmpeg merges WebRTC support

#87
post #76
post #63

Earlier quoted context omitted.

Kernel level exploits are more dangerous but also way less common, for a lot of places docker is sorta okay as a security boundary

It's layers. Docker is better than nothing, but a VM is better still, and even better is docker on a dedicated VM on dedicated hardware on a dedicated network segment.

That's sacrificing an awful lot of latency cost for each transcode job though.

Re: FFmpeg merges WebRTC support

#88

I am so incredibly excited for WebRTC broadcasting. I wrote up some reasons in the Broadcast Box[0] README and the OBS PR [1] Now that GStreamer, OBS and FFmpeg all have WHIP support we finally have a ubiquitous protocol for video broadcasting for all platforms (Mobile, Web, Embedded, Broadcasting Software etc...) I have been working on Open Source + WebRTC Broadcasting for years now. This is a huge milestone :) [0]…

Your work in this area has been phenomenal. Thank you! I use broadcast-box all the time.

What sort of infrastructure do you need for scaling WebRTC multicast?

Are we entering an era where you don't need Amazon's budget to host something like Twitch?

Re: FFmpeg merges WebRTC support

#90
post #88

Earlier quoted context omitted.

Your work in this area has been phenomenal. Thank you! I use broadcast-box all the time.

What sort of infrastructure do you need for scaling WebRTC multicast? Are we entering an era where you don't need Amazon's budget to host something like Twitch?

Yes we are :) When OBS merges the PR [0] things are going to get very interesting.

Before you needed to run expensive transcoding jobs to be able to support heterogenous clients. Once we get Simulcast the only cost will be bandwidth.

With Hetzner I am paying $1 a TB. With AV1 or H265 + Simulcast I am getting 4K for hundreds of users on just a single server.

We will have some growing pains, but I am not giving up until I can make this accessible to everyone.

[0] https://github.com/obsproject/obs-studio/pull/10885

Post reply on HN