-
Notifications
You must be signed in to change notification settings - Fork 2.8k
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
[hwdec_d3d11va] No hardware acceleration with H264 #5420
Comments
This appear to be a bug in |
@shinchiro is there a some workaround for this cause looks like this will not going to be fixed soon.I still don't see any response from the devs here. |
It's been discussed on IRC. The windows hwdec wscript deps are currently a mess. The workaround for now is to compile with ANGLE. |
Got it.Thanks for the update @kevmitch |
Looks like the bug has been fixed so i'm closing this to reduce the ticket clutter. |
Well, technically, that hasn't been merged yet. It will be in the next hour or so. |
mpv version and platform
mpv-x86_64-20180120-git-dba143d (latest build by shinchiro)
Windows 10 x64 LTSB 1607
Reproduction steps
Playing any h264 file with --vo=gpu --gpu-context=d3d11 --hwdec=d3d11va
Expected behavior
To be hardware accelerated by my eGPU(NVIDIA) as the previous build(s) did
Actual behavior
THIS:
0.584][v][vd] Opening video decoder h264
[ 0.584][v][vd] Looking at hwdec h264-d3d11va...
[ 0.584][v][vo/gpu] Loading hwdec driver 'cuda-nvdec'
[ 0.584][v][vo/gpu] Loading failed.
[ 0.584][v][vd] Could not create device.
[ 0.584][v][vd] Using software decoding.
I know that you guys did some changes but didn't expect to cut all(or at least most of it) codec support from d3d11. What is the point to have good GPU if you can't even use it to watch some videos?
What i see so far is that the VSync Jitter increased from 0.007(full screen) to 0.070 and there is much more pressure on the CPU.Bring back the codec support PLEASE !!!!!!
Log file
log.txt
The text was updated successfully, but these errors were encountered: