LAV Filters - DirectShow Media Splitter and Decoders

[madshi]

I'm not sure if that's my problem or LAV's problem? Could be that my D3D11 pixel shader is somehow not compatible with DX9 GPUs. Or could be that the D3D11 device created by LAV needs to be created with different flags? I don't know. nevcairiel, what do you think?

[nevcairiel]

No idea without any hardware at hand. I can go dig in my GPU bin to see if i still have something that old but yet still with decoding support.
Check with EVR if copy-back works, as one intermediate step? That'll tell you if decoding works.

The best, er.., worst, I can do is apparently a GTX 260-216, which is a DX10 GPU. Will test that tomorrow.

[Great Dragon]

Hello,

Is it OK that using NVIDIA CUVID decoder makes GPU to run on maximum performance (clock speed)?
While using regular DXVA renderer a GPU performs in regular Desktop Mode. I'm using GTX 1070.

Do I have some control over CUVID Renderer settings?
And what's the difference between CUVID and DXVA ?

[strumf666]

D3D11 native on intel HD2500 (I5 3470) works for me if that helps. Win 10 pro & Potplayer 64bit; intel drivers 10.18.10.4425
On a very quick test for H264, cpu utilization is a few % lower than on dxva2 copyback, but render times are much higher.

[aufkrawall]

Is it OK that using NVIDIA CUVID decoder makes GPU to run on maximum performance (clock speed)?

That's normal for all CUDA apps, CUVID unfortunately isn't an exception.
DXVA2/D3D11VA on the other hand will give you lower GPU clocks than even CPU decoding with madVR because the driver apparently chooses lower clock speeds when hardware decoding is going on than without.

I don't really see any reason to use CUVID anymore. imho both CUVID and QuickSync probably could even get removed out of LAV Filters in favor of the new D3D11VA decoding.
It's probably not too harsh when you say that CUVID and the used QuickSync decoder are end of life or even already dead.

[aufkrawall]

With new build, I can confirm that selecting IGP for decoding works with D3D11VA, great. :)
Buuut: Would it be possible to make copyback selectable like for DXVA2? Or do that automatically when a device is selected which is not the primary graphics adapter?
Kinda odd that it currently only works with renderers which refuse direct D3D11VA connection.

[AngelGraves13]

VC-1 playback doesn't work for me with DX11 LAV Video (0.70.2-45 nightly) and madvr 0.92.1b. Can someone else confirm this on their end? My GPU is a 1080 Ti. DXVA2 N and CB work fine. Also, software works fine too, as well as CUDA.

[nevcairiel]

Would it be possible to make copyback selectable like for DXVA2? Or do that automatically when a device is selected which is not the primary graphics adapter?

I didn't want a seperate entry in the decoder box because that doesn't allow seamless fallback between Native and Copy-Back.

However I have changed it now to only use Native when you select "Automatic" and updated the instruction hint to that effect. It probably makes the most sense to always obey user settings, and for testing purposes its probably a good thing as well.

VC-1 playback doesn't work for me with DX11 LAV Video (0.70.2-45 nightly) and madvr 0.92.1b. Can someone else confirm this on their end? My GPU is a 1080 Ti. DXVA2 N and CB work fine. Also, software works fine too, as well as CUDA.

VC-1 works just fine here. Make sure you don't use way too many buffers (ie. input queue size in madVR), it can sometimes cause decoding failures.

I should probably put an artificial limit in place for VC-1, it seems to be more affected by this then the others, but I would generally not recommend to use extremely large decoder queues in madVR either way.

[aufkrawall]

I think with native hardware decoding, it's safe to stick to a queue which is as short as possible on the GPU side (aka 4 frames with madVR).
With a short GPU/presentation queue, there are sometimes presentation glitches reported after the playback started, but I haven't yet seen any at a later time. + it also reduces input lag when e.g. changing volume via mouse wheel.
However, setting CPU queue (isn't it actually a D3D11VA queue in our case?) to only 4 frames as well gives me some weird intensive stuttering which is not detected by madVR's stats. It already seems to be gone with 5 frames, but for safety I set it to 8.

Only 12 more hours till next nightly build. :o

[nevcairiel]

4 is probably too short, especially because it also limits the GPU queues then, I would go with 8 or 16 at most personally.

I've been thinking about more strictly limiting the maximum number of surfaces in all cases to something reasonable like 32 (which is used for VC-1 now). There is a hard limit of 127 (ie. 7-bit), which is required for DXVA to function at all, but using that many buffers really has no advantages in native mode.

[AngelGraves13]

VC-1 works just fine here. Make sure you don't use way too many buffers (ie. input queue size in madVR), it can sometimes cause decoding failures.

I should probably put an artificial limit in place for VC-1, it seems to be more affected by this then the others, but I would generally not recommend to use extremely large decoder queues in madVR either way.

I have them both maxed in madvr. 24 for GPU and 128 for CPU. It looks better for smooth motion, but a limit should be put in place if it's a problem in DX11. Why does it work fine in every other mode with large queues except DX11? Is it a bug? Software, CUVID, DXVA2 Native and Copy-Back all work fine with 128 queue.

I also get random freezes if I pause and attempt to play a video with DX11, especially if I skip to a certain timecode and then pause. The player MPCH-HC locks up under DX11, but DXVA2 Native and Copy-Back have no issues.

[nevcairiel]

The CPU queue doesn't affect anything with smooth motion. Don't buy into snake oil explanations. :p
Such a huge CPU queue has zero benefit, just eats up your memory and makes seeking/startup slower.

[el Filou]

I watch a lot of DVB, and sometimes there are errors in the feed due to bad reception and I find that when this happens, having a bigger decoding queue smoothes things out a bit (i.e. the hiccup due to lost packets is less brutal), but nothing quite as big as 128 (I use 24).

[aufkrawall]

It works like a charm now, nev. Very cool tech, thanks for making it possible!
I thought my Skylake IGP wouldn't be able to decode HEVC 10 bit, but apparently it is (with high GPU usage, so likely hybrid).

[Goeggel]

No hardware acceleration with 4K videos

I have been looking around the web for possible solutions and have fiddled with the settings, but haven't had any luck so far. When playing 1080p videos, I get hardware acceleration and LAV shows my GTX 980 as active hardware device.

However when playing 4K videos (for example Exodus or Life of Pi HDR demos), no active hardware device is shown. Is this a known issue?

Windows 7 64bit
Nvidia GTX 980 384.94
LAV 0.70.2 / DXVA Copy-Back
madVR 0.92.1
Zoom Player 13.5 Max

[LigH]

Not every graphic chipset supports hardware accelerated decoding for every video format (AVC/HEVC, Profile@Level + several specific encoding complexity attributes) in every resolution. There are limits.

[nevcairiel]

The 980 doesn't have full HEVC decoding, and no HEVC 10-bit at all, which would be required for those HDR demos. Like LigH said, older hardware doesn't support all newer formats.

[huhn]

is d3d11 headless mode also planned for the next release?

so i take the nightly 0.70.2.49 as a yes.
fantastic feature very useful!

[aufkrawall]

One more observation regarding queue length + madVR:
DXVA deinterlacing really doesn't like a small GPU queue. When I set it to 4 and presentation queue is 4 frames as well, I'm getting framedrops. Setting GPU queue to 8 seems to be enough to avoid drops with DXVA interlacing.

[nevcairiel]

Yeah 4 might be too short, but 8 is fine, or even 16 if you must, with an absolute maximum of 32. Anything above that seems wasted.

[aufkrawall]

I noticed two issues with the current nightly:
-YADIF doesn't work for VC-1 interlaced (without software deinterlacing, LAV reports interlaced content properly to renderer).
-When changing the YADIF setting when LAV config is opened via MPC HC filter list, it makes the player invisibly hang in background after closing.

[VictorLS]

For people who still like WinXP - last working version of subj is LAVFilters-0.70.2-16 and it's a pity (as all non-modified LAV Video Decoders) it can't hardware decode H265 10bit via CUVID on nVIDIA's GM206-based videocards - it seems nevcairiel too hard understand how it was made working (but it's just few strings of code).
Next installer LAVFilters-0.70.2-29.exe says "This program does not support the version of Windows your computer is running."
Best regards.

[aufkrawall]

Btw: What's the reason for the brief corruption after seeking in HEVC 10 bit video? It happens with both software and hardware decoding, but not in the Windows 10 video app.

[sneaker_ger]

Container (TS?)? Sample?

The FFmpeg TS demuxer does not offer such functionality (it doesn't know what kind of frames are in the stream, since thats codec dependent information and mpeg-ts itself does not carry such flags), and I do not currently plan to work on this myself.
I could maybe hide the frames (like h264 does) if that makes you feel better? :) It would still start decoding a "proper" image at the same spot as it does now though.

MPEG-TS is generally not a format you should expect "perfect" seeking on, because the format itself has basically no seeking support. Even finding the appropriate timecode in the file is already a slow process, and with broadcast streams can even be really annoying (ie. with wrap-around).

[nevcairiel]

-YADIF doesn't work for VC-1 interlaced (without software deinterlacing, LAV reports interlaced content properly to renderer).


That should be fixed.


-When changing the YADIF setting when LAV config is opened via MPC HC filter list, it makes the player invisibly hang in background after closing.

I can't reproduce that. All settings changes are really quite equal, change the value, save it. It doesn't do anything special for those settings.

[aufkrawall]

Container (TS?)? Sample?
You nailed it, both tested files have TS container. Thanks.


I can't reproduce that. All settings changes are really quite equal, change the value, save it. It doesn't do anything special for those settings.
I can always provoke it by turning YADIF off in a paused video and then close MPC HC.

[nevcairiel]

Seems like an odd way to do things, but I've found a work-around for the issue.

[mitchmalibu]

Hey, great work on LAV filters. I did have a quick question though.

Using a youtube clip downloader (https://yd.3dyd.com/), I downloaded a 60fps 4K clip on youtube (https://www.youtube.com/watch?v=ArPP6_QXqyQ) and watched it with the latest LAV + madvr available using D3D11 hardware decoding. It worked perfectly, lav video reporting that the active decoder is D3D11 native and madvr OSD showing the DXVA11 flag. I also tried to download another 60fps 4K clip, but with HDR (https://www.youtube.com/watch?v=GTGm7mye-_4). The file isn't hardware decoded, LAV video showing that avcodec is active. Both files are straight from youtube so encoded with VP9.

Is this an expected behaviour ?

Thanks !

[sneaker_ger]

For HDR Youtube provides VP9 10 bit - for SDR only 8 bit. 1070 cannot decode VP9 10 bit. So if you downloaded the VP9 10 bit stream that should be the reason.

[LigH]

Not every graphic chipset supports hardware accelerated decoding for every video format (AVC/HEVC, Profile@Level + several specific encoding complexity attributes) in every resolution. There are limits.

Sorry for shameless self-quote :p – and yes, VPx is another issue, in relation to MPEG specified formats.

[mitchmalibu]

For HDR Youtube provides VP9 10 bit - for SDR only 8 bit. 1070 cannot decode VP9 10 bit. So if you downloaded the VP9 10 bit stream that should be the reason.

OK thanks, I knew there was a bitdepth difference, but couldn't find the exact decoding capabilities of the 1070.

[mitchmalibu]

Quick question: updating from nightly 45 to 49 and later, I loose DXVA11 native decoding, the active decoder now being D3D11 cb direct instead of D3D11 native. Is this normal ?

[mrcorbo]

Quick question: updating from nightly 45 to 49 and later, I loose DXVA11 native decoding, the active decoder now being D3D11 cb direct instead of D3D11 native. Is this normal ?

Did you select the active decoder instead of leaving it on automatic?

[mitchmalibu]

I did leave it on automatic. A settings reset solved it. Thanks

[Jasch]

Hi, a small info/bugreport.
with new Dxva11 +madvr deinterlacing is not working at all, dxva2native +copyback works fine.
Win10 Rx460 latest Madvr and Lav nightly

[sneaker_ger]

madshi hasn't implemented deinterlacing for D3D11 DXVA yet.

https://forum.doom9.org/showpost.php?p=1815291&postcount=44714

[Sunspark]

In build 0.70.2.66-git I have made the observation that in video filters if you select DXVA2 (native), it will display the expected NV12, 8 bit, 4:2:0 (DXVA2).

However, if you then change it to None, it continues to display NV12, 8 bit, 4:2:0 (DXVA2) even though software decoding should be in use at this point.

If you change it to DXVA2 (copy-back), it will display NV12, 8 bit, 4:2:0.

Then changing it to None, it displays NV12, 8 bit, 4:2:0.

Repeating the process where you go back to DXVA2 (native) and then None, None once again holds on to (DXVA2).

[nevcairiel]

It doesn't change without re-starting playback.

[Sunspark]

You are right. It is not enough to just stop playback, you have to quit out of the player entirely and restart it.

[sneaker_ger]

In MPC-HC there is a hotkey to restart. ( ctrl + e ?)

[XMonarchY]

What is the advantage of D3D11 DXVA? Faster rendering for rigs that support it? Does it improve image quality?

[SamuriHL]

There shouldn't be a quality difference in any of the decoding types. It's likely the benefit is resource utilization.

[huhn]

DXVA native with nvidia cards can result in quality loss if it is used with madVR for example. D3D11 doesn't have this problem.

on top of it D3D11 supports headless mode which is very useful for PCs that have a iGPU with very good codec support and a dGPU with not that good codec support.

[SamuriHL]

Well that's good to know about headless. I see I've been away from these things too long. LOL. D3D11 support seems very good to me in my latest tests with my new 1060. I had no issues with 3D playback which is awesome.

[yukinok25]

Well that's good to know about headless. I see I've been away from these things too long. LOL. D3D11 support seems very good to me in my latest tests with my new 1060. I had no issues with 3D playback which is awesome.

I am sorry if its a stupid question, but I can't understand how can I enable the D3D11 support in LAV Filter, I have only DXVA2 (copy-back) and all the others except D3D11?

What I am doing wrong?

[FDisk80]

I am sorry if its a stupid question, but I can't understand how can I enable the D3D11 support in LAV Filter, I have only DXVA2 (copy-back) and all the others except D3D11?

What I am doing wrong?

You install the latest Nightly.

[yukinok25]

You install the latest Nightly.I thought I did! Which is the latest versions, just to make sure?

Thanks for the help by the way.

[FDisk80]

I thought I did! Which is the latest versions, just to make sure?

Thanks for the help by the way.

https://files.1f0.de/lavf/nightly/LAVFilters-0.70.2-66.exe

[yukinok25]

https://files.1f0.de/lavf/nightly/LAVFilters-0.70.2-66.exeThanks!!

[fakel]

D3D11 DXVA it is a miracle, just do not understand how deinterlacing algorithm qualitatively?