LAV Filters - DirectShow Media Splitter and Decoders

[omarank]

I can confirm that the problem is fixed in the build v0.67.0-75. Thanks!

[Leader]

Hi, nevcairiel!

I found a bug in "LAV Video Decoder".

Incorrect playback this file: https://torrentreactor.com/torrents/6197645/APC-Princess-Mononoke-DVD-x264-07f4b3d1-ogm in LAV Video Decoder (DXVA2 decoding and software decoding).

[mixus]

can you add hevc multithread?

[nevcairiel]

can you add hevc multithread?

HEVC is already multithreaded.

[mixus]

Not Write HEVC.
I wrote this reason.

http://i.hizliresim.com/jV71jW.png

Sorry for my bad english :(

[LigH]

^ Apparently he only forgot to add this format in the tooltip text.

[nevcairiel]

I don't even remember there is such a list in the tooltip, I should probably just remove it, its quite out of date.

[Reign]

I have ran into a problem with the CUVID HW decoding for HEVC, while it has always worked for me a video I downloaded recently causes MPC-HC crash here is a dump I received. https://drdump.com/UploadedReport.aspx?DumpID=6648438 sample video: http://www.nyaa.se/?page=view&tid=779737&showcomments=52aa3f1#c538731

Win 7 x64 sp1
MPC-HC x64 1.7.10
LAV x64 0.67.0
NVidia GTX 970

[nevcairiel]

I have ran into a problem with the CUVID HW decoding for HEVC, while it has always worked for me a video I downloaded recently causes MPC-HC crash here is a dump I received. https://drdump.com/UploadedReport.aspx?DumpID=6648438 sample video: http://www.nyaa.se/?page=view&tid=779737&showcomments=52aa3f1#c538731

Win 7 x64 sp1
MPC-HC x64 1.7.10
LAV x64 0.67.0
NVidia GTX 970

This issue is already fixed in the next version.

[Leader]

Hi, nevcairiel!

I found a bug in "LAV Video Decoder".

Incorrect playback this file: copyright violation removed. in LAV Video Decoder (DXVA2 decoding and software decoding).

nevcairiel, I've updated the link to the torrent file, so you can download it without any problems.

Link: copyright violation removed

With regard to the problem: during playback of the file, there are frames missings and deviations, as well as video frames played unsmooth and intermittently.

[nevcairiel]

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

[DragonQ]

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.

http://f19.ifotki.info/thumb/7c92db627144a1abc49403726e4052a325358f237498156.png (http://i-fotki.info/19/7c92db627144a1abc49403726e4052a325358f237498156.png.html)
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]

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]

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]

Software Decoding is perfectly fine however.

Confirm!

[nevcairiel]

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]

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 (https://forums.geforce.com/default/topic/908792/artifacts-with-dxva-decoding/)

[hoborg]

Hello.
Intel (HD6200) also working just fine.

[NikosD]

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

similar clip (https://forums.geforce.com/default/topic/908792/artifacts-with-dxva-decoding/)

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]

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.

[NikosD]

Yes, maybe that particular way is incompatible with Nvidia's HW decoder.

[huhn]

it there any reason it should work with quicksync and CUIVD but not with DXVA?

[nevcairiel]

it there any reason it should work with quicksync and CUIVD but not with DXVA?

QuickSync is not NVIDIA, so there is that.

And it only works with CUVID on Windows 10 because that doesn't go through DXVA, on earlier Windows versions it goes through DXVA and shows the exact same result.
Its probably a driver issue and not even hardware, but who knows if they'll fix anything.

[huhn]

And it only works with CUVID on Windows 10 because that doesn't go through DXVA, on earlier Windows versions it goes through DXVA and shows the exact same result.

that make a lot more sense to me now.

[Alexey1975]

Here is the my assumption:

The fact that NVIDIA has some specific problems with DXVA is clear, but CUVID engine is not identical to the DXVA.
Here the experiment:
1. When it comes thru the CUVID tract - all just fine.
(pay attention to the log)
http://f19.ifotki.info/thumb/84af893261bff3040a475792875b35e525358f237554083.png (http://i-fotki.info/19/84af893261bff3040a475792875b35e525358f237554083.png.html)

2. When it comes thru the DXVA enviroment it cause a problems. And pay attention to the log now!
http://f19.ifotki.info/thumb/179d5306189d28964ee40e54163dbc6525358f237554105.png (http://i-fotki.info/19/179d5306189d28964ee40e54163dbc6525358f237554105.png.html)
http://f19.ifotki.info/thumb/be00410a8153352f56f99f1afdd7356825358f237554112.png (http://i-fotki.info/19/be00410a8153352f56f99f1afdd7356825358f237554112.png.html)

The fact that the video streams were processed by the graphics card is evidenced by its load levels. So we have not software but hardware decoding in all of the cases.

3. Now check the results of the latest LAV beta:
http://f19.ifotki.info/thumb/00d597fc27b9ad2aab79a4933bf2856525358f237554118.png (http://i-fotki.info/19/00d597fc27b9ad2aab79a4933bf2856525358f237554118.png.html)

At latest betas the CUVID mode calls or passes through the DXVA enviroment instructions and that begets the inconsistency.

[romulous]

Hi nev,

When the next stable version rolls around, will there be an installer available that includes the new MVC dll's that does not require an internet connection? So the dll's will be included in the installer rather than having them downloaded I mean.

Thanks,

romulous

[nevcairiel]

No, having them downloaded is the intended solution since they are quite big and most people probably won't install them.

[Manni]

I found a solution to switch bitstreaming on/off on the fly in LAV in order to resolve the problem of limited cross-upmixing with some AVRs after the DTS:X upgrade, so I thought I'd share it in case others experience the issue. I created a new thread to not clutter this one and make it easier to find the workaround.
Here is the link: http://forum.doom9.org/showthread.php?p=1756727#post1756727

[4h4h270]

When I using latest beta to play MVC 3D with madvr on framepacked 3D mode, after 1hr10min play I will get massive frame drop.
It happened by abnormal cpu use, I'm not sure if it's intel's dll or lavfilter's problem :(

[madshi]

When I using latest beta to play MVC 3D with madvr on framepacked 3D mode, after 1hr10min play I will get massive frame drop.
It happened by abnormal cpu use, I'm not sure if it's intel's dll or lavfilter's problem :(
Can you please check if maybe the process is running out of RAM or something? Are you using an x64 or x86 media player? Try x64, just as a test.

[4h4h270]

Can you please check if maybe the process is running out of RAM or something? Are you using an x64 or x86 media player? Try x64, just as a test.

:O I'll try x64, still using x86 because of reclock.

Thx madshi, I never notice the RAM problem, I tried x64 no more frame drop. :D

[scollaco]

I'm a relative newbie to all this and trying my best to learn.

I have a new Intel Skylake NUC (NUC6i5syk), Using MPC-BE x64, LAV x64 and MadVR (all latest nightlies)

My question is which decoder setting is the best for me? I usually play some 720p, mostly all 1080p and sometimes 4K 8 bit. I get dropped frames with 4K 10 bit (I know my Skylake doesn't support hardware accel with 10 bit).

So in general what would be my best choice to get the most efficiency?

What do I choose in LAV?

None
CUVID
Intel Quicksync
DXVA (Copy Back)
DXVA native

thanks for the help

[DragonQ]

DXVA Native should always be the most efficient. If DXVA Copy Back works that is probably a better choice since it's a bit more flexible.

[scollaco]

DXVA Native should always be the most efficient. If DXVA Copy Back works that is probably a better choice since it's a bit more flexible.

Got it. Both DXVA native and copy back work fine for me. So I guess it's up to me to choose one of them knowing DXVA copy back is more flexible with different setups.

So at least I know to ignore Intel Quicksync, CUVID and none.

[Patrik G]

this is probably a noob question but i have downloaded the latest LAV nightly build for use in MPC-HC
just to test some HDR demos with madvr

but when i start MPC-HC it still uses the build in lav filters
how do i activate the latests lav filters in mpc-hc?

Edit:
problem solved i think
just added the latest lav decoder to the external filters list.
now mpc-hc uses it

[LigH]

The other way would probably be to exchange the files in MPC-HC\LAVFilters, these are the "internal" copy which MPC-HC prefers over system-wide installed DirectShow filters if you don't disable internal filters for a specific format.

[Patrik G]

About HDR playback
is it more to include with the latest nightly builds for HDR metadata that is being sent to madvr or is it complete?
Are all HDR metadata being sent?
HDR peakbrightness and colorgamut (BT2020) are there already but what about gamma?

just watched Exodus and life of Pi HDR demos on a 8 year old KRP-500M plasma monitor with peakbrightness at 220cd/m2 and 93% of DCI P3 gamut
it looked amazing.
im going to compare the regular blu ray version of that movie later.

[nevcairiel]

Are all HDR metadata being sent?
HDR peakbrightness and colorgamut (BT2020) are there already but what about gamma?

The Gamma of HDR content is being defined by SMPTE ST 2084, and the required min/max luminance is supplied as metadata.

So yes, all required metadata is provided to madVR to render HDR content properly.

[Patrik G]

So yes, all required metadata is provided to madVR to render HDR content properly.

thats amazing!
thanks for the hard work it really pays off even on tvs with less peak brightness and no HDR support

so if you put it this way
if you have a tv with 500cd/m2 peakbrightness and 100% DCI P3 coverage but no natvie HDR support.
will this tv output the same HDR performance as a "new" tv with the same specs but with native HDR support?

it clearly is a big difference with the HDR version compared to the Blu Ray
much more details both near black and near white
better and more natural looking colors.

i took two photos here
one with the HDR version of Exodus and one from the regular Blu Ray
its not quite a fair comparsion because the crappy camera still crushes blacks.
http://privat.bahnhof.se/wb192876/500M%20HDR%20COMPARSION.jpg
you can see that the HDR version has more details and better colors.
colors with the wider colorgamut on the 500M with the regular blu ray just looks oversaturated and cartoon.

when watching these two versions its like comparing a Full frame DSLR camera to a crop sensor camera.
the image from the HDR version is much more lifelike.
just when you watcing photos taken with a full frame DSLR.

just waiting for more HDR content to be available :)

[nevcairiel]

thats amazing!
if you have a tv with 500cd/m2 peakbrightness and 100% DCI P3 coverage but no natvie HDR support.
will this tv output the same HDR performance as a "new" tv with the same specs but with native HDR support?


A HDR TV can of course show a much higher dynamic range, since the panels are designed for a much higher range of brightness.
How this will be usable from a HTPC is a question we won't be able to answer until we developers have access to such TVs however.