mpv.net media player

[pirlouy]

intel uhd730 should be able to handle default.
gpu-hq profile was changed to high-quality in mpv v0.37 and polar lanczos scalers do use more resources than lanczos (now default).
Thanks for the info about new profile.
If you think it can "handle default", you surely mean Intel iGPU can't handle "high-quality" profile with display-resample interpolation ? That's what I though but I would have know from someone who has the hardware.
I guess I'll test myself if/when I got one in the next years.

If someone wants to test before that...
vo=gpu-next
gpu-context=d3d11
gpu-api=d3d11
hwdec=d3d11va
d3d11va-zero-copy

profile=high-quality

video-sync=display-resample
interpolation=yes
tscale=oversample

[huhn]

Huhn/Mightyhuhn (I'm JimboTHX1138 back in the day :)) let me clarify my chroma comments. We all know it shows up on red really bad. But I'm a fan of upscaling chroma. Getting 4:2:0 to 4:4:4. People can test this on Netflix logo. Bad filter will look like a sabertooth tiger with rigid edges or cheap bilinear filter so soft like most TV manufactures that's annoying. Check out Netflix logo 720p/1080p with Krig. :D Love ya:)

and i'm obsessed with them:
https://slow.pics/c/H2YeNTcm
https://slow.pics/c/7iTtfshW

and yes i think chroma in mpv is just terrible when krig the bleeding master is one of the better scaler. all hail super xbr the king of kings.

https://slow.pics/c/KbViAj68 it even beat ravu in image scaling well r4 is not tested yet but seeing the others i'm not sure.

[anta777]

How can you measure fps ?
Artoriuz write
"Measure-Command { mpv --no-config --vo=gpu-next --gpu-api=vulkan --audio=no --untimed=yes --video-sync=display-desync --vulkan-swap-mode=immediate --window-scale=2.0 --fullscreen=yes }"

How can I make sure my shader is connected and working?

Could you add to your wonderful player the ability to load custom shaders through the menu?

[huhn]

try this: mpvnet.exe --no-config --vo=gpu-next --gpu-api=vulkan --loop-file=yes --dither=no --audio=no --untimed=yes --video-sync=display-desync --vulkan-swap-mode=mailbox --opengl-swapinterval=0 --osd-msg1="FPS: ${estimated-display-fps}" --window-scale=2.0 --fullscreen=yes --glsl-shaders="path to the GLSL shader to test like "~~/shaders/ArtCNN_C4F16.glsl"" "path to a testfile like a 1080p file if you have a UHD screen"

C4F16 has about 320 FPS at 90 % GPU load using my 4060 that's relative low noise.

opening the OSD will tank FPS massively even the OSD text may massively lower FPS. but the OSD will also show you if the shader is loaded and does something. shift+i open the OSD for rendering you now press 2. `will show you protentional errors that's shift+´ on my keyboard which is next to backspace.


~~/shaders/ArtCNN_C4F32.glsl
there are some arguments in there that do nothing i just changed my benchmark mpv.conf to an command line and this works.

[Alexkral]

I don't remember the benchmarking profile I used with regular mpv, but d3d11 was the fastest renderer, and setting gpu-shader-cache-dir was needed for heavy shaders like FSRCNNX-56-16-4-1, possibly beneficial for others as well.

[huhn]

are you sure about that?
gpu-shader-cache-dir is "on" by default it is used to change the shader cache not to create one or use one that's gpu-shader-cache which is also on by default. does it not work one windows?

D3D11 1800 40 %
vulkan 1900 40 %

these numbers are completely meaningless and it is only one GPU architecture anyway.

and i don't see a way to benchmark D3D11 at all.

[Alexkral]

This was some time ago, at the time I was using a GTX 1080 and d3d11 was clearly faster than vulkan on windows. When I set gpu-shader-cache-dir the folder was filled with shaders on run, I don't remember if FSRCNNX-56-16-4-1 was much slower before that or directly unusable.

Many things may have changed since then, and I'm just talking about Windows.

EDIT:

I've looked at the reference and I think gpu-shader-cache didn't exist back then, so it probably wasn't used unless gpu-shader-cache-dir was set.

For benchmarking d3d11, you may be missing d3d11-sync-interval=0

[huhn]

i was very close to report that it is slower when it is active window/application it caps at 300 exactly.

d3d11 360 fps 2600 mhz at 94 % load
vulkan active 330
vulkan inactive 320 2700 mhz at 90% load

i'm not skilled enough to read the OSD to know if it is rendering 10 bit or not.

artcnn is now on my ignored scaler list anyway. the motion errors are unacceptable and the 16 version has similar issues as fsrcnn.

[anta777]

Help me!
I can't connect some shader:
-FSRCNN
-ArtCNN
-Ravu
-Nvscaler
Why don't I see connected shaders in the statistics?

SSIM,Krigbilateral,Anime4K work fine.

[anta777]

delete

[huhn]

you can put it where ever you want.

~~/shaders/ points to your home directory for mpv so it is different for every computer and different between mpv and mpv.net.


could be this: C:\Users\anta777\AppData\Roaming\mpv.net\shaders

i don't know could be everything. it's the location of mpv.net.conf
you can also put them in C:\mpv\shaders\ArtCNN_C4F16.glsl
so glsl-shader="c:\mpv\shaders\ArtCNN_C4F16.glsl"

mpv is literally design so people don't use it.

[anta777]

Thank you!

What should I see in the statistics when ArtCNN is applied?
t,2
Can you take a screenshot?

[huhn]

yeah they changed the OSD to t here.

https://i.postimg.cc/HL4GCNtB/mpv-net.png

[anta777]

Thank you very much!!!!!!
Everything works, I checked it on rip 600x300!


They just don't work now NVScaler and NVsharpen.
But this maybe my old video?
Notebook 8600GS.

[huhn]

https://www.techpowerup.com/gpu-specs/geforce-8600-gs.c1767 ?

not that i know but i doubt that it will run modern gpu instruction and even if it could do these instruction there is no way it is fast enough.

[anta777]

AiUpscale doesn't work either.
AiUpscale working today!

[anta777]

What's the easiest way to compare the performance of different settings?

[huhn]

try the benchmarking settings.

[anta777]

Thank you very much, everything worked out!

[anta777]

FSRCNN only luma or upscale chroma too ?

[anta777]

Which upscaler is the best right now for films (not manga) SDR fhd to 4K?

1. AiUpscale?
2. ArtCNN? (for manga only?)
3. FSRCNN?
4. SXBR?
5. NGU sharp?

[anta777]

How to disable built-in filters scaler in mpv?

Write in mpv.conf:
scaler=no

[huhn]

How to disable built-in filters scaler in mpv?

Write in mpv.conf:
scaler=no
video-unscaled=yes
makes the video native resolution but chroma scales.

FSRCNN only luma or upscale chroma too ?
not sure but there are a lot of fsrcnn versions out there. on a first look it doesn't seem to scale chroma the version i have here.

Which upscaler is the best right now for films (not manga) SDR fhd to 4K?

1. AiUpscale?
2. ArtCNN? (for manga only?)
3. FSRCNN?
4. SXBR?
5. NGU sharp?

there will never be a general answer for that.
SXBR is clearly not the highest end it's power is that it is cheap and save to use. the mpv version is bad anyway.

artcnn is supposed to be good for everything. but everything i have seen it should be completely avoid. motion issues massive ringing and odds lines... and chroma is super noisy with odd artefacts.

all of this hit me unprepared because the preview image and psnr are very good.

AIscale no clue looks like yet another FSRCNN port/fork.

FSRCNN there are a lot of version of it originally it had ringing issues now isthas the same issue as NGU sharp it like to mess things up if they are not "perfect". i didn't really look to much into it.

NGU sharp another rated scaler but has virtually no ringing gaving me the impression neural network scaler can generally do that i guessed wrong. can go completely wrong.

NGU AA is most likely the saves selection it can handle nearly everything without going nuts but is by far not as sharp.
no ringing no totally odd behaviour no common issues with sources of type x. i guess pixel art is the one thing it can go wrong on else this is a stable but not as sharp scaler.

if i had to choice something as "best" it would be NGU AA.

[anta777]

Thank you very much!

I want to disable all built-in ones scalers in mpv and use for upscale my glsl shaders.

Is it possible?

[anta777]

What are there chroma upscalers without pixel offset?
Only built-in mpv?

[huhn]

Thank you very much!

I want to disable all built-in ones scalers in mpv and use for upscale my glsl shaders.

Is it possible?

if you load a shader it will do that automatically the build in one are then used as correction or chroma.

What are there chroma upscalers without pixel offset?
Only built-in mpv?

you need an offset the build in ones will use the correct offset automatically. with glsl chroma you run the risk of wrongly placed chroma there is new hooks that can be added but not sure which ones have them.

[anta777]

If I use FSRCNNX and cscaler=ewa_lanczos4sharpest , then they won’t have a conflict?

Or cscaler won't work ?


How can I check correct offset in new hooks?
Krigbilateral?
Joinbilateral
Chroma-from-luma-prediction?

[anta777]

Why i look in statistics
ortho(vert)upscaling (lanczos)
ortho(horiz)upscaling (lanczos)

I disable scalers in mpv and use my shader.

[huhn]

If I use FSRCNNX and cscaler=ewa_lanczos4sharpest , then they won’t have a conflict?

Or cscaler won't work ?


How can I check correct offset in new hooks?
Krigbilateral?
Joinbilateral
Chroma-from-luma-prediction?

i don't know if it is even used i only know it exist.
you can try this: https://drive.google.com/file/d/19wIkcOpBGCtaCeh-ZNsShlCn-FvKnc48/view?usp=sharing

all files are 100% the same only the meta data is different. if it moves when you switch between them it is most likely working.

maybe maybe not mpv is a complete mystery to me:
Chroma variants are trained to learn how to reconstruct chroma using information from both chroma and luma. The DN and DS variants should generally work well on most lossy video content, you should only consider the other variants on very high quality sources. You should not use this alongside luma prescalers.

YCbCr variants are 2x YCbCr models that double the image and reconstruct chroma simultaneously. This is what you should generally use if you want to use ArtCNN for both luma and chroma. Do not use these on 4:4:4 content.

RGB variants are normal 2x RGB models. These are not trained to learn how to reconstruct chroma, they simply double the image. These are the preferred models for RGB or 4:4:4 content in general.

why do you need to use a different shader when the source is 4:4:4.
why does it need an RGB version.
if can i not use the chroma version with another prescaler i'm so confused.

maybe FSRCNN works together with krig but it is not supposed to work together with chroma artcnn for reasons or something.

Why i look in statistics
ortho(vert)upscaling (lanczos)
ortho(horiz)upscaling (lanczos)

I disable scalers in mpv and use my shader.
well it has to scale to match luma even if you tell it not to "scale".
could be chroma when you scale the image with FSRCNN. i'm really not qualified to answer that.

[stax76]

awesome-mpv has been updated today, I sync it a few times per year with the user script section in the wiki.

https://github.com/stax76/awesome-mpv

https://github.com/mpv-player/mpv/wiki/User-Scripts

[therube]

history.txt:
is there a minimum file size (or some other determining factor) for which history.txt
is not updated for particular file(s)?
- like if i throw (drag & drop) a directory of files into mpv.net, files ranging
in length between 0:10 to 1.34.23
no. it is not length or size alone?
is % of file played a factor?
or how the player is Quit? Or...?
- as it is, something ? either causes a file to turn up in history.txt, or not?

https://forum.doom9.org/showthread.php?p=1944164#post1944164 (only answering a 3-year old post ;-).)

Not length, size, or %, or... simply the amount of time that the clip has been open (not necessarily playing or anything else, simply open) - with a minimum time needed before a file is logged of 60 seconds.

---

And in that respect...


history.lua (https://github.com/stax76/mpv-scripts/blob/main/history.lua)

a minimum of 60 sec.

Is there any downside (as in extra polling or i/o or...)
to reducing that 60 to some other amount, say 18 seconds or whatever?

likewise, say you jump to the next file, never start playback,
& the player simply sits... for hours or days... any impact there?
or does it simply sit in a no-op state, & on the next Next File,
/then/ it checks time & writes to the .log ?

[therube]

(I don't really know what I'm saying below, so I'll just carry on... heh.)

input.conf

> a cycle-values video-aspect 16:9 4:3 2.35:1 -1 #menu: Video > Cycle Aspect Ratio

so 'a' cycles aspect ratio
i suppose you can simply add any wanted value, say 16:10, to that "list", & they would then (also) cycle

what is the meaning of -1 ?
or does that mean something like, reset on close (of clip)?
oh "video-aspect-override"... & that means just what... ?
oh, oh. so -1 resets AR to "Default", & if set that way, /then/ subsequent clips open at Default - otherwise they'll open at whatever the last override was set to.

in that regard, could hitting -1 throw up a message, "video-aspect: #, Default", to make it more apparent that the DAR is being used instead of an override?
likewise, considering a/r carries forward unless reset, maybe an 'A' to manually reset it - without cycling, or can something like the be defined in input.conf ?

and 0 is "PAR", which is "native resolution" ? NO, must be "pixel aspect ration"... which means what, width/height ?
and -1 is "Default", which is what "DAR", display aspect ration ?

so if:
Width: 426
Height: 282
PAR is then: 1.5106 = ar = 0
DAR: 3:2, is 1.5000 = ar = -1

Do I kind of understand the above - kind of correctly?

[stax76]

I did a little maintenance work and released a new beta version.

# v7.1.1.1 Beta (2024-07-20)

- Korean, Russian and Turkish translation added, Japanese translation fixed. Thanks to the translation team!
- Action/Workflow/Auto build fix and update.
- New default bindings and menu items for select.lua which is a new simple mpv built-in command palette script.
In the context menu select.lua features can be found under `View > On Screen Menu`.
https://github.com/mpv-player/mpv/blob/master/player/lua/select.lua
- New PowerShell script 'Tools\release-mpv.net.ps1' used to releases mpv.net on GitHub.
- Fix DVD ISO file support.
- MediaInfo updated to version v24.6.
- New ARM64 support.
- New zhongfly libmpv x64 build.
- New Andarwinux libmpv ARM64 build.

[therube]

7111.

- New default bindings and menu items for select.lua which is a new simple mpv built-in command palette script. In the context menu select.lua features can be found under `View > On Screen Menu`.

I'll just note that I'm not getting anything; F8, F1, F3...?

Win7 x64 (might matter).

No messages in Console.


If I download select.lua, I get:


[select] stack traceback:
[select] C:\mpvnet7111\portable_config\scripts/select.lua:19: in main chunk
[select] [C]: at 0x07fec638c550
[select] [C]: at 0x07fec638cb00
[select] Lua error: C:\mpvnet7111\portable_config\scripts/select.lua:19: module 'mp.input' not found:
[select] no field package.preload['mp.input']
[select] no file 'C:\mpvnet7111\lua\mp\input.lua'
[select] no file 'C:\mpvnet7111\lua\mp\input\init.lua'
[select] no file 'C:\mpvnet7111\mp\input.dll'
[select] no file 'C:\mpvnet7111\loadall.dll'
[select] no file 'C:\mpvnet7111\mp.dll'
[select] no file 'C:\mpvnet7111\loadall.dll'

[stax76]

I don't know if you can use select.lua with an old libmpv build, you can use command_palette.lua. It has new features:

- Command palette features
- Bindings
- Playlist
- Chapters
- Profiles
- All tracks
- Audio tracks
- Video tracks
- Subtitle tracks
- Secondary subtitle tracks
- Subtitle line
- Commands
- Properties
- Options
- Audio devices
- Blu-ray Titles

https://github.com/stax76/mpv-scripts?tab=readme-ov-file#command_palette

[stax76]

The command palette user script supports now stream quality and aspect ratio.

https://github.com/stax76/mpv-scripts?tab=readme-ov-file#command_palette

[therube]

How is mpv-hero (https://github.com/stax76/mpv-hero) (which I've not looked at yet) different / related to mpv.net ?

[stax76]

They are both easy to learn and use mpv GUIs, mpv.net is easier to learn and use, and it will probably stay that way. I intend to improve both, it depends on the feedback I get.

[stax76]

# v7.1.1.2 Beta (2024-10-10)

- Polish translation fixed. German, Turkish and Japanese translation updated.
French translation added! Thanks to the translation team!
- Support of relative folders from command line.
- Support for the mpv option `cursor-autohide`.
- A issue with the support of the mpv property `title-bar` has been fixed,
at the moment this is most useful for users of the popular uosc user script,
the mpv built-in OSC doesn't fully support it yet.
- `media-controls=yes` is now enabled by default, this enables play controls
in the `KDE Connect` android app.
- The mpv.net option `auto-load-folder` by default is now disabled and the
option is deprecated. The reason for this is mpv has new native support
for it using `autocreate-playlist`, which mpv.net uses now instead by default.
- New zhongfly libmpv x64 build.
- New Andarwinux libmpv ARM64 build.

[stax76]

I'm releasing a new mpv.net version with a few small improvements to mpv.net and the Command Palette script.


# v7.1.1.3 Beta

- Support for autocreate-playlist, video-exts, audio-exts, image-exts.
Windows 7 support should still work, but needs auto-load-folder to be enabled
or autoload.lua.
- The command palette user script is installable from the context menu under
`Settings > Setup > Install Command Palette`. The command palette features
are shown in the menu under 'View > Command Palette'.
- New command to select the stream quality `Video > Stream Quality (Alt+q)`,
this calls the Stream Quality feature of the command palette.
- mpv.net interacts with the Command Palette to enable the Recent Files
feature in the Command Palette.
- New zhongfly libmpv x64 build.
- New Andarwinux libmpv ARM64 build.


In the Command Palette script, there is improved default font size handing, so people get a good default font size with any DPI setting, people that customized the font size need to adjust.

[stax76]

I've updated and improved my awesome-mpv (https://github.com/stax76/awesome-mpv) project today.

There is not much mpv.net development, but I want to make a new beta release this or next year, if it becomes incompatible with libmpv, I will fix it.

[stax76]

Hello everybody,

I released the first beta version this year. I try to make at least one beta and one stable release every year.

On the issue tracker, I need to be more active.

I hope it works well.


# v7.1.1.4 Beta (2025-10-05)

- Support for select.lua has been added. It's a new Lua script built
directly into mpv like the osc or console script. It's similar to command_palete.lua.
- Fix --script-opt not working.
- The mpv.net manual was updated.
- The Turkish translation was updated. A Bulgarian translation was added.
Thanks to the translators!
- The required Dotnet version changed from 6.0 to 9.0. This drops Win 7 support
unfortunately. It was done to use new C# language features and make
the mpv.net project more attractive for new developers to contribute.
Also most users prefer having the newest runtime.
- auto build has been disabled because it requires updating libmpv and
mediainfo all the time which is too much manual work.
- The script src/Tools/update-mpv.ps1 has been improved. It's the easiest way
update mpv and libmpv (x64 and ARM64). Shinshiro has a update script too,
but it's a lot longer and more complex.
- mediainfo and libmpv have been updated.

[v0lt]

Thank you.
I tested it, it works.

Could you explain why developers use .NET Standard Term Support instead of Long Term Support?
.NET 9 STS 2024-11-12 ... 2026-05
.NET 8 LTS 2023-11-14 ... 2026-11
LTS support is one and a half years longer than STS.

[stax76]

Thanks for the interest. I think younger users and developers are more excited than older people about the latest and greatest features and software. For me, it's not a problem to wait a few years, I cannot remember many programming features anyway, poor memory. I'm looking for a new developer because I can no longer spend a lot of time on my software projects, mpv.net and awesome-mpv are the only projects I still maintain.

mpv/libmpv is written in C, and it requires at least Windows 10, this is not because of mpv, but because of a mpv dependency requires it and Linux developers don't care much about Windows 7 support.

[v0lt]

My question is not about Windows 7 support.
Support for your chosen .NET 9 STS will end earlier than support .NET 8 LTS.

[stax76]

I don't know what implications the difference between STS and LTS has. Is your concern security related?

If enough people request LTS, I can change it to use LTS, v10 comes out in December I believe.

[v0lt]

I don't know what implications the difference between STS and LTS has. Is your concern security related?
As a user, I don't like having to install new versions of .NET frequently. I'd like to do it less often. Long Term Support versions are preferable in this regard.

[stax76]

I understand and will update it to use v10 LTS, v10 is scheduled for this November.

[therube]

How to change the (Windows) taskbar icon (of mpv.net)?

I tried Resource Hacker (http://www.angusj.com/resourcehacker/), & with that the desktop icon changed, but not the taskbar icon.
(With other programs I've messed with, Resource Hacker seems to do the job. With mpv.net, I'm only getting partial results.)

(I'm on Win7, & I've been using 7.1.1.3, but never got the F8 "playlist" to work, so I reverted to 6.0.4, but now my audio instance of mpv.net uses the same taskbar icon as my "video" instance, making hard to distinguish. [And with the back end changes to 7.1.1.4, I'm left out altogether.])

[stax76]

I uploaded a new beta release today with small improvements.

# v7.1.1.5 Beta (2025-11-20)

- Same as in mpv the `?` and `t-4` keys can be used to show the active
key bindings on-screen, it supports scrolling and searching.
In the context menu it's located at:
`View > More > Show Active Bindings On-Screen`
- Bindings of select.lua menus have changed:
`F1` On-Screen menu
`F2` Bindings
`F3` Properties
`F4` Commands
- The German, Chinese, Japanese and Turkish translations were updated. Thanks to the translators!
- Users need to install .NET 10 LTS (Long Term Support), it should run on Windows 10.
It was requested by users to prefer LTS over STS (Short Term Support).
- libmpv and MediaInfo was updated.