pixelsort VS FFmpeg

Thanks a lot! I don't remember the exact process but I used some pixelsorting (I always use this pixelsorting tool) and a little tool I created myself (I haven't published that project yet, but I plan doing that in the future). I also use GIMP to mix the different images with the layer mode (I mostly use „lighten/darken only”, the „HSV […]” or „LCh […]” options) and shifting the layers around. The „Hue-Saturation” tool in GIMP can also give pretty nice results in combination with different layer modes. Honestly I always just play a bit with the different GIMP tools until I get to a result I enjoy. The reddit post with the original image sadly got deleted already… I hope this helps you at least a bit.

this was more of an experiment to see if i could do pixel sorting in ubuntu. relies on ffmpeg and a python pixel sort library that can be run on the terminal.

Learn & Code

photoshop, illustrator and https://github.com/satyarth/pixelsort/

Yes, it's actually two pixelsorted versions of the image merged together with the original image. I used this pixelsorting algorithm and merged the images with gimp.

On the Mac, I use this python module: https://github.com/satyarth/pixelsort but there is also these: https://github.com/wolfembers/Pixelsorting https://github.com/madlitch/MadPixelSort-Legacy

https://github.com/satyarth/pixelsort via http://satyarth.me/articles/pixel-sorting/

I used this pixelsorting algorithm (file-edges interval function with a mask generated with elementary-ca). Then I loaded the original image (sadly the creators account is alredy deleted) and the pixelsorted image into Gimp. I modified the pixelsorted image by applying a layer mode to it (I think it was "lighten only") and flipping it horizontally.

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.