FotoKilof VS FFmpeg

Oh and I just discovered FotoKilof which is in fact a GUI frontend to imagemagick; though I don't actually have any experience using it.

FotoKilof might be interesting for you. While the initial setup is command-line (python), afterwars when running it, it will open a GUI.

check the issues on github. there was someone with the same problem: https://github.com/TeaM-TL/FotoKilof/issues/116

https://handbrake.fr/ you can use as alternative for ffmpeg and https://github.com/TeaM-TL/FotoKilof for images that is a GUI for imagemagick

mmm maybe some sort of image magick based software? https://github.com/TeaM-TL/FotoKilof

ImageMagick powerful CLI image editor, accepts an absurd amount of operations and formats as input and output, is very well documented, basically there is nothing like it when it comes to the amount of options to convert, resize and lossy compression images (and many other options). You can also try FotoKilof which is a GUI fork of ImageMagick if CLI is not your thing.

This one looks good, and has the capability to crop via mouse. now batch scaling is not a feature in said frontend, you'll have to write a shell script for that or use the tool you posted.

FFmpeg (https://ffmpeg.org/)

GPL2

Since FFmpeg is GPL2, doesn’t that require CompressX to disclose its source code?

IANAL, apologies if I miss understand license requirements.

https://github.com/FFmpeg/FFmpeg?tab=License-1-ov-file

This turns out to be a lot of assembly macros to help write one x86 assembly. https://github.com/FFmpeg/FFmpeg/blob/master/libavutil/x86/x...

The sibling comment recommending compiler intrinsics is probably the best way to go for writing SIMD code. A mixture of `` style types and intrinsics to specify instructions is a solid 90% solution compared to assembly.

If you want that last 10%, I think macros are putting the emphasis in the wrong place. They're a somewhat easy way to build up a language abstraction which will work if held carefully, but I'm confident the dev experience using this abstraction when you write invalid code will be deeply confusing.

I would suggest to write a parser instead of the macros. That'll tell you clearly when the syntax is invalid (though possibly not with much precision) and it'll give you a place to put semantic analysis for where valid syntax encodes nonsense. Do the equivalent of the macro expansions on the parsed tree instead of on the text. Emit asm as the "back end".

You might have heard of FFMPEG or ImageMagick for image and video edition in a programmatic way. MoviePy is a Python module for video editing (Python wrapper for FFMPEG and ImageMagick). It provides functions for cutting, concatenations, title insertions, video compositing, video processing, and the creation of custom effects. It can read and write common video and audio formats and be run on any platform with Python 2.7 or 3+.

There are many cloud-based tools and websites that can convert your images, but the problem with these tools is that you usually have to upload the files for them to be processed, and some of their services are not free. In this article, I'd like to introduce a piece of software called FFmpeg, which allows you convert the images locally with one simple command.

To run the demo locally, be sure to have Python 3.11 and FFmpeg installed.