libvips VS mpv

After some research, I found libvips, a demand-driven, horizontally threaded image processing library. It is designed to run quickly while using as little as memory as possible.

Sharp is a fast and efficient image optimization Node.js module that makes use of the native libvips library.

h2non/bimg can handle both if the underlying libvips is compiled with support for both formats.

if you're using linux (which it doesn't seem so) there's also vispdisp https://github.com/jcupitt/vipsdisp which is based on https://github.com/libvips/libvips which will likely take over how images are decoded in the future for everything, at least methodology wise.

The magic happens by way of a library called Libvips, which contains an ultra-high-speed low-memory image resizer.

imagor uses one of the most efficient image processing library libvips. It is typically 4-8x faster than using the quickest ImageMagick and GraphicsMagick settings.

Try the solutions here: https://github.com/libvips/libvips/issues/2479

in that case maybe take a look at https://github.com/libvips/libvips

libvips v8.6+ or ImageMagick for image analysis and transformations

https://mpv.io/ has yt-dlp support, if yt-dlp is installed you just need to throw the URL at it and it plays the video (without download).

See https://github.com/mpv-player/mpv/issues/9053

I apologise for not following procedure. I am in the middle of building mpv 0.37 from source. Irrespective of the outcome I will document what I had to do in addition to the instructions on mpv.io and if the problem perststs, where it happens and where not with kernel version, mpv version taken from the screen, and the terminal output.

Use MPV. Partticularily shinchiro's builds. Extract the folder where you want its installation directory to be, if you decide to install it. Otherwise, just drag and drop files on top of its window or executable.

Author of ripgrep here.

Like automatic encoding detection and transparently searching UTF-16?

Or simple ways for composing character classes, e.g., `[\pL&&\p{Greek}]` for all codepoints in the Greek script that are letters. Another favorite of mine is `\P{ascii}`, which will search for any codepoint that isn't in the ASCII subset.

Or more sophisticated filtering features that let you automatically respect things like gitignore rules.

Those are all things that ripgrep does that grep does not. So I do not favor this explanation personally.

ripgrep has just about all of the functionality that GNU grep does. I would say the two biggest missing pieces at this point are:

* POSIX locale support. (But this might be a feature[1].)

* Support for "basic" regexes or some equivalent that flips the escaping rules around. i.e., You need to write `\+` to match 1 or more things, where as `+` will just match `+ literally.

Otherwise, ripgrep has unfortunately grown just about as many flags as GNU grep.

[1]: https://github.com/mpv-player/mpv/commit/1e70e82baa9193f6f02...

- https://github.com/mpv-player/mpv/issues/8692

https://mpv.io played it without fuss.