Yeah, if the author sees this, it would be best to change this to "Click to Open". We can argue about the icon (I would say the floppy image), but seeing the word "upload" with a cloud icon 1000% means "send this up to the Internet."
I guess UI-wise some changes wouldn't be bad, but I am
just glad it works. I am currently converting an ancient
.mpg into a .mp4; I could do so via ffmpeg from the
commandline, but I always forget which options to use,
so a GUI kind of frees brain space here.
Nice interface at a first glance, for sure can be useful for users who would find using the actual thing too cumbersome. How does performance compare to the native app? Is any form of hardware decoding/encoding like h264_nvenc available? (I guess not?)
Note those only apply to scene_sad which is used for scene change detection and freeze detection and a few other things like mpdecimate -- it's a very specific use case
Just a thought - is the text “Click to upload” with a cloud icon perhaps a bit misleading?
If it’s fully client side, then you are just opening a file in essence - no clouds in sight!
Yeah, if the author sees this, it would be best to change this to "Click to Open". We can argue about the icon (I would say the floppy image), but seeing the word "upload" with a cloud icon 1000% means "send this up to the Internet."
I agree something like a folder or file icon would be more accurate.
I guess UI-wise some changes wouldn't be bad, but I am just glad it works. I am currently converting an ancient .mpg into a .mp4; I could do so via ffmpeg from the commandline, but I always forget which options to use, so a GUI kind of frees brain space here.
I love this, be interesting if this could make an in-browser video editor
Nice interface at a first glance, for sure can be useful for users who would find using the actual thing too cumbersome. How does performance compare to the native app? Is any form of hardware decoding/encoding like h264_nvenc available? (I guess not?)
I would imagine the only way to use NVENC directly from a browser would be via WebCodecs.
FFmpeg is so useful for TTS
Any chance those AVX-512 optimizations they released a while ago work within this? [1]
[1] https://www.phoronix.com/news/FFmpeg-July-2025-AVX-512
I think WASM SIMD is only 128-bit wide.
Note those only apply to scene_sad which is used for scene change detection and freeze detection and a few other things like mpdecimate -- it's a very specific use case
vibe-coded, and the github repo does not even contain the sources, just a single 'server.js' that is only for the documentation
Just look at the descriptive commit messages. /s
Tells you that most here just read the headline and not the code or commits any-more and this will just become abandonware.
this is ffmpeg running inside the browser am I correct? did not know this was possible. wonder what else we can run via webassembly
This is dope. Made a PR.
Interesting idea - must have been a lot of work to add all those features. I just tried it and it works locally too, which is pretty epic.
From https://news.ycombinator.com/item?id=44717303 :
> Objective metrics and tools for video encoding and source signal quality: netflix/vmaf, easyVmaf, psy-ex/metrics, ffmpeg-quality-metrics,
netflix/vmaf: https://GitHub.com/netflix/vmwaf
gdavila/easyVmaf: https://github.com/gdavila/easyVmaf
psy-ex/metrics: https://github.com/psy-ex/metrics/
slhck/ffmpeg-quality-metrics: Calculate quality metrics with FFmpeg (SSIM, PSNR, VMAF, VIF) https://github.com/slhck/ffmpeg-quality-metrics
Something like this would be great too:
The Ardour Manual > Loudness Analyzer and Normalizer: https://manual.ardour.org/mixing/basic-mixing/loudness-analy...