Replies (28)

My setup runs entirely on-device and doesn’t rely on any third-party servers. Any web client can implement this. Previously, the common approach was to use FFmpeg, which requires downloading a ~40MB WASM package and is significantly slower. In comparison, this approach using built-in WebCodecs is much faster, up to 67x in my tests, and simpler to integrate. I know Amethyst also supports compression, though I’m not sure which package or approach it uses.
My only suggestion is the default output should be webm instead of mp4, with an optional "Primal compatibility mode" button that switches to mp4 This helps draw attention to Primal's issues with webm support
This is sick, it would be cool to plugin to put it on zapstore and maybe clients could plugin, the ideal flow would be upload from client, your tool compresses, puts in morganite before actual upload to remote blossom servers and note publish
↑