Built a browser-based FFmpeg editor that runs entirely client-side via WebAssembly. Your files never leave your device -- all processing happens in a Web Worker. Works offline as an installable PWA after first load.
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
senshi001•1h ago
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!
pooploop64•50m ago
I agree something like a folder or file icon would be more accurate.
ale42•58m ago
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?)
dtf•51m ago
I would imagine the only way to use NVENC directly from a browser would be via WebCodecs.
luispa•9m ago
This is dope. Made a PR.
zuzululu•8m ago
this is ffmpeg running inside the browser am I correct? did not know this was possible. wonder what else we can run via webassembly
westurner•1h ago
> 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...