LAV Filters - DirectShow Media Splitter and Decoders

[Nevilne]

So I've installed 0.61.1, noticed that watching avisynth scripts works terrible with lav-potplayer-madvr, installed 0.60 and can't open .avs anymore??
Installing ffdshow and ticking avisynth and raw video does nothing. Ok, back to 0.61.1, installed with installer:

With 0.61.1-potplayer-madvr i have to wait 5 seconds for video to start after every unpause. But it's fine with mpc-hc and madvr or in potplayer with evr-cp.

Now, it's kinda hard to see what's the problem is out of madvr/lav/potplayer, as I updated them all at once and can't revert to previous lav version, but:

When I use mpc-hc there's a lav video decoder in filter list (lav splitter-lav video-madvr), but in potplayer it's just splitter and madvr (and yes it plays video).
After i switch to evr-cp lav video appears and 'delay after resume' is gone. after i switch back to madvr lav video stays and 'delay after resume' is still gone.
If i force lav video to 'preferred' in potplayer, it loads lav video and there's no 'delay after resume'.

Also, potplayer uses async source+lav splitter for avs unless I force lav splitter source, although it's configured to use lav splitter source for everything.

Don't know what to make out of all this really but I hope there's a resolution.

[Asmodian]

How does it work in MPC-HC? That sounds like a PotPlayer issue not LAV's.

[nevcairiel]

Sounds like you enabled madVR's decoders. If LAV Video isn't even used, and even more, the issue goes away when its used, its definitely not a LAV issue.

[NikosD]

I want to ask a little more technical question about HW de-interlacing and LAV Video options.

There is an option of HW de-interlacing activated only using QuickSync or NVCUVID, called Adaptive HW deinterlacing.

Is the algorithm used by this option, different/ better than the default HW algorithms selected automatically by EVR/ EVR-CP when using DXVAn for Nvidia and Intel HW decoders ?

The comparison should be CUVID vs DXVAn for Nvidia regarding HW deinterlacing algorithms and QS vs DXVAn for Intel.

Not Nvidia vs Intel.

[nevcairiel]

Its the same deinterlacing algorithm, just performed by the decoder immediately after decoding instead of the renderer later - but otherwise exactly the same GPU deinterlacing.
Both the CUVID library and Eric's QuickSync Decoder offer a simple option to turn it on, so it was trivial to add it - and it can be useful if you want to do post-processing on the image, or for transcoding.

In theory it could also be implemented for DXVA2-CB, but its quite a lot of effort and IMHO not generally worth it.
For DXVA2-Native it doesn't make any sense, since you cannot use it for post-processing or transcoding anyway, and the renderer comes immediately after the decoder.

[NikosD]

Thanks

[P.J]

Originally Posted by wanezhiling

1. YADIF won't work in dxva2n mode.
2. You use LAV in PotPlayer? Then disable PotPlayer's built-in video processing filter.

1. I don't use DXVA2n 2. No, I use MPC-HC with LAV.
I have no problem in PotPlayer since I can select HW/SW de-interlacing method there.
And I don't use LAV with PotPlayer. I want to have software de-interlacing with LAV+MPC-HC

[NikosD]

If you want SW de-interlacing you have to forget HW decoding too.

You have to use SW decoding for SW deinterlacing.

So, put in hardware decoder option "None" and then Enable YADIF.

You will have SW decoding and SW deinterlacing, although I really don't understand why you want SW deinterlacing.

All of my clips tested with HW deinterlacing look better than YADIF for all three HW decoders (Intel, Nvidia, AMD)

[sneaker_ger]

Originally Posted by NikosD

If you want SW de-interlacing you have to forget HW decoding too.

You have to use SW decoding for SW deinterlacing.

No, you don't. Only DXVA2 native doesn't work with sw deinterlacing in LAV Video.

[NikosD]

So if you select DXVA-CB or QS for Intel and NVCUVID for Nvidia you can have SW de-interlacing ?

I'll try it.

I always use DXVAn for HW decoding.

UPDATE:

Yes, SW deinterlacing works for both DXVA-CB and QS.

[DragonQ]

Originally Posted by NikosD

I really don't understand why you want SW deinterlacing.

All of my clips tested with HW deinterlacing look better than YADIF for all three HW decoders (Intel, Nvidia, AMD)

Depends on your hardware. I highly doubt a 5 year old nVidia/AMD/Intel card has the same deinterlacing algorithm as a current model.

Also, if you have a really crap GPU then using software deinterlacing can take offload some of the burden to the CPU. I agree that hardware deinterlacing is generally better though.

[P.J]

Ok, just found the issue and it's because of playing a 1080i H.264 4:2:2 video.
LAV makes MPC-HC to encode via CPU (correct) but de-interlace via GPU!
And nothing lets me to change HW de-interlacing to SW/QS de-interlacing for that file.

[NikosD]

Originally Posted by DragonQ

Depends on your hardware. I highly doubt a 5 year old nVidia/AMD/Intel card has the same deinterlacing algorithm as a current model.

I'll check my 7 year old Radeon 3650 (UVD+) card against SW de-interlacing on some difficult H.264 and VC-1 interlaced clips and I'll tell you.

[nevcairiel]

Originally Posted by P.J

Ok, just found the issue and it's because of playing a 1080i H.264 4:2:2 video.
LAV makes MPC-HC to encode via CPU (correct) but de-interlace via GPU!

Are you sure you enabled YADIF Software Deinterlacing in LAV Video? It supports deinterlacing 4:2:2 too.

[P.J]

Originally Posted by nevcairiel

Are you sure you enabled YADIF Software Deinterlacing in LAV Video? It supports deinterlacing 4:2:2 too.

Yes, no problem with MPEG2 1080i 4:2:2 but H.264 1080i 4:2:2
QS/CUDA de-interlacing methods don't work for both too.

[nevcairiel]

QS/CUDA only works if the hardware decoder for those is used as well, which is not compatible with 4:2:2 in general.
How do you know its not working? I just tested such a file, and it deinterlaces fine.

Note that it only deinterlaces 8-bit, if you are using 10-bit 4:2:2 videos, you're out of luck.

[P.J]

Originally Posted by nevcairiel

QS/CUDA only works if the hardware decoder for those is used as well, which is not compatible with 4:2:2 in general.
How do you know its not working? I just tested such a file, and it deinterlaces fine.

Note that it only deinterlaces 8-bit, if you are using 10-bit 4:2:2 videos, you're out of luck.

Oh yes, it's 10bit H.264 1080i 4:2:2, HW Nvidia GT640 can de-interlace it but SW YADIF can't.
Any chance to add SW Motion/Vector adaptive instead of YADIF?

[nevcairiel]

In theory YADIF supports those, maybe I can hook that up for a future version.
But for now, no deal.

[P.J]

Any chance to add SW Motion/Vector adaptive instead of YADIF?

[nevcairiel]

If you provide a patch to do so, sure.

If you want better quality deinterlacing, let your GPU do it.