pako
ffmpeg.wasm
Our great sponsors
pako | ffmpeg.wasm | |
---|---|---|
6 | 76 | |
5,295 | 12,983 | |
0.8% | 3.6% | |
0.6 | 8.9 | |
about 1 year ago | 18 days ago | |
JavaScript | C | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
pako
-
Gzip library for client-side compression
try pako
-
Storing State in the URL
A trick I've used on top of serializing JSON in the URL is in-browser compression with a library like pako [0] (zlib in JavaScript). This helps you get more data in before you reach the browser limit for URL length.
[0] https://github.com/nodeca/pako
-
Browsers can do that?
Another operation that is sometimes desired is to take several files and give the user a compressed file. There are actually a surprisingly large amount (jszip, pako) of client side options here, but my favorite so far when it comes to speed, size and working with .zip has been fflate. But if you'd like to work with other formats, there are also libraries to decompress 7-Zip, RAR & TAR.
-
Major updates for bundle.js.org v0.0.3
I used monaco-editor for the code-editor, esbuild and rollup as bundler and treeshaker respectively, pako as a js port of the zlib and gzip libraries, pretty-bytes to convert the gzip size to human readable values, and countapi-js to keep track of the number of page visits, in a private and secure way.
-
Interacting with usernotes outside of toolbox
Just wanted to let you know the most current version of pako does not work with the example on the wiki page. It errors out with "unknown compression format". I had to use the version found in Toolbox lib folder in order to get the example from the wiki page to work.
-
298 App Lab apps in a Steam-like filter system
Uncompressing should be straightforward with pako.js.
ffmpeg.wasm
-
Show HN: I open-sourced the in-memory PostgreSQL I built at work for E2E tests
There's already ffmpeg wasm. I've used it in projects. Works great.
https://github.com/ffmpegwasm/ffmpeg.wasm
-
FFmpeg 7.0 Released
There's a low-hanging fruit that I think would make ffmpeg more helpful for regular people.
There's a million terrible websites that offer file conversion services. They're ad-ridden, with god-knows-what privacy/security postures. There's little reason for users to need to upload their files to a third-party when they can do it locally. But getting them to download fiddly technical software is tough - and they're right to mistrust it.
So, there's a WASM version of ffmpeg, already working and hosted at Netlify [1]. It downloads the WASM bundle to your browser and you can run conversions/transformations as you wish, in your browser. Sandboxed and pretty performant too!
If this tool a) was updated regularly b) had a nicer, non-CLI UI for everyday users and c) was available at an easily-Googlable domain name - it would solve all the problems I mentioned above.
[1]: https://ffmpegwasm.netlify.app/
-
FFmpeg-online: ffpmeg running on the browser
As their github page says, based on https://ffmpegwasm.netlify.app ...
I'm guessing no one did GPU-optimizations? I saw a web app (not an ffmpeg transpilation) that went clever and used WebGL so it can access the GPU and use its parallel processing capabilities...
-
Locoly (locoly.app): an in-browser video editor running all computations locally
ffmpeg.wasm: The engine making all these happen. However, I’m a bit concerned about its current situation. The repo has not been updated for more than six months now, and that’s not a healthy sign for an open-source project. Clearly I was reading the commits wrong. The author mentioned “speed up x264 with SIMD intrinsics” in their roadmap (https://github.com/ffmpegwasm/ffmpeg.wasm/discussions/415), which, if landed, could make such on-device video editors much more competitive.
-
[TASK] Reverse Engineer my Web App Before Production
I use https://github.com/ffmpegwasm/ffmpeg.wasm and I want my FFMPEG commands to be hidden from others.
- AWS service for transcoding audio to mp3 and images to jpg?
-
I made a simple online video editor with React and ffmpeg
Possibly using this? https://github.com/ffmpegwasm/ffmpeg.wasm
-
Newbie question: Is there any possible way to grab metadata from local media files and process them in the webbrowser?
You could try using something like ffmpeg wasm which is a way of using ffmpeg client side in browser. Unfortunately WebAssembly only supports files less than 2 gigabytes, which is a problem for videos. And I don't know if ffmpeg wasm contains ffprobe, so you might have to find another project or try to compile ffprobe to wasm yourself. This stuff is out of my wheelhouse so I can't offer much help.
- Show HN: FFmpeg UI
- Petition to add support for Gopher protocol in Firefox
What are some alternatives?
JSZip - Create, read and edit .zip files with Javascript
rust-ffmpeg-wasi - ffmpeg libraries precompiled for WebAsembly/WASI, as a Rust crate.
fast-zlib - Shared context synchronous compression
ffprobe-wasm - A Web-based FFProbe. Powered by FFmpeg, Vue and Web Assembly!
decompress-zip - Module that decompresses zip files
ffmpeg-libav-tutorial - FFmpeg libav tutorial - learn how media works from basic to transmuxing, transcoding and more. Translations: 🇺🇸 🇨🇳 🇰🇷 🇪🇸 🇻🇳 🇧🇷
fflate - High performance (de)compression in an 8kB package
node-ytdl-core - YouTube video downloader in javascript.
Archiver - a streaming interface for archive generation
handbrake-js - Video encoding / transcoding / converting for node.js
decompress - Extracting archives made easy
ffmpeg.js - Port of FFmpeg with Emscripten