The VideoLAN Forums

Do you have a sample file ?

Do you have the text resolution different between the two screens ? The "scale and layout" in the Windows 10 display properties should tell you.

I finally found the problem and the solution. The tone mapping was done but BT.2020 colors (wide gamut) was not converted to BT.709 (smaller gamut). That explains the less saturated colors (smaller values were not expanded). This is fixed in the 4.0 master and will be available in the nightly builds...

It would be useful to provide some verbose logs (2 : debug). You can press 's' to stop playback after a few flashes. With the logs we should be able to tell what's the issue.

The washed out colors should be better in 3.0 especially since 3.0.2.

For the stuttering you may have to force ffmpeg threads to 1 when using hardware decoding. Otherwise the GPU sometimes get overloaded and it can cause stutter.

4:4:4 or 4:2:2 HEVC is not supported by hardware decoders, at least not in VLC/ffmpeg via DVXA. So yes you should stick to 4:2:0 if you want hardware decoding.

And software decoding of such a file (>4K) with an old 4770k is probably not going to work either.

"mkv debug: found nothing, go up"

Thats' usually a sign the file is broken or may not be fully downloaded (from torrents).

Also can you change the ffmpeg-threads preference to 1 (instead of 0) ?
Preferences > show all > Input/Codecs > Video Codecs > FFmpeg > Threads

And see if it helps.

So going back to VLC 3.0.3 works ???

You may change the output module in the Preferences and see if it has any effect. There's a chance the 2.2 was using an older Windows API and 3.0 is using the newer one.

qt4 is not in VLC 3.0, we're using Qt5. So you must be using an outdated version of VLC.

Can you provide the verbose logs of what happen before ? And also select different deinterlace algorithm from the UI (and even disable deinterlacing to see if it helps).

What OS version are you using ? Normally we ask the OS what the display can support and try to adapt to the source as much as possible. That's D3D11SetColorSpace() in the code. But if your OS is too old (no IDXGISwapChain3) it won't be used and we use the default for the old OS values (RGB full rang...

What are you driver versions ? Can you try with a 3.0 nightly build from here ? https://nightlies.videolan.org/build/wi ... 0717-0549/

Can you try using only one thread for the ffmpeg codec ? In the advanced preferences > Input /Codecs > Video codecs > FFmpeg > Threads : 1 instead of 0

Did you use HOST-TRIPLET literally or you replaced it with a proper value ?

The logs are incomplete, it fails to use D3D1 (because the GPU is too old) but we don't see when it's trying D3D9/DXVA2

Can you provide verbose logs for the 3.0 so we can know what's going on ? Thanks

Are you using VLC 3.0 ?

What version are you using ? Is it playing or immediatly crashes ?

Windows has a feature to disable the screensaver. You should use that rather than an outdated version of VLC.

How did you install it ? Do you have a file VideoLAN\VLC\plugins\plugins.dat ? If not you can drag & drop the plugins folder over vlc-cache-gen.exe and it will generate it.
The installation should have done it though.

You have one of these Intel GPUs that say they can decode HEVC but really can't. It will be blacklisted in the next release.

That's probably because it's using the hardware deinterlacer. Depending on your GPU it may not support all the possible options. You may disable hardware decoding but then it will use a lot more CPU.

This might be due to a profile not supported by the GPU. Can you provide the file or at least the beginning of it ? Or alternatively the logs from MediaInfo ?

Or the result of DXVA Checker. It seems your GPU is using outdated drivers.