auto-editor VS oxipng

A few days ago I discovered a program that automatically trims the pauses from your video. This can decrease my raw footage duration by around 25%. I've used this for editing two videos so far, and this has been such a helpful tool.

Looking at the GitHub of auto-editor , I see it has a options page, and not being familiar with this app, I can see it has a pretty good display options.

auto-editor — removing silent portions from video recordings

auto-editor – Auto-Editor: Effort free video editing

Auto-Editor <--Is a command line application.

auto-editor can edit parts out based on motion and noise thresholds. I haven't found any settings I'm happy with though.

https://github.com/WyattBlue/auto-editor - to automatically remove silent portions of video recordings.

For those of us on Linux, check out https://github.com/WyattBlue/auto-editor: "Auto-Editor is a command line application for automatically editing video and audio by analyzing a variety of methods, most notably audio loudness."

However I have compiled it into a Windows binary which you can find here.Also a video I posted on using it is here.He also has a website for it here, from which you can also find a GUI version for Windows and Mac for a "donation" of $35 or more.

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