audio-router VS mpv

Audio router

I imagine Audio router might help in what you're looking for.

The ones that people recommended that I could still find (both of which are at least 7 years old): https://github.com/audiorouterdev/audio-router https://vb-audio.com/Cable/index.htm

I personally use Audio Router, you can look up guides about how to set it up fairly easily.

How did you used to route audio from YouTube to Audacity? Mac's require something like Blackhole to do that. Maybe try something like https://github.com/audiorouterdev/audio-router

https://github.com/audiorouterdev/audio-router and some virtual cable device?

If Voicemeeter can't force it, you can use this one, so you can select the output for the specific app. But you'll still need Voicemeeter or Virtual Audio Cable

One program you can test is Audio Router. It can't mess up anything, but it also has not received any updates in over 6 years so it's not uncommon for it to not work with certain devices or programs.

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.