Hello,Remi was completely right:
I changed (via tools -> preferences -> input/codecs ->) hardware-accelerated decoding from automatic to disable
and now everything is just dandy (no more need to constantly deselect image-adjust),
thanks for helping an(other) ignoramus out !
Indeed, set hardware-accelerated decoding from automatic to disabled (via tools -> preferences -> input/codecs ->) solves the issue after update to 3.0.3 Vetinari.
A shame the development team didn't set this to default in the update, but hey....: we all make mistakes and this is only a small one.
I registered to help with solving this problem.
the fix posted above worked for me. I'm not sure what logs you're looking for.
GPU info below
discrete https://www.techpowerup.com/gpuz/details/bha27
cpu embedded https://www.techpowerup.com/gpuz/details/zvwzb
cpuz vali: https://valid.x86.fr/n4jvd9
let me know if there's anything you want me to try / change.
Code: Select all
main debug: auto hiding mouse cursor
direct3d11 debug: unhandled source transfer 0
direct3d11 debug: unhandled source transfer 0
freetype debug: DWrite_Fallback(): family: arial, codepoint: 0xd
freetype debug: DWrite_Fallback(): returning Segoe UI
freetype debug: DWrite_GetFamily(): family name: Segoe UI
freetype debug: DWrite_ParseFamily(): using font at index 0 with weight 400 for bold: 0, italic: 0
freetype debug: DWrite_ParseFamily(): using font at index 1 with weight 700 for bold: 1, italic: 0
freetype debug: DWrite_ParseFamily(): using font at index 2 with weight 400 for bold: 0, italic: 1
freetype debug: DWrite_ParseFamily(): using font at index 3 with weight 700 for bold: 1, italic: 1
direct3d11 debug: unhandled source transfer 0
main debug: VoutDisplayEvent 'mouse button' 0 t=8
main debug: VoutDisplayEvent 'mouse button' 0 t=9
main debug: auto hiding mouse cursor
direct3d11 debug: unhandled source transfer 0
main debug: toggling resume
main debug: toggling resume
main debug: toggling resume
mmdevice debug: state changed: 0
Here is the log. Thank you very much for your help.Hi,
@NonToxic628: it might be easier to create a new subjet. Either way, are you turning debugging logs in the message window, before starting the video ? It might not be an error.
Your hardware looks quite old for this kind of playback.
@moronicsmurf: can you provide the full logs ?
So is there a way to force the CPU to decode instead, or am I in the same boat with the 3930k?You're trying to play 4K HEVC, but your GPU cannot decode it. So it's not in software. Which is pretty much impossible in realtime. That's why you see only black, no frame is ever decoded in time to be displayed.
Ok thanks. Its interesting because the CPU isn't really turning up when I try to run one of these files. The utilization is sitting around 12% and that is with some other stuff going on in the background. I may just need to buy a new videocard and offload the processing to it as the 3930k has done everything else I have asked it to without any issues."So it's not in software" -> "So it is in software". It's is the CPU decoding, but it's too slow for such a large video.
Return to “VLC media player for Windows Troubleshooting”
Users browsing this forum: Google [Bot] and 92 guests