You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For lossy encoders theres usually some parameter controlling compression. Instead of using hardcoded settings, or manually tuning such, I’ve been working on a tool that I call Imager that tries to find the best compression/file-size tradeoff automatically.
Just curious to get some usage feedback and all. :)
The text was updated successfully, but these errors were encountered:
Hey @lilith, regarding cross platform support. In summary, only MacOS and Linux has been tested.
Personally I’m not very familiar with Windows, and Imager depends on various C dependences that will probably beed to be updated (i.e. the build scripts), such as VMAF and WebP, I think mozjpeg will be fine though (I didn't write this).
Part of me has been wishing I could fallback to compiling my C dependencies to WASM, among other reasons. Also may be easier to maintain as new codecs get added in the future (really excited about AV1/HEVC).
For lossy encoders theres usually some parameter controlling compression. Instead of using hardcoded settings, or manually tuning such, I’ve been working on a tool that I call Imager that tries to find the best compression/file-size tradeoff automatically.
Just curious to get some usage feedback and all. :)
The text was updated successfully, but these errors were encountered: