The VideoLAN Forums

Does it work if you disable the generate HDR mode ?

It's OK. I managed to reproduce the issue and fix it. The fix will soon be in nightlies https://code.videolan.org/videolan/vlc/ ... uests/5562

Wasn't it "wcscat_s" instead ? It's a very recent addition in 3.0.21.

53x Drivers work, 54x Drivers don't work. Maybe we're doing something wrong, but it seems the drivers are behaving differently now. And since it fails in the driver there's no way for us to tell...

I can reproduce the issue on a RTX 3070 and 546 Studio drivers. Going fullscreen (double click on the video) it works fine. But resizing manually gives this issue: NVWGF2UM: Failed to run Algo 2 of Stream 1. D3D11: Removing Device. direct3d11 vout display error: SwapChain Present failed. (hr=0x887A0...

Thanks for the report. For some reason libavcodec cannot handle this file and it crashes during probing. A fix is coming. It works fine when switching to dav1d.

The nightly with the fix is the one from 2023-10-16, not from 2023-10-15: https://artifacts.videolan.org/vlc-3.0/ ... 1016-0220/

What OS are you using ? Does it crash with D3D11 ? Can you provide logs when disabling hardware decoding with D3D11 ?

The bar code is "0 31398 31493 6 80" There are also two codes printed on the disc itself in the clear inner ring: "9855 A0576961 N00120-01Z 4635 SP" and "9855 A0576960 N00106-19Y 6875 SP" The only other code I have access to is the public library's internal identificat...

One issue that 3 4K HEVC streams might be using too much memory from the GPU. In 4.0 we use less memory for hardware decoding. In 3.0 you might reduce that amount by using a single decoding thread (instead of 3 you seem to set).

Can you try with the open GL or Direct3D9 outputs ? I assume you're using the Direct3d11 one.

Your GPU cannot decode 10 bits HEVC, so it's decoded in software. But in software your computer is too slow to decode so playback is not smooth and many frames are dropped.

It says 6 GB, not 16 (which would be a lot on a laptop or even in general). I think it's a memory size issue. In 4.0 we will less memory to do the same decoding. But huge files like this will always have problems on some config.

direct3d11 debug: Direct3D11 Open Succeeded main debug: using vout display module "direct3d11" main debug: removing module "direct3d11" direct3d11 debug: Direct3D11 resources destroyed Unfortunately it goes through an error path that has no log. Not sure what happened. It opened...

I reopened issue https://trac.videolan.org/vlc/ticket/21329 to solve this issue.

Hi, I looked at the files. The source file is marked as BT.470 for the Transfer Function and the Matrix Coefficients (according to MediaInfo). In the destination file the values are BT.709 for the Transfer Function and BT.601 for the Matrix Coefficients. You are using Direct3D11 so the colours are a...

At the very least the doc is not clear. But it doesn't make sense to provide a size to the host app without telling it what display size it should be.
Plus this API provides planes pitch but doesn't even tell how many planes there are...

I don't understand the same app but it is possible to enable/disable `avcodec-hw` through libvlc. There are cases where it's not going to work though. For example if you use `libvlc_video_set_callbacks()` or `libvlc_media_player_set_hwnd()`. When you create your media to play, you can add options, f...

Can you try this build and provide the logs in Automatic ? https://nightlies.videolan.org/build/win64/vlc-3.0.6-20190109-0510/ (it has more debug info about why we don't detect the drivers) It's possible to get things working with D3D9 but we really want to fix it with D3D11 which is the way forward...

Same problem here. I have a Core i7, 16GB of RAM, a GTX970, which definitely supports HVEC, and the latest available version of VLC. I have tried using the various setting recommended to stop this problem to no avail. If I DISABLE hardware acceleration, the problem disappears, but then everything e...

The log still doesn't say the WDDM driver version. I'll add some logs to find out what is failing there. If you are on Windows 10 you can see the WDDM drivers in the Task Manager when you click on your GPU in the Performance tab. It should be something like Driver Version: 25.10.14011.123 . Otherwis...

What is the WDDM driver version ? It's supposed to show up in the logs but it doesn't.

If the revision build is older than 14011 it won't work (and we don't blacklist your GPU yet). Can you also provide logs from 4.0 nightlies ? The WDDM version detected should show up there.

It's possible we don't support that in a MRL

It's the deinterlacing that is taking too long just before displaying. It's both a design issue in VLC that is doing it too close to the display time, but also your GPU is quite slow to do it.

Did you try resetting the preferences ?