LAV Filters - DirectShow Media Splitter and Decoders

[nevcairiel]

If its broken with CUVID, then it is the NVIDIA Hybrid decoder just not liking this stream. Nothing can be done on my side.
You can report it to NVIDIA and hope they improve it.

[Half-Light Agent]

even with CUVID HEVC support the GPU would be to slow.
i'm not even sure if HEVC hybrid decoding with CUVID/DXVA is a lot faster than simple CPU decoding using GPU slower than nvidia 460.

and about coreAVC. DXVA should be the same. (and it was the same on my ION)
if coreAVC really uses CUDA and that not over CUVID. DXVA should be a lot faster.

I have never had reason to consider how CoreAVC decodes x264 once it was installed, but the reduction of CPU activity is of such a degree that I'm fairly confident it offloads AVC to CUDA as it indicates. 1080p AVC plays back comfortably on an Intel Atom 230.

If there is some way to do the same for HEVC, that would extend the horizon for an entire generation of hardware. I doubt either the h265 group or NVIDIA are interested in doing much themselves along these lines, as there the new standard provides a nice opportunity to render a lot of hardware in need of replacement.

[nevcairiel]

There is NO CUDA decoder for H264/AVC. It uses a dedicated decoding chip in the GPU, it does NOT use CUDA. If anyone claims it uses CUDA, it is lying and misleading users.
The GPU needs to support the codec you want to decode, your ancient GPU does not support it, so you don't get HEVC decoding.

[petran79]

A DWORD value with the name of the exe as key (without path), and the value "1".

thanks.

[e-t172]

There is NO CUDA decoder for H264/AVC.

How can you be so sure? Theoretically, I would assume it's possible to write a video decoder in CUDA or OpenCL itself (as in, actually implement a decoder using the CUDA/OpenCL language), or at least offload parts of it. It would probably be very hard, and wouldn't be as efficient as direct GPU support, but it guess it could still be faster than the CPU.

[captainadamo]

How can you be so sure? Theoretically, I would assume it's possible to write a video decoder in CUDA or OpenCL itself (as in, actually implement a decoder using the CUDA/OpenCL language), or at least offload parts of it. It would probably be very hard, and wouldn't be as efficient as direct GPU support, but it guess it could still be faster than the CPU.

I'm pretty sure nev's comment was in the context of CoreAVC.

[Half-Light Agent]

There is NO CUDA decoder for H264/AVC. It uses a dedicated decoding chip in the GPU, it does NOT use CUDA. If anyone claims it uses CUDA, it is lying and misleading users.
The GPU needs to support the codec you want to decode, your ancient GPU does not support it, so you don't get HEVC decoding.

I have seen a screenshot of a GTX-660Ti decoding HEVC through CUVID, although apparently it oughtn't.

http://i.imgur.com/YWFOSzS.png

Might this be an exploitable fluke?

EDIT: My mistake. In March, NVIDIA officially added HEVC decoding support to a number of VDPAU cards (http://www.nvidia.com/download/driverResults.aspx/83515/en-us), including the GTX-660Ti.

[D2MAC]

Play fine using DXVA Native + GTX 960.

Play fine DXVA NATIVE + GTX 960, only HEVC low profile.
(Example : Elecard 4K video about Russian Beatles - 8 bits)

But with HEVC 10 bits UHD 4K from ASTRA/EUTELSAT demo, it doesn't work at all -> no DXVA2 enabled.
(only ok with latest MPC-BE)

[huhn]

I have never had reason to consider how CoreAVC decodes x264 once it was installed, but the reduction of CPU activity is of such a degree that I'm fairly confident it offloads AVC to CUDA as it indicates. 1080p AVC plays back comfortably on an Intel Atom 230.

would be the same with DXVA/CUVID from lavfilter but for free of cause.

CUVID was very important before DXVA was a "thing". since DXVA it is kind of superseded.
at the moment CUVID just wastes power by forcing the GPU in highest powerstate.

[P.J]

Play fine DXVA NATIVE + GTX 960, only HEVC low profile.
(Example : Elecard 4K video about Russian Beatles - 8 bits)

But with HEVC 10 bits UHD 4K from ASTRA/EUTELSAT demo, it doesn't work at all -> no DXVA2 enabled.
(only ok with latest MPC-BE)

Use DXVA2 copy-back.

[D2MAC]

Use DXVA2 copy-back.

Hi,

Thanks

DXVA2 copy-back + GTX960: UHD 4K 10 BITS ASTRA/EUTELSAT

it's work only with latest LAV 0.64.52 build (16/04/2015)
(ok with enhanced video renderer or madvr)
(files froms nightly MPC-HC)

Still not ok with DXVA2 NAtive, but it's better. (20% CPU)

[MeteorRain]

If its broken with CUVID, then it is the NVIDIA Hybrid decoder just not liking this stream. Nothing can be done on my side.
You can report it to NVIDIA and hope they improve it.

Gotcha.:thanks:

[pirlouy]

I've discovered madVR has now a 64 bits. What about dts-hd decoder ? Do you know if there's something being worked to have a 64 bits dts-hd decoder ?
I remember once reading there were a "beginning" on ffmpeg project.

[huhn]

get the lavfilter nightly.

[nevcairiel]

Still not ok with DXVA2 NAtive, but it's better. (20% CPU)

DXVA2 Native does not support 10-bit, and thats very unlikely to change.

[pirlouy]

I searched through the commits and I finally ended on dcadec (https://github.com/foo86/dcadec).

Is it working well for classic DTS-HD from Blu-Ray ? If yes, that's great, and I'll wait for final LAV builds to test this 64 bits.

[ryrynz]

Is it working well for classic DTS-HD from Blu-Ray ? If yes, that's great, and I'll wait for final LAV builds to test this 64 bits.

Don't get why you don't just install it and test it for yourself... But yes it works fine.

Why wait for final? Nev's master builds are as stable as anything final.

[Half-Light Agent]

would be the same with DXVA/CUVID from lavfilter but for free of cause.

CUVID was very important before DXVA was a "thing". since DXVA it is kind of superseded.
at the moment CUVID just wastes power by forcing the GPU in highest powerstate.

Thanks for your thoughts on the matter,

Half-Light Agent

[ocyl]

EDIT: My mistake. In March, NVIDIA officially added HEVC decoding support to a number of VDPAU cards (http://www.nvidia.com/download/driverResults.aspx/83515/en-us), including the GTX-660Ti.
No, it did not. Currently, the only nVidia GPU that has VDPAU feature set F support in hardware is GM206, which is used in GeForce GTX 960.

http://http.download.nvidia.com/XFree86/Linux-x86_64/349.16/README/supportedchips.html

[betaking]

last GIt can not complie X64 build Lav!
http://oi58.tinypic.com/xkuidd.jpg

[Magik Mark]

Is LAV dithering has similar algorithm as provided in madVR?

[Asmodian]

Is LAV dithering has similar algorithm as provided in madVR?

No, madVR uses higher quality dithering. LAV's dithering will never be used when rendering with madVR and using LAV's default settings.

[nevcairiel]

LAV Filters 0.65

LAV Splitter
- NEW: Support for MKV subtitle Cues to show subtitles immediately after a seek
- NEW: Attachments and embedded cover art images are exported through the IDSMResourceBag interface
- Fixed: Improved demuxing of HEVC in MPEG-TS and increased the reliability of the SPS/PPS/VPS extraction
- Fixed: Demuxing Blu-rays/MPEG-TS where the first stream was not a video stream could result in broken timestamps
- Fixed: Seeking in MKVs which are currently being written is more reliable

LAV Video
- Fixed: Improved HEVC DXVA2 decoding on a few samples
- Fixed: Playback of VFR MPEG-4 in AVI had wrong timestamps in 0.64
- Fixed: Improved handling of DVD subtitles without timestamps

LAV Audio:
- NEW: Native DTS-HD decoding using libdcadec
- Changed: 5.1 audio prefers the speaker mask with side channels, to match recent specifications

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

DTS-HD decoding support through libdcadec

LAV Audio now includes libdcadec (https://github.com/foo86/dcadec), a full-featured DTS-HD decoder.
All known DTS-HD MA and DTS-HD HRA samples are supported and decoded perfectly lossless, up to 7.1, 192kHz, 24-bit (with a possible exception in a few weird samples). In addition, it also supports a long list of core extensions, including XCH (for 6.1 DTS ES streams), and X96 (for DTS 96/24).

The only unsupported DTS format that I know of is DTS Express, which is used for interactive commentary tracks on Blu-rays.

If the ArcSoft decoder is present, it will continue to be used for the time being, but in the long run I may even remove it.

If you find anything that doesn't seem to behave properly with the new DTS decoder, please do report and I'll work with the libdcadec author to see what is going on!

------

I wanted to get some more features done for this release, but time was short, and it felt like this was worth releasing anyway, so, have fun with it!

[kalston]

Nice! Btw in the original post next to the dl link for the installer it still says 0.64 :D (even though the link does point to 0.65)

[ddjmagic]

Thanks for the new release! :)

[Bozotheclown]

in audio properties -> formats -> in libdcadec section should be add (DTS, DTS-HD, DTS-HR, etc.) like in ac3?
I mean common used codec name

[rd1979]

This is a big release to me, even if it doesn't have everything you wanted in it, a lot of longstanding little niggling issues I had are addressed here.
Thanks nev!

[khanmein]

when i choose mpc-hc audio renderer @ sound device choose speaker (realtek ALC892) the sound is good but whenever i adjust the seekbar got the distortion & shuttering sound from any videos.

[nevcairiel]

MPC-HC Audio Renderer is not recommended to be used at this point, but thats more of a topic for the MPC-HC thread.

[khanmein]

MPC-HC Audio Renderer is not recommended to be used at this point, but thats more of a topic for the MPC-HC thread.

sorry bro, noted.

[Ver Greeneyes]

I noticed that the changelog and download links on http://1f0.de/downloads/ are out-of-date, showing the changes for and linking to 0.61.2! This caused a Dutch news website I frequent to report the wrong changes (I left a comment with the correct changelog, also linking to this thread).

[nevcairiel]

I removed the page and linked to GitHub instead. Don't feel like updating things in way too many places anymore.

[iSunrise]

...If the ArcSoft decoder is present, it will continue to be used for the time being, but in the long run I may even remove it.
Ugh, didn't know that, I thought that the nightly builds already defaulted to the new decoder. Thanks for pointing that out, I must have missed that probably.

Did anyone do tests whether there is a general quality improvement due to the exceptional good documented and implemented code from foo86 compared to ArcSoft? Seems it is time to do a spectral analysis, when I have some time.

[nevcairiel]

Both decoders are lossless, there is no quality difference.

[XinHong]

Hi nevcairiel,

With this new release DXVA (native and CopyBack) does not work in DVBViewer (5.3.2, DVBSource 3.8.1.0), but it's working with the same recorded stream played in MPC-HC x86.
I tried several old releases and the last working one is 0.64.0-52, since 0.64.0-54 it does not work.

I can upload a sample if you need.

[nevcairiel]

This will be fixed in an upcoming build. I do however urge the developers of TS source filters to scan the H264 stream for SPS/PPS and export that in the media type, so that decoders know right away what kind of video they are to expect, and these problems can be avoided entirely.

[XinHong]

OK, thanks for the advise and the fix, I will post it in their forum.

[James Freeman]

I can't force LAV Splitter on MPC-HC, it seems to always use the internal one (yes, prefer is selected).
Any idea?

[Qaq]

Disable internal one(s).

[Ver Greeneyes]

I removed the page and linked to GitHub instead. Don't feel like updating things in way too many places anymore.Thanks, that's fine - it clears up the confusion in any case :)

[stax76]

Can anyone play this with LAV Filters? Plays fine with MPC-BE.

http://1drv.ms/1bpjp7k

ID : 1
Format_Profile : Main 10@L5@Main
Codec/String : HEVC
Duration/String1 : 10s 43ms
BitRate/String : 1 610 Kbps
Width/String : 3 840 pixels
Height/String : 2 160 pixels
PixelAspectRatio : 1.000
DisplayAspectRatio/String : 16:9
FrameRate/String : 29.970 fps
FrameCount : 301
Resolution/String : 10 bits
StreamSize/String : 1.93 MiB (100%)
Title : Video
Encoded_Library : x265 - 1.6+174-4cccf22b00ee:[Windows][GCC 4.8.2][64 bit] 16bpp
Encoded_Date : UTC 2015-04-24 18:20:28

[sneaker_ger]

No problem at all. (Software decoding)

[stax76]

Thanks for testing, problem was normal EVR, custom works (I use a self coded player using EVR), is this a LAV Filters or a EVR problem? I'm on Win 7 with GTX 960.

[SeeMoreDigital]

Can anyone play this with LAV Filters? Plays fine with MPC-BE.
Yup... It plays okay (Win10 64-bit):)

[NikosD]

Thanks for testing, problem was normal EVR, custom works (I use a self coded player using EVR), is this a LAV Filters or a EVR problem? I'm on Win 7 with GTX 960.

What happens if you disable P010/P016 output ?

Does it work ?

[stax76]

@NikosD

It plays then, I didn't notice these options, thanks.

@SeeMoreDigital

Please verify that normal (non custom) EVR on Windows 10 supports 10-Bit.

[huhn]

@NikosD

It plays then, I didn't notice these options, thanks.

@SeeMoreDigital

Please verify that normal (non custom) EVR on Windows 10 supports 10-Bit.

i forced lavfilter to output p010 and MPC-HC simply crashes when i use normal EVR on windows 10. without forcing p010 NV12 is used.
maybe EVR for MF can do this. but currently you need madVR for 10 bit input.

outputting 10 bit is a hole different story...

[stax76]

Thanks for the test, for now I just disable P010/P016.

[NikosD]

I have reported in Intel forums the P010/P016 output issues as a bug of Intel drivers and not bug of LAV filters.

Nvidia supposedly has fixed that bug in their drivers and can work with output P010/P016.

But after Stax76's post using Win 7 and Nvidia 960 there seems to be a problem.

I have to ask again:
What is exactly the problem with Intel and Nvidia drivers regarding output of P010/P016 with LAV Video ?

Intel is still investigating the issue but has already replied in public that probably is a LAV filters issue, not their drivers - but it's still under investigation.

[nevcairiel]

Its not a LAV Filters issue. EVR is just incapable of accepting P010 or P016, but somehow Intel and NVIDIA managed to enable that in EVR, and then you get no image, because EVR just fails at it.
Although NVIDIA fixed that in a newer driver again last I checked.