Hopefully this doesn't make it more dangerous to keep ffmpeg on our systems. WebRTC security flaws are responsible for a lot of compromises. It's one of the first things I disable after installing a browser
FFmpeg merges WebRTC support
11–20 of 204 posts
Re: FFmpeg merges WebRTC support
#12I 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.
If you visit the ffmpeg.wasm documentation, the first example on the Usage page does almost exactly this:
https://ffmpegwasm.netlify.app/docs/getting-started/usage
It transcodes a webm file to MP4, but making it speed up the video is trivial: just add arguments to `ffmpeg.exec()`. Your lack of success in this task is trusting an LLM to know about cutting-edge libraries and how to use them, not a lack of progress in the area.
Re: FFmpeg merges WebRTC support
#13I 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.
Entered the same prompt with Sonnet 4. Just needed to paste the two errors in the console (trying to load the CDN which won't work since it uses a web worker, and hallucinated an ffmpegWasm function) and it output an HTML file that worked.
Re: FFmpeg merges WebRTC support
#14Interesting I keep getting blocked by the bot detection on iOS safari, both from our work WiFi and cellular data. Anubis let me go
[deleted]
Re: FFmpeg merges WebRTC support
#15I 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.
if you‘re really interested in doing that, i‘m certain you can with a bit of effort. There are plenty of docs and examples online.
[deleted]
Re: FFmpeg merges WebRTC support
#16Not the SCTP parts! It's implementing WebRTC-HTTP Ingestion Protocol (WHIP), a commonly used low-latency HTTP protocol for talking to a gateway that talks actual WebRTC to peers over WebRTC's SCTP-based protocol. https://www.ietf.org/archive/id/draft-ietf-wish-whip-01.html
I hope some day we can switch to a QUIC or WebTransport based p2p protocol, rather than use SCTP. QUIC does the SCTP job very well atop existing UDP, rather than add such wild complexity & variance. One candidate, Media-over-Quic ?MoQ), but the browser doesn't have a p2p quic & progress on that stalled out years ago. https://quic.video/ https://datatracker.ietf.org/group/moq/about/
Re: FFmpeg merges WebRTC support
#17I 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.
Don't try to do cutting edge stuff with a brain that doesn't know anything past a certian date.
Trying to do things off the beaten path with LLMs is rarely successful, especially if there's a related much more popular option.
I'm convinced that programmers' bias towards LLMs is strongly correlated with the weirdness of their work. Very often my strange ideas pushed to LLMs look like solutions but are rather broken and hallucinated attempts which only vaguely represent what needs to be done.
Re: FFmpeg merges WebRTC support
#18That should make self hosting streams/streaming CDNs way easier.
If you know how to use it ffmpeg is such an amazing stand alone/plug and play piece of media software.
Re: FFmpeg merges WebRTC support
#19Interesting I keep getting blocked by the bot detection on iOS safari, both from our work WiFi and cellular data. Anubis let me go
Are you getting the "access denied" page, or an infinite challenge loop?
Re: FFmpeg merges WebRTC support
#20I 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] https://github.com/Glimesh/broadcast-box?tab=readme-ov-file#...