mpv.net VS rav1e

There's a pinned issue on the github page about the state of mpv.net development from January 2023 where the dev says that they started working on a cross-platform successor of mpv.net instead.

mpv.net - A great open-source lightweight video player based on mpv with support for many formats and extensive configuration. Replaces MPC, VLC, PotPlayer, Windows Media Player, etc. Strongly recommend replacing your current video player with this, since programs like VLC are bloated and can have issues playing back videos and exhibit weird artifacts.

You can use mpv (I use mpv.net as GUI) since IINA is just based on it.

https://github.com/mpvnet-player/mpv.net in the microsoft store too. get with the times, gramps

The binary is hosted on github https://github.com/mpvnet-player/mpv.net

mpv.net for a more beginner-friendly version.

Now on to the second solution. This is divided into 2 sub options. Either stock MPV which doesn't have much of a UI and relies on the user knowing various hotkeys, or MPV.net which has a UI but won't have all the latest updates from mainline MPV. For stock MPV you will need to have 7zip installed.

Music player: A decent media player that I've used is MPV.Net, while not strictly for audio, it can be used to play audio. Alternatively, I use foobar2000.

in Lua Script I try to debug, but it required "libmpv-2", when I require the module it failed, is anybody know how to debug? my launch settings are from here:https://github.com/mpvnet-player/mpv.net/wiki/Extending-mpv-and-mpv.net-via-Lua-scripting

i use this

Sure. You'll see it very often in codec implementations. From rav1e, a fast AV1 encoder mostly written in Rust: https://github.com/xiph/rav1e/tree/master/src/x86

Large portions of the algorithm have been translated into assembly for ARM and x86. Shaving even a couple percent off something like motion compensation search will add up to meaningful gains.

Or the current reference implementation of JPEG: https://github.com/libjpeg-turbo/libjpeg-turbo/tree/main/sim...

Again, if anything AOM would be the one restricting licenses to AV1 (if they chose to) except AOM has stated and also published AV1 in a way to allow license free access to development (which allows people to make forks of the official build like it's open source) and usage. (1)(2) I don't see why they would suddenly change this.

You can speed up the sampling process with --vmaf n_subsample=5, which in my experience works more accurately than either 2 or 4, possibly due to this bug/feature present in multiple encoders. You might also need to manually set the number of threads used for VMAF calculation with --vmaf n_threads=16, but YMMV.

That remember me of https://github.com/xiph/rav1e which is an AV1 encoder

I put in the request for ffmpeg passthrough mastering-display data a few years ago and haven't heard of any support yet.

It's getting there.. Initial steps for FFmepg: https://patchwork.ffmpeg.org/project/ffmpeg/list/?series=8444 rav1e: https://github.com/xiph/rav1e/pull/3000

It's entirely possible to re-use bits of other HW encoders for the first pass (motion estimation, etc).