Stockfish VS FFmpeg

The Stockfish program can be set to play at strength level 0-20. Estimates of the levels' Elo is provided here: https://github.com/official-stockfish/Stockfish/commit/a08b8...

- and handicapped Stockfish (https://stockfishchess.org).

The whole thing is at https://github.com/magv/bchess, and can be installed with just 'pip install bchess'.

This was the result searching for all the 35 stockfish benchmark positions to depth 6.

Stockfish doesn't have a classical evaluation anymore. And before this, most of the time (around 90%), NNUE was used to evaluate.

If you use ChessBase on a MacBook through Parallels, there's an issue where people have posted Apple Silicon compiles for Windows: https://github.com/official-stockfish/Stockfish/issues/4241

Progress can be found here https://github.com/official-stockfish/Stockfish/wiki/Regression-Tests At 1 thread it has gained +18.3 elo on a balanced book, and +47.03 on UHO (unbalanced) book as well as +39.4 elo for FRC and +65.56 for DFRC. At 8 threads it has gained +14.33 elo on a balanced book and +49.46 on UHO (unbalanced book). Also testing was done on 8 threads with 180+1.8 (this is considered very long time control for fishtest standards) and progress was +9.45 on balanced book and +49.65 on UHO.

Downloads are available temporarily here https://github.com/official-stockfish/Stockfish/releases/tag/stockfish-dev-20230622-a49b3ba7

The strongest version of Stockfish is the latest development version of Stockfish

I am trying to implement Stockfish (a popular chess engine) into my React Native app.

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.