LAV Filters - DirectShow Media Splitter and Decoders

[LigH]

There are additional audio processors available (e.g. DeDynamic or TFM for DirectShow). LAV Filters may well be pure decoders.

[nevcairiel]

LAV Filters 0.70

General
- Official LAV Filters builds require a SSE2 capable CPU

LAV Splitter
- Fixed: Certain MP4/MOV files didn't play or seek correctly in recent versions of LAV Splitter
- Fixed: HEVC in MP4 without PTS timestamp is being signaled appropriately
- Fixed: Closing RTSP streams did not properly call the TEARDOWN function

LAV Video
- NEW: CUVID support for VP9 8/10-bit and HEVC 10/12-bit decoding
- NEW: DXVA2 support for VP9 10-bit decoding
- Changed: Simplified the internal dataflow to reduce overhead and improve performance
- Changed: Enabled P010 output to EVR on Windows 10 Creators Update
- Fixed: Y416 output was incorrect (required by madVR 0.91.8 and newer)
- Fixed: Parsing H.264 MVC SEI NALs could fail in some cases
- Fixed: CUVID decoding could deinterlace progressive streams under certain circumstances, degrading the quality

LAV Audio
- Fixed: LATM AAC streams with Program Config Elements (PCE) (common in DVB-T2 broadcast) played with audible distortions
- Fixed: Very short PCM audio streams didn't play properly


Download: Installer (both x86/x64) (https://files.1f0.de/lavf/LAVFilters-0.70.exe) -- Zips: 32-bit (https://files.1f0.de/lavf/LAVFilters-0.70.zip) & 64-bit (https://files.1f0.de/lavf/LAVFilters-0.70-x64.zip)

Its already been half a year again since the last release, so it was about time.

NVIDIA finally released the updated NVDEC SDK (formerly CUVID), which allowed adding support for new codecs and proper 10/12-bit decoding without too much trouble, for those people that still cling to NVDEC/CUVID decoding.
In addition to that, DXVA2 also supports VP9 10-bit decoding now - with the required hardware support of course.

Overall I spend some time cleaning and optimizing LAV Video, which should lead to a small performance increase across the board - it does depend on the video and decoding mode however, so the improvements vary.

Otherwise the same as every release, a bunch of fixes that didn't make the log, some in LAV and some inherited from FFmpeg.
As always, please do report regressions, preferably with a sample file to reproduce them.

[madshi]

Very nice, thank you!

Can you add some details for "Fixed: Parsing H.264 MVC SEI NALs could fail in some cases"? I'm asking just in case it might also be something I need to fix in my code somewhere.

[nevcairiel]

Can you add some details on "Fixed: Parsing H.264 MVC SEI NALs could fail in some cases"? I'm asking just in case it might also be something I need to fix in my code somewhere.

Doubtful. You don't parse any raw H.264 stuff anywhere, do you?

The problem was that I tried to parse the SEI without un-escaping it first, which would fail if the data contained a double zero byte (which is forbidden and therefor escaped). I don't know if any real world problems came from this (at worst the subtitle offsets might have been wrong), but it logged errors in some cases.

[manolito]

General
- Official LAV Filters builds require a SSE2 capable CPU

Could you please tell me which 0.69 nightly is the last version which works without SSE2? I'm too lazy to try them all... :scared:

Cheers
manolito

[madshi]

Doubtful. You don't parse any raw H.264 stuff anywhere, do you?

The problem was that I tried to parse the SEI without un-escaping it first, which would fail if the data contained a double zero byte (which is forbidden and therefor escaped). I don't know if any real world problems came from this (at worst the subtitle offsets might have been wrong), but it logged errors in some cases.
Thanks.

(Actually I do parse h264 in some situations in madVR. I'm doing that to extract video header information in case the video decoder doesn't properly report that to me. Not needed when using LAV Video Decoder, obviously.)

[sneaker_ger]

Could you please tell me which 0.69 nightly is the last version which works without SSE2? I'm too lazy to try them all... :scared:
Try LAVFilters-0.69.0-85.exe.

[nevcairiel]

Note that you can still make non-SSE2 builds if you choose to, it'll be slightly slower but it will work. Only the official builds will require it, the source itself does not.

[manolito]

I cannot build the binaries myself...
Any reliable source for "non-official" builds?

[Virtual_ManPL]

@ nevcairiel - Thank you very much for the new stable release! :thanks:

[mzso]

for those people that still cling to NVDEC/CUVID decoding.

I for one am not clinging to it, but I'm forced to use it since apparently that's the only way I can get decent deinterlacing. LAV's deinterlacer wouldn't work without HW accelerated decoding, madVR's apparently doesn't work at all.

[huhn]

because it doesn't work for does mean it doesn't work in general.

does it work with EVR? it is using the exact same deinterlancer.

[nussman]

I for one am not clinging to it, but I'm forced to use it since apparently that's the only way I can get decent deinterlacing. LAV's deinterlacer wouldn't work without HW accelerated decoding, madVR's apparently doesn't work at all.
LAV's deinterlacer = ?
GPU HW Deinterlacers work with software, dxva native and dxva copyback (and cuvid). With software or dxva it depends on the videorenderer, but with madVR and EVR / EVR Custom HW deinterlacing is just fine here (Win7, Win 8.1, Win10).

[nevcairiel]

His problems seem to come from his TV player application which somehow does a bad job of re-initing the directshow graph on channel changes, causing madVR to drop the deinterlacing. Could probably be fixed in madVR somehow, or perhaps in the player (or using a different one).

[mzso]

LAV's deinterlacer = ?
GPU HW Deinterlacers work with software, dxva native and dxva copyback (and cuvid). With software or dxva it depends on the videorenderer, but with madVR and EVR / EVR Custom HW deinterlacing is just fine here (Win7, Win 8.1, Win10).

In LAV I can only enable HW deinterlacing when I enabled HW acceleration.

because it doesn't work for does mean it doesn't work in general.

does it work with EVR? it is using the exact same deinterlancer.

It seems like deinterlacing is fine with EVR, when it works. Apparently ProgDVB crashes with LAV 0.70 and disabled HW acceleration.

His problems seem to come from his TV player application which somehow does a bad job of re-initing the directshow graph on channel changes, causing madVR to drop the deinterlacing. Could probably be fixed in madVR somehow, or perhaps in the player (or using a different one).

Sadly I can't find a better one. So far this seems to be the most decent. (Despite being buggy.)

[nussman]

You dont have to enable HW deinterlacing in LAV.
GPU/Hardware Deinterlacing setting is for cuvid/quicksync (?) only.

You can try another deinterlacing mode (aggressive or force) in LAV or another TV-Player (i.e. DVBViewer Pro).

P.S. I hope you are not using WinXP? :)

[mzso]

You dont have to enable HW deinterlacing in LAV.
GPU/Hardware Deinterlacing setting is for cuvid/quicksync (?) only.

You can try another deinterlacing mode (aggressive or force) in LAV or another TV-Player (i.e. DVBViewer Pro).

P.S. I hope you are not using WinXP? :)

I'm not sure what you're trying to say. (I took a look at DVBViewer, but I found the interface really cumbersome)

(I'm on 8.1)

[el Filou]

I'm not sure what you're trying to say. (I took a look at DVBViewer, but I found the interface really cumbersome)

(I'm on 8.1)
MediaPortal 1 supports madVR now, maybe try it?

I'll try the free version of ProgDVB when I have time, to see if I have the same problems as you.

[mzso]

MediaPortal 1 supports madVR now, maybe try it?

I'll try the free version of ProgDVB when I have time, to see if I have the same problems as you.
I believe I tried MediaPortal for something a while ago. But if memory serves it has a very cumbersome tv/remote oriented UI. (which is aggravated by the fact that I'm using a desktop pc to watch TV)

[manolito]

Try LAVFilters-0.69.0-85.exe.
Thanks... :thanks:

Yes, this is the last version which works without SSE2.

[egandt]

Any idea, it is a new setup using 0.70, and is working well, but I'm getting dual LAV splitters with what appear to be doing the same thing. When I look at the playback graph I see only one copy however.

Thanks,
ERIC

[nevcairiel]

Perhaps the player is using it to load external subtitles or an external audio file.

[mzso]

MediaPortal 1 supports madVR now, maybe try it?

I'll try the free version of ProgDVB when I have time, to see if I have the same problems as you.

Hi!

So, did you try it?

[el Filou]

Hi!

So, did you try it?
Yes, I've answered you with a screenshot in the madVR thread.
I can use GPU deinterlacing without any problem with LAV software decoding + madVR.

[huhn]

can you keep this to one thread please?

[nussman]

I think @mzso should start a new thread for his issue with all infos from LAV and madVR thread about it for supporters.

[mzso]

I think @mzso should start a new thread for his issue with all infos from LAV and madVR thread about it for supporters.

If I couldn't find a solution in the dedicated thread of the stuff I'm having troubles with I doubt there'd be any in a separate thread.

[nussman]

Do what ever you want, but hardware deinterlacing works just fine for most LAV/madVR users. So my guess is there must be something different on your system, but if you spread out the informations in different threads its harder to help you.

[mzso]

Do what ever you want, but hardware deinterlacing works just fine for most LAV/madVR users. So my guess is there must be something different on your system, but if you spread out the informations in different threads its harder to help you.

I didn't I asked here whether I could have different LAV settings for a specific app, after which the conversation trailed toward to be identical to the one in the madVR thread.

[chros]

@ nevcairiel - Thank you very much for the new stable release! :thanks:
Me too :)

[VictorLS]

nevcairiel

LAV Filters 0.70
LAV Video
- NEW: CUVID support for VP9 8/10-bit and HEVC 10/12-bit decoding
- Fixed: CUVID decoding could deinterlace progressive streams under certain circumstances, degrading the quality

That's great (Russian says in such cases "better later than never") - with my GTX750 on GM206 work both NVIDIA CUVID h265 10bit HW decoding and playing all artifacted files without artifacts by switching off Enable CUVID DXVA Processing in Win7x64.
But it's a pity in WinXP h265 10bit HW decoding still not work as with previous versions of LAV Video Decoder - except is 0.68.1.35 modified by Aleksoid1978 which works pretty well in WinXP - correct it in future releases, please.

[nevcairiel]

If its broken on XP, it'll likely remain broken.

[VictorLS]

If its broken on XP, it'll likely remain broken.
It's a pity 2.
Where you lost your Perfectionism?

[QBhd]

Are you kidding? XP is beyond old! Why would you think any developer would keep supporting this? Get a grip. Besides, XP is horrible for media playback.

QB

[lvqcl]

There are 2 ways to make LAVFilters more perfect:
1) fix all problems with WinXP (apparently won't happen)
2) make them require Vista+

(so VictorLS should be happy that nevcairiel isn't perfectionist ;) )

[VictorLS]

lvqcl
Logically you're quite right, but I like first variant ;)

XP is beyond old!
But works almost perfect, incl. while playing 4K h265 10bit with hardware acceleration with LAV Video Decoder 0.68.1.35 modified by Aleksoid1978.
Why would you think any developer would keep supporting this?
Aleksoid1978 even gave diff-file. Why just implement it in modern version of LAV Video Decoder with some updates to work in XP correctly?
Besides, XP is horrible for media playback.
You're right - if playing more then one videostream, sometimes WinXP lags, but I usually plays one videostream simultaneously )
And in one videostream in KMPlayer or donateware SAT-program SmartDVB it shows all ~20 4K h265 8-10bit SAT channels I can receive quite well without any stuttering (my monitor supports 50Hz input frequency natively) - in Win7x64 I see some stutter sometimes.
PS. I saw Smurfs2 4K h265 10bit HDR in WinXP with KMPlayer and MadVR with HDR->SDR conversion setting without any stutter too (my monitor supports 2*23,976=47,952Hz input frequency natively too).

[nevcairiel]

As I've mentioned many times in the past - before I'll spend time trying to fix something on XP (nevermind something that requires hardware decoding, and thus XP on actual hardware, not even a VM), I'll just disable XP support entirely. So if you still use XP, I would be very careful with what you ask for. :)

[VictorLS]

As I've mentioned many times in the past - before I'll spend time trying to fix something on XP (nevermind something that requires hardware decoding, and thus XP on actual hardware, not even a VM)
As usual first of all thanks for reply.
I know many people (and from various forums too) using LAV in WinXP but they don't watch 4K h265 10bit because they haven't GM206-based videocard, so they are satisfied, but I require maximum possible.
I want mention, Aleksoid1978 is MPC-BE developer and MPC-BE not work in WinXP many times ago, so people I know have to use MPC-HC instead, but Aleksoid1978 spend some (very few) time to modify LAV Video Decoder work perfect in WinXP.
So if you still use XP
Of course still - as minimum while my computer supports it.
I'll just disable XP support entirely
OK. I'll just use modified 0.68.1.35 as do it now :)
It's a pity I can't use LAV Splitter and Audio Decoder separately LAV Video Decoder. When was MpegSplitter.ax, MpaDecFilter.ax and MPCVideoDec.ax it was easy possible.

PS. If you want I can ask Aleksoid1978 (or you can ask him by yourself) what the secret of h265 10bit support under WinXP implementing. I hope he'll answer to me (or you).

[Groucho2004]

I'll just use modified 0.68.1.35 as do it now :)Got a link for that?

[P.J]

Why does the edge of saturated colors look bad in prores format?
I have this problem only with prores videos :confused:

http://screenshotcomparison.com/comparison/213956

[sneaker_ger]

It's probably a different output format than your other videos (10 bit 4:2:2?) and your renderer/GPU driver/OS messes up. Try madvr. (Or set LAV to only output RGB/4:4:4. I assume it has a better conversion.) It's a common artifact of low quality chroma upsampling.

[nevcairiel]

That certainly sounds like a possibility. 4:2:2 -> RGB upsampling appears to be of weird quality on some GPUs, so using madVR or LAVs upsampling (which might not be very fast on high resolutions, though, maybe I should make an AVX variant of it) could help.

[VictorLS]

Got a link for that?
It was here http://forum.doom9.org/showthread.php?p=1786045#post1786045
New link to download LAVFilters-0.68.1-35.exe (10MB) https://yadi.sk/d/ylhX_1Es3KapC6

[P.J]

It's probably a different output format than your other videos (10 bit 4:2:2?) and your renderer/GPU driver/OS messes up. Try madvr. (Or set LAV to only output RGB/4:4:4. I assume it has a better conversion.) It's a common artifact of low quality chroma upsampling.

Yes, prores is (8 bit) 4:2:2 and avchd is 8 bit 4:2:0
I'm using Win10 GTX960 EVR-CR


That certainly sounds like a possibility. 4:2:2 -> RGB upsampling appears to be of weird quality on some GPUs, so using madVR or LAVs upsampling (which might not be very fast on high resolutions, though, maybe I should make an AVX variant of it) could help.

LAVs upsampling = set LAV to only output RGB/4:4:4 ?

[sneaker_ger]

Correct.

[Groucho2004]

It was here http://forum.doom9.org/showthread.php?p=1786045#post1786045
New link to download LAVFilters-0.68.1-35.exe (10MB) https://yadi.sk/d/ylhX_1Es3KapC6Thanks.

[nevcairiel]

LAVs upsampling = set LAV to only output RGB/4:4:4 ?

Or at least disable 4:2:2 modes, that'll force 4:2:2 to 4:4:4/RGB but keep 4:2:0 as-is.

[P.J]

Or at least disable 4:2:2 modes, that'll force 4:2:2 to 4:4:4/RGB but keep 4:2:0 as-is.

Yea, I actually did that and now it's much better :thanks:
http://screenshotcomparison.com/comparison/214003

I'll test with Intel HD4600 too, not sure what to blame :D

[e-t172]

Of course still - as minimum while my computer supports it.

Running a decades-old OS which has stopped getting security updates long ago, and therefore constitutes a significant threat for yourself and others, is not a "matter of course". If anything, nev would be making the world a better place by disabling XP support, as it would encourage people like you to move to a more secure OS.

[manolito]

... as it would encourage people like you to move to a more secure OS.

A more secure OS like Win10 for example? :devil:
That's a good joke...
(You do not read any security news, do you? "Security" and "Microsoft", these two terms are mutually exclusive.)