MediaInfoLib VS mpv

can you use https://mediaarea.net/MediaInfo and post the text output. maybe there is something malformed in the source that the render engine is unhappy with. as soon as i see sync issues that dont make any sense, i always blame the source media and look to reencode it or somehow repackage it (like with handbrake) into a known and not wierdo format. remember mp4 is just a box. there might be a cat in that box, there might not be a cat at all.

Footage specs - MediaInfo - please include the "Text" view of the file.

Is the problem with absolutely every AVC (h264) video you've tried, or only some? If it works with some and not others, can you share a MediaInfo report on a sample "faulty" file?

Need a little more info. What's the audio codec? Try converting the audio to AAC. Use mediainfo to see what codecs the file have.

Can you give the MediaInfo report from one of the files that Jellyfin is having a "hard time" with?

Some can be encoded with 8bit others with 10bit, the device maybe doesn't play well with 10bit encoded videos. You can use mediainfo to see if was encoded with 8bit or 10bit.

What are the specifications of the file? Run MediaInfo on it and post the results here.

Use MediaInfo on it and post the results.

Footage specs - MediaInfo - please include the "Text" view of the file.

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.