retropie-setup-notes VS mpv

I personally still like the RetroPie setup the best. It has some quirks, but I think it's mostly a sensibly configured solution and there's plenty of community knowledge / help out there. Maybe it's just familiarity bias, but after many hours of poking around in it and tweaking stuff I can't say I dislike it.

IMHO worst part of the out-of-the-box experience with RetroPie is that everything is configured for maximum performance, which kinda means worst latency. The input lag is astronomical if you're used to original hardware / FPGA emulation / CRTs or zero-lag scalers etc. You can get it to very acceptable levels for many systems, but you have to know which settings to change.

Here are the notes I took when configuring and tuning my setup:

https://github.com/blitzcode/retropie-setup-notes/blob/maste...

They're for a Pi 3B that's setup for output on a CRT TV, but like 90% should apply to a Pi4 on an HDTV.

Shaders are always a personal taste thing. Those posted here certainly get the as sharp as possible without shimmering, blurring, borders or wrong aspect look right, but there are other options if you want the CRT look.

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.