LAV Filters - DirectShow Media Splitter and Decoders

[nevcairiel]

LAV Filters 0.81

LAV Splitter
- NEW: Support for APV (Advanced Professional Video) video streams
- Fixed: VVC in MP4 without CTTS did not play properly
- Fixed: AV1 streams with invalid metadata did not get handled correctly

LAV Video
- NEW: Support for decoding APV (Advanced Professional Video)
- Changed: Re-designed pixel format mapping to be based on a heuristic rather then hard-coded, improving support for rarely-used formats
- Fixed: Deinterlacing of 4:2:2 videos was broken in 0.80

LAV Audio
- Fixed: Bitstreaming TrueHD from Blu-rays with seamless branching could result in out-of-sync audio, or a noticeable gap

Download: Installer (both x86/x64) -- Zips: 32-bit & 64-bit

Finally getting another long-standing TrueHD bitstreaming issue resolved. Otherwise the usual, FFmpeg updates and tackling anything that was immediately actionable and reported.

As always, please report issues, especially regressions, in as much detail as possible, and with a sample file.

[StainlessS]

Thankyou kind sir.

[clsid]

Some crash fixes:
https://github.com/clsid2/LAVFilters...519a249104d25f
https://github.com/clsid2/LAVFilters...d38b0c42f82818
https://github.com/clsid2/LAVFilters...95069d86e9e9ca
These can happen when accessing tray icon during loading.

And in libavutil\tx.c
https://drdump.com/Problem.aspx?ProblemID=1016430
Disabling those blocks under CONFIG_SMALL‎ fixes it. Seems like unnecessary debug/trace code for release builds.

[manolito]

Hi clsid,

interesting bug report, but frankly as a non-dev I do not really know what to do with it...

I am unable to compile my own version of LAV Filters, so I probably need to wait for nevcairiel to publish a fixed version. But anyways, thanks a lot for your findings...


Cheers
manolito

[manolito]

@clsid

Sorry for my ignorance about Github...
On the first page of this thread I found a link to "nightly test version", and the last commit is this one:
LAVFilters-0.81.0-3.exe

Am I correct that this is your commit? Anyways, I installed it, and all my taskbar problems (disappearing icons) were gone. I would never have guessed that, because I thought that as long as LAV Filters is not used by some software that it would not affect the Taskbar. Now I know better, and this commit made my life a lot easier.


A big Thank You

Cheers
manolito

[clsid]

No whatever problem you had is unrelated to LAV Filters.

[clsid]

@nevcairiel
DVD hardware decoding is broken.
https://drdump.com/Problem.aspx?ProblemID=1011044

Time to finally remove this option? It isn't enabled by default. Any hardware from the past 15 years can decode DVD resolution video without breaking a sweat.
Maybe also ditch quicksync as well.

[Sunspark]

Quicksync has adaptive hardware decoding of interlaced video.

If the code paths aren't broken why remove it? People say it is old, but it seems to work fine.

[Klaus1189]

What is "adaptive hardware decoding". Do you mean deinterlacer or indeed decoding?

[Sunspark]

Both.. it would be used with stuff like television broadcast mostly I imagine, perhaps DVD as well. But, it's not an inverse telecine so for DVD I haven't been using it. I did test the functionality though with a TV clip, and it does deinterlace using hardware (which is awesome when one considers AMD for example pretty much has completely broken deinterlacing functionality).

I use quicksync to this day because I always felt there was something "different" about how colour or motion looked with dxva2-cb. I also use overlay output since I have it. I was told that it's not very likely there's a difference but I am unable to capture it in a screenshot. I just remember a long time ago there was a pipeline graph that shows quicksync processes colour at a different stage of the pipeline than dxva2-cb, so it's not impossible that there is a subtle difference.

I looked it up, quicksync talks directly to the intel video firmware while dxva2 goes through the windows driver stack. I also observe that Intel has a new SDK (OneVPL) which continues to use quicksync and ffmpeg is supporting both the old and new.. so..

I get simplicity, but the decoder isn't something like an old forked version of ffmpeg 2.0. It's just the interaction with the firmware as I understand it.

[clsid]

The Intel driver applies some processing filters when using DXVA2. You can disable that in driver settings.

[clsid]

Got a bug report where a Matroska file contained more than 64 tracks.

So I tried increasing MAX_TRACKS to 80. But things got unstable and freezes. Even got a process stuck and unable to kill. Are more changes required?

I also noticed that in FFmpeg Matroska encoder, MAX_TRACKS is set to 126.

[nevcairiel]

Matroska files in LAV Splitter are limited to 64 tracks. Changing that would require quite some work.

[arapaz]

Hi,

I have a 3d video in a .mkv with a full side-by-side image (3840 x 1980)
The mkv has flags for multi view count and layout.
When played with MPC-BE/LAV/MadVR (3d set to auto), the output is not framepacked sent to the TV, it is the original image.

Is it possible that LAV split the image in 2 views and send that to MadVR as 3d ?

Thnaks

[josey_wells]

First, let me say that LAV Filters is a fantastic product, and I have been utilizing it for more than a decade.

With my current configuration of Pot Player, MadVR, LAV Filters, and HDMI receiver, any version of LAV filters above V0.80.0-7 Beta with audio bitstreaming enabled hangs on startup. If bitstreaming is disabled then no hang occurs.

To rule out all other causes, I have used other players such as MPC-BE & MPC-HC, other renderers such as EVR, and other HDMI receivers.

It would be appreciated if this could be looked at.

[Sunspark]

I was playing again with decoding methods the other night. I've always maintained that there is a subtle visual difference besides the native one which we know has issues.

AI says that I am not imagining things, that there actually is a difference with quicksync decoding with older Intel hardware due to this and that reason. Also goes on to say that because of fixed-function, etc. there can also be very subtle differences between software decoding and dxva2-copyback.

Came across this 2011 article today, it's not about LAV, but it does discuss software and hardware decoding so it might be of interest for some. https://www.tomshardware.com/reviews...sync,2839.html

[nevcairiel]

The truth of the matter is that there is one correct way of decoding any codec newer then MPEG-2 (MPEG-2 still had some inaccuracies in its IDCT that doesn't make it bitexact), any other methods are factually wrong.

- DXVA2-CB (and D3D11-CB) has been proven to be identical to software decode on any semi-recent hardware, so both of those are "perfect" as software decode is tested against the reference.
- DXVA2-Native has some issues not with decode, but with the way renderers access the image - its not designed to get a perfect version of the image for further processing, instead its really designed to shove it into DXVA2 Video Processing, which puts you at the mercy of the driver/hardware.
- D3D11 Native does not have this issue, and gives you access to the perfect pixel data, if thats used correctly

If any of those above are not true, then the driver does some undue processing, or the decoder is not up to the specification. Of course any hardware in history may have had issues, but video hardware from 15 years ago as in that article is practically unusable by now. Very old Intel stuff was indeed a bit weird with decode, but thats been over with for 10 years or so.

[nevcairiel]

Originally Posted by josey_wells

First, let me say that LAV Filters is a fantastic product, and I have been utilizing it for more than a decade.

With my current configuration of Pot Player, MadVR, LAV Filters, and HDMI receiver, any version of LAV filters above V0.80.0-7 Beta with audio bitstreaming enabled hangs on startup. If bitstreaming is disabled then no hang occurs.

To rule out all other causes, I have used other players such as MPC-BE & MPC-HC, other renderers such as EVR, and other HDMI receivers.

It would be appreciated if this could be looked at.

You'll have to elaborate a bit more. Others seemingly are not reporting any issues, so it must be something specific for your use.

Does this happen with all files, any particular ones? Are you bitstreaming all codecs? Did you try different audio renderers?

And can you confirm that issue did indeed start with 0.80.0-9? (versions are available at https://files.1f0.de/lavf/nightly/)