trackselect VS mpv

If you don't have to deal with multiple languages then https://github.com/po5/trackselect works. But in case SDH is not available for your preferred language but is present for another language then it will select that unfortunately.

Basically, you need a way to differentiate signs and full subs so that your player can autopick based on your preference. This can be done by marking them as different languages - jpn/eng, eng/zxx, enm/eng etc. or tagging both as eng but marking the signs track as "forced" to signify that it goes with the eng audio. Given that most people fail at this basic task, you can use this - https://github.com/po5/trackselect on mpv to fix the issue to a certain extent.

I am also using Trackselect in order not bother with manually selecting tracks in videos which have multiple audio and video tracks.

I'm trying to get this particular script working https://github.com/po5/trackselect

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.