Open dexeonify opened 1 year ago
Sounds like a possible difference in libplacebo version, where the older one in vs-placebo causes issues. I assume you used a recent FFmpeg build?
It could help if you provide the debug log by adding log_level=5
to the placebo.Shader
call.
In the meantime I started a build to test with the latest libplacebo here: https://github.com/quietvoid/mpv-winbuild-cmake/actions/runs/5163637750 When it's ready it'll output the updated vs-placebo DLL.
I assume you used a recent FFmpeg build?
Yes, I usually use the ffmpeg
git. However, libplacebo also works for me on the release version of ffmpeg
- v6.0 (which is 2023-03-04, according to Gyan.dev).
Contrary to the guides I found online, I do not need to specify hwupload
and hwdownload
for libplacebo to work. In fact, these two parameters caused libplacebo to fail for me.
It could help if you provide the debug log by adding
log_level=5
to theplacebo.Shader
call.
There doesn't seem to be additional logs? For reference, I'm getting the logs using this command line:
vspipe -c y4m placebo.vpy - | mpv -
There doesn't seem to be additional logs? For reference, I'm getting the logs using this command line:
vspipe
hides stdout logs.
You can try adding video.get_frame(0)
to your script and just running it with Python.
I found this which seems like a similar issue to what you're seeing: https://github.com/haasn/libplacebo/issues/172#issuecomment-1567589476 So I'm going to guess the updated libplacebo might fix your issue. Or maybe it is an Intel driver problem.
Can you try this: https://github.com/quietvoid/mpv-winbuild-cmake/suites/13347837213/artifacts/729911053
It's vs-placebo
built on latest Vulkan/libplacebo: https://github.com/quietvoid/mpv-winbuild-cmake/actions/runs/5163637750
Unfortunately, no. The silver lining is the backtrace log is more verbose.
I'm not sure what's going on and if it's something that needs to be fixed in vs-placebo
.
Seems to be Intel specific at least.
Oh well, let's see if there's any progress on haasn/libplacebo#173. Unlike the OP though, I can get libplacebo to work in ffmpeg
.
When I try to use any shaders with
core.placebo.Shader()
, I get a green blank output in VapourSynth-Editor or when piped to mpv. When I pipe to mpv, I get this error repeatedly printed out in the terminal:I've done a few checks myself:
vs-placebo
release version (1.4.4)ffmpeg
'slibplacebo
works, hardware incompatibilities shouldn't be an issuelsmas
andffms2
doesn't change the outputcore.placebo.Deband()
works, sovs-placebo
is definitely loaded correctlyadaptive-sharpen
YUV444Px
as requested before passing it off to the shader functionI'm out of ideas.
Environment
CPU: Intel Core i7-9700 RAM: 8GB GPU: Intel UHD Graphics 630, No external GPUs OS: Windows 11 Build 22621.1778
Minimal Working Example