media-driver VS FFmpeg

You might need to install the non-free intel media driver: https://github.com/intel/media-driver

Intel had VP9 decode since Kaby Lake (7th gen); original Skylake (6th gen) could not handle it (see here).

I've heard intel-media-driver was the way to go for supported hardware, but I also heard that it could decode slower than libva-intel-driver (like #925), and that Intel doesn't officially support some kind of decode feature in intel-media-driver, but it's implemented in libva-intel-driver.

I reproduced the issue on my end and opened a ticket to let intel devs know. https://github.com/intel/media-driver/issues/1628

I can see 22.6.6 was released in December ( Releases · intel/media-driver (github.com) ), but I'm having troubles getting it installed.

You should be able to choose FFmpeg VAAPI encoder, though it is suggested that kernel 6.2 is needed for this to actually work. I can confirm that it's broken with my A770, while I can choose the device, encoder is failing. No such problem with my Rapter Lake iGPU.

On GitHub there are similar problems reported: https://github.com/intel/media-driver/issues/1282

Source: https://github.com/intel/media-driver/blob/master/docs/media_features.md

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.