dano VS oxipng

You should check out my program dano. It has a dupe detection function.

dano is a wrapper for ffmpeg that checksums the internal file streams of ffmpeg compatible media files, and stores them in a format which can be used to verify such checksums later. This is handy, because, should you choose to change metadata tags, or change file names, the media checksums should remain the same.

dano - a hashdeep/md5tree (but much more) for media files

My best advice (from a person who knows only enough to package his own projects) is it depends on the project. For my own Rust projects, I've found a Debian autopackager called cargo-deb for cargo. I convert those deb packages to rpm with alien. I upload both to the repo manually, and have a script which generates what I need and uploads to a PPA.

The meaty part of the holidays comes a little early this year for Ubuntu/Debian users, as I've prepared a special treat -- a PPA for httm (and dano)!

If you use something like ZFS, then you have a system thats watching your entire data path. If you're not paranoid, afraid of other ways your data can be corrupted, bit rot, etc. (again you do you), you might still want to look at a program I wrote awhile ago, dano, and have a system to periodically verify the data on disk.

One thing ZFS doesn't do (and thank goodness it doesn't?), it doesn't detect out-of-band changes to files. If a program has the permissions to modify a file, ZFS happily modifies that file. But, for some files (and for the truly paranoid), we may want to keep additional metadata about file integrity. For instance, FLAC files keep checksums of its music streams. A program I wrote, dano, provides a way to do the same for all FFMPEG compatible media streams.

Packages and source available for dano at the following link.

I have had good experiences with https://github.com/shssoichiro/oxipng . Although, I suspect this wouldn't give you nearly enough space savings as jpg.

If you do want the file as a PNG (for transparency and a common format that's well supported), but don't want it so huge, consider something like oxipng. https://github.com/shssoichiro/oxipng

oxipng, pngquant and svgcleaner — optimizing images

I wonder how `pngcrush` compares to `oxipng` (https://github.com/shssoichiro/oxipng).

Personally, I use `oxipng` if I want lossless compression. However, most of the time, I use `pngquant` instead, since it gives significant size reduction even at `99%` (I can't even distinguish between the original and reduced image).

    pngquant --quality=99 --ext=.png --force file.png

Depending on your workflow it might make sense to export PNGs directly from Affinity and then reduce their size with a utility like Oxipng, which uses all your cores to find the best algorithm for each particular image.

Assuming your frames are PNG files, you could use a lossless optimizer like optipng to try if their size can be reduced. I prefer oxipng, which is faster and multithreaded, and seems to have more active development.

Not sure what extensions of images you use, but if they’re PNG you could use oxipng: https://github.com/shssoichiro/oxipng