LAV Filters - DirectShow Media Splitter and Decoders

[nevcairiel]

OGM is a broken format, I wouldn't expect many improvements, sorry.

[DragonQ]

Originally Posted by nevcairiel

As of 0.67.0-67, LAV Video supports a new software deinterlacer, Weston Three Field Deinterlacing Filter (w3fdif)

w3fdif was developed by the BBC, and as I understand it, is also used by them in real-world usage.

Well I wonder where they actually use this w3fdif filter because their deinterlacing method when doing slow/stop motion during sports replays is awful - it's basically weave. Even their method of adding real-time graphics to interlaced video doesn't look great and produces a tonne of shimmering and other artefacts.

I assume, and hope, the w3fdif filter is different.

[Alexey1975]

I have tested all of betas in 0.67 series and catch such an issue with some of sources.


704x576 AVC (High@L3 CABAC / 4 Ref Frames)

Release version LAV 0.67 just fine, but beta versions are buggy.

[nevcairiel]

As always, please provide a sample, otherwise there is nothing I can do.

[Alexey1975]

Excuse me, here it is http://www.ex.ua/98151805 the stream dump.
(DVBViewer 5.5.2.0 + MadVR 0.90.4 + LAV 0.67.0.76)

[nevcairiel]

Sorry, but your link doesn't work.

[Alexey1975]

Sorry, try this link https://yadi.sk/i/RfCr6RnMoSDhL

[nevcairiel]

Originally Posted by Alexey1975

Sorry, try this link https://yadi.sk/i/RfCr6RnMoSDhL

The file seems to decode fine, which decode mode do you use?

[Alexey1975]

Strange thing. I tried CUVID, DXVA-CB, DXVA-N modes with the same result...
Third-party decoders produce no any issues (just like release version LAV 0.67) with that stream, but 0.67-betas do!

[nevcairiel]

It breaks only in DXVA2 mode apparently. I get the same issue with 0.67.0 however, and with 0.66 and 0.65.
Same problem with Microsofts DXVA decoder.

Seems like either the stream is not compatible with DXVA for some reason, or its a hardware/driver issue.

[Alexey1975]

Just right now I rollback to the release version and it works just fine. I hope this strange things don't float up into the next release - I just want to help the beta testing. Thank you for attention.

[nevcairiel]

From what I can tell it never worked with DXVA2, same result in all recent release versions.
And like I said in my previous post, same result using the Microsoft decoder as well.

Software Decoding is perfectly fine however.

[Alexey1975]

Originally Posted by nevcairiel

It breaks only in DXVA2 mode apparently. I get the same issue with 0.67.0 however, and with 0.66 and 0.65.
Same problem with Microsofts DXVA decoder.

Seems like either the stream is not compatible with DXVA for some reason, or its a hardware/driver issue.

Microsofts DXVA2 decoder and etc. works just fine with this stream - i had no any problem before that betas.

[Alexey1975]

Originally Posted by nevcairiel

Software Decoding is perfectly fine however.

Confirm!

[nevcairiel]

Originally Posted by Alexey1975

Microsofts DXVA2 decoder and etc. works just fine with this stream - i had no any problem before that betas.

I can only tell you what I am seeing, and that is that its broken with DXVA everywhere. I tested 0.64 to 0.67, and the Microsoft decoder, and all behave *exactly* the same, so from my end, its not a new issue, and considering the Microsoft decoder looks just the same, it smells like a driver problem.

One simple explanation would be that earlier LAV versions for some reason just didn't use DXVA for you, because Software decoding works.

In any case, unless I can find one DXVA decoder that actually works, I have no proof that its actually supposed to work, and no starting point where to start poking.

[DragonQ]

Originally Posted by DragonQ

Well I wonder where they actually use this w3fdif filter because their deinterlacing method when doing slow/stop motion during sports replays is awful - it's basically weave. Even their method of adding real-time graphics to interlaced video doesn't look great and produces a tonne of shimmering and other artefacts.

I assume, and hope, the w3fdif filter is different.

Just had a quick check of this with some 576i/25 footage. YADIF definitely handles panning shots with diagonal lines (e.g. painted lines on a pitch) better. I was gonna compare to AMD's Adaptive Sync but it looks very broken with Crimson drivers so I can't...

[wanezhiling]

@Alexey1975, nevcairiel
That is Nvidia's hardware problem, ATI&Intel are just fine.

similar clip

[hoborg]

Hello.
Intel (HD6200) also working just fine.

[NikosD]

Originally Posted by wanezhiling

@Alexey1975, nevcairiel
That is Nvidia's hardware problem, ATI&Intel are just fine.

similar clip

Both files start with artifacts or black, frozen image but the video stream after a while is decoded just fine in DXVA mode using Win 10 - iGPU 4600 - Drivers 4331.

One thing that differentiates those two interlaced H.264 files, from all the "common" files that work fine using Nvidia HW decoder is this according to MediaInfo:

Color primaries : BT.601 PAL
Transfer characteristics : BT.470 System B, BT.470 System G
Matrix coefficients : BT.601

My other H.264 interlaced samples are BT.709, but I really don't know if that means something.

[nevcairiel]

Originally Posted by NikosD

One thing that differentiates those two interlaced H.264 files, from all the "common" files that work fine using Nvidia HW decoder is this according to MediaInfo:

Color primaries : BT.601 PAL
Transfer characteristics : BT.470 System B, BT.470 System G
Matrix coefficients : BT.601

My other H.264 interlaced samples are BT.709, but I really don't know if that means something.

That info is just metadata, its probably something about that specific way to encode interlaced.