com.obsproject.Studio VS mpv

The "see details" link takes you to: https://github.com/flathub/com.obsproject.Studio/graphs/contributors/

With official packages, I have even more questions. Example: OBS Studio. The publisher link points to this repo, which is currently archived, with the message "This repository is no longer used to build OBS. Issues should be reported at https://github.com/obsproject/obs-studio". After some digging, I found they're using Github Actions to automatically publish to Flathub on release, which is fine (and pretty cool), but I would still prefer that Flathub provide some kind of records on their end. What assurances do I have that the package installed on my machine from Flathub is the one that was built by upstream? Maybe they have something and I'm not looking in the right place.

Big news for Linux users: We now officially ship OBS Studio via Flatpak (in addition to the PPA), greatly expanding support for more distros and providing a much more consistent experience, no matter your environment. Download it from Flathub here - https://flathub.org/apps/details/com.obsproject.Studio

OBS (stream/rec): Flatpak, Steam(?)

There is obs-studio package in Debian, try using that. Alternatively, you could install it as a Flatpak via Flathub (there were also recent news of OBS Project is making it their official Linux package instead of Ubuntu PPA).

I'm not the only one. The issue tracker is full of people having serious issues like, y'know "Doesn't work at all" and "No fonts," and "Crashes on Alt-Tab," etc.

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.