Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

MPV: gpu-next + Vulkan causes Anime4K to malfunction. #144

Open
Artins90 opened this issue Nov 15, 2021 · 9 comments
Open

MPV: gpu-next + Vulkan causes Anime4K to malfunction. #144

Artins90 opened this issue Nov 15, 2021 · 9 comments

Comments

@Artins90
Copy link

Artins90 commented Nov 15, 2021

I might be getting ahead of myself by submitting a bug report for an in-development rendering option but I find the HDR passthrough of the new gpu-next quite useful.

Unfortunately gpu-next seems to break Anime4K, making lines disappear and darkening the image

Anime4K OFF [gpu-next + Vulkan]:
Screenshot (71)

Anime4K ON [gpu-next + Vulkan]:
Screenshot (72)

Anime4K ON [gpu-hq + DX11]:
Screenshot (73)

@bloc97
Copy link
Owner

bloc97 commented Nov 15, 2021

gpu-next is the new rendering pipeline based on libplacebo, right? I'll keep an eye out on this as there should not be any differences between running shaders on gpu vs gpu-next, as libplacebo implements the same hook syntax as mpv.

@Artins90
Copy link
Author

Yes, from the mpv manual:

"gpu-next
Experimental video renderer based on libplacebo. This supports almost the same set of features as --vo=gpu. See GPU renderer options for a list.

Currently, this only supports --gpu-api=vulkan, and no hardware decoding. Unlike --vo=gpu, the FBO formats are not tunable, but you can still set --gpu-dumb-mode=yes to forcibly disable their use.

Should generally be faster and higher quality, but some features may still be missing or misbehave. Expect (and report!) bugs."

@Artins90
Copy link
Author

I just tried using Vulkan with vo-gpu and, as hooke007 suggested, Vulkan on its own is triggering the issue, I think it's safe to assume it's a Vulkan issue.

@hooke007
Copy link

hooke007 commented Nov 16, 2021

I deleted the post for I am not sure if it was caused by the vulkan driver or mpv's vulkan api. Maybe report it to mpv?

@hooke007
Copy link

@bloc97 Sry to disturb u, after one commit (not sure which one) of upstream, restore_CNN_M didn't work properly with vo=gpu-next gpu-api=vulkan mpv-player/mpv#9505 (aliasing or no change at all)
I wish I was not the only lucky one to meet with the issue. still reproduce here by this build. 20211212 https://sourceforge.net/projects/mpv-player-windows/files/64bit/

@bloc97
Copy link
Owner

bloc97 commented Dec 12, 2021

Hmm... it seems that gpu-next doesn't like //!SAVE MAIN. If you remove that line the shader Anime4K_Restore_CNN_M works correctly. The same can be applied to the upscale shaders.

@hooke007
Copy link

Eh, work for some kinds of cases, but could still produce aliasing in my case.

@bloc97
Copy link
Owner

bloc97 commented Dec 13, 2021

Really? I couldn't reproduce aliasing problems after removing all the //!SAVE MAIN from the shaders.

@hooke007
Copy link

hooke007 commented Sep 1, 2022

but could still produce aliasing in my case.

With more tests I found it would happen on 720p source(paused) but not 1080p.

apply single Anime4K_Restore_CNN_M.txt (no //!SAVE MAIN)

origin --------------------------------- gpu --------------------------------- gpu-next
-- --

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants