LAV Filters - DirectShow Media Splitter and Decoders

[LigH]

The video decoder unit on Nvidia GPUs is called PureVideo (https://en.wikipedia.org/wiki/Nvidia_PureVideo) (and the encoder unit is NVENC (https://en.wikipedia.org/wiki/Nvidia_NVENC)).

A video decoder software using the PureVideo SIP block will only support its provided features according to the feature set of its generation. Feature Set F should be the first supporting HEVC Main10 profiles; Feature Set G cards even support Main12 profile.

[CruNcher]

Or Internally just VPX (where X is the Generation) and it includes both Encoder/Decoder as most probably it stands for Video Processor X.

And Encoding started as NVCUVENC which is still working up to date before everything was moved to the Hardware and recaled NVENC

We are at Feature Set H

8th Generation by now

Added support for VDPAU Feature Set H to the NVIDIA VDPAU driver. GPUs with VDPAU Feature Set H are capable of hardware-accelerated decoding of 8192x8192 (8k) H.265/HEVC video streams.

either that or higher bitrate or Mulitply streams unless you reach the Maximum Decoding Capacity and Encoding/Capturing has some Software Driver Locks on the utilization side for different market usage ;)

Though it's pretty uknown if the 1050 (GP107) brings anything new yet to VPX that's not externally made public so officially its feature set H ;)


Nvidias Hybrid H.265 Decoder inside GM204 is roughly as performant as 4 intel Sandy Bridge cores on OpenHEVC alone at decent 4K Streaming bitrates, with some Decoding Performance issues that most probably never really got considered of being optimized any further it could certainly do better as it does by now ;)

[NikosD]

Using LAV 0.68.1.

Any idea why it keeps defaulting to avcodec? I have a GTX 1070 which should be able to decode this with ease, since it supports 4k@60 10b decoding.

Try again using DXVA2 instead of CUVID.

I can't play 10-bit H.265 on my system, but I thought that H.265 was handled by a separate chip on Pascal cards, not CUVID cores.

Try again using DXVA2 instead of CUVID.

[nevcairiel]

Indeed, just don't use CUVID. It doesn't support proper 10-bit decoding (and I do not plan to offer broken 10-bit decoding like some of these XP users here want).
DXVA2 is generally superior, it offers full bit-exact 10-bit decoding and various other features that CUVID couldn't begin to offer (like proper HDR metadata extraction, and more).

[trandoanhung1991]

Indeed, just don't use CUVID. It doesn't support proper 10-bit decoding (and I do not plan to offer broken 10-bit decoding like some of these XP users here want).
DXVA2 is generally superior, it offers full bit-exact 10-bit decoding and various other features that CUVID couldn't begin to offer (like proper HDR metadata extraction, and more).

Is the broken 10-bit decoding due to Hybrid decode? Pascal seem to offer full HW decoding of 10 and 12 bit streams.

[nevcairiel]

The CUVID interface just doesn't offer full access to 10-bit images, its a limitation from the API NVIDIA makes available for CUVID.

[VictorLS]

nevcairiel
Many thanks for reply.
It is a pity but I have to use Win7x64 from now more often (
PS. I have 8bit monitor and NVIDIA CUVID with h265 10bit hardware decoding by "dither it down to 8bit to return as NV12" like in Linux will be quite enough for me but ... thanks once more.
PPS. What about add possibility check/uncheck Use HQ DXVA Processing in LAV Video Decoder like in LAV CUVID Decoder with possibility automatic switch CUVID for h264 and DXVA2 for h265 while DXVA2 will play files such DXVA_NVidia_bug.ts and 2016-09-20 21-15-33.ts by new videocards without artifacts?
It was one of the important thing why I used WinXP - I never saw artifacts like in Win7x64 when watch SAT programs. If all SAT h265 is 8bit I use XP now with LAV Video Decoder NVIDIA CUVID )

[trandoanhung1991]

The CUVID interface just doesn't offer full access to 10-bit images, its a limitation from the API NVIDIA makes available for CUVID.

CUVID offers decoders for H264, HEVC, H263, MJPEG, mpeg1/2/4, vp8/9, vc1. Codec support varies by hardware. The full set of codecs being available only on Pascal hardware, which adds VP9 and 10 bit support.

While decoding 10 bit video is supported, CUVID is only able to output 8 bit video, so the additional 2 bits are lost in the process.

https://trac.ffmpeg.org/wiki/HWAccelIntro

Pretty conclusive. Maybe put this as part of the FAQ?

[kral2008]

Indeed, just don't use CUVID. It doesn't support proper 10-bit decoding (and I do not plan to offer broken 10-bit decoding like some of these XP users here want).
DXVA2 is generally superior, it offers full bit-exact 10-bit decoding and various other features that CUVID couldn't begin to offer (like proper HDR metadata extraction, and more).

But, kindly, if you improve the LAV CUVID compatibility, people haveing older graphic cards can watch UHD channels, I think most of them only want to watch just 4K HEVC and they don't attention to whether it is 8bit, 10bit, Dolby vision or HDR.

[LigH]

How do you mean that?

If CUVID does not support decoding 10 bit precision, LAV can't make CUVID support it. Only Nvidia could (if it is at all technically possible).

[nevcairiel]

But, kindly, if you improve the LAV CUVID compatibility, people haveing older graphic cards can watch UHD channels, I think most of them only want to watch just 4K HEVC and they don't attention to whether it is 8bit, 10bit, Dolby vision or HDR.

CUVID does not offer anything that DXVA2 does not also offer. I will not implement broken decoding modes, ever.

[kral2008]

How do you mean that?

If CUVID does not support decoding 10 bit precision, LAV can't make CUVID support it. Only Nvidia could (if it is at all technically possible).

While decoding 10 bit video is supported, CUVID is only able to output 8 bit video, so the additional 2 bits are lost in the process.
https://trac.ffmpeg.org/wiki/HWAccelIntro

CUVID does not offer anything that DXVA2 does not also offer. I will not implement broken decoding modes, ever.
I know it too,
as I said before, it is just a demand by the users of old cards to watch 10bit HEVC, they don't care about losing 2 bits in output picture (according to the link given above). Maybe they don't want to spent money on a new card.
But you have absolute discretion to choose what you want to do.

[captaiŋadamo]

as I said before, it is just a demand by the users of old cards to watch 10bit HEVC, they don't care about losing 2 bits in output picture (according to the link given above). Maybe they don't want to spent money on a new card.
But you have absolute discretion to choose what you want to do.

You seem to act like it's only loosing bits of precision in the output, when in reality what is likely to come out of the decoder is broken or corrupted output. From what I remember a couple of years back from an Ars Technica dicussion, someone tried to feed the 1st-gen Maxwell Hybrid decoder with 10-bit HEVC and they got output with a purplish haze to it. Which is completely broken and would be silly to allow.

[nevcairiel]

as I said before, it is just a demand by the users of old cards to watch 10bit HEVC, they don't care about losing 2 bits in output picture (according to the link given above). Maybe they don't want to spent money on a new card.
But you have absolute discretion to choose what you want to do.

Every card that can decode HEVC 10-bit through CUVID can also do it through DXVA2. There is literally no reason to use it, except when you are on Windows XP, but there is an easy fix for that, too, just install a supported OS.
Before I do *anything* for XP, I would rather remove support for it entirely to close this annoying topic down.

[kral2008]

Every card that can decode HEVC 10-bit through CUVID can also do it through DXVA2. There is literally no reason to use it, except when you are on Windows XP, but there is an easy fix for that, too, just install a supported OS.
Before I do *anything* for XP, I would rather remove support for it entirely to close this annoying topic down.

You seem to act like it's only loosing bits of precision in the output, when in reality what is likely to come out of the decoder is broken or corrupted output. From what I remember a couple of years back from an Ars Technica dicussion, someone tried to feed the 1st-gen Maxwell Hybrid decoder with 10-bit HEVC and they got output with a purplish haze to it. Which is completely broken and would be silly to allow.


By reading these two posts I understood the story. Now I convinced that CUVID is a dead one and spending time for it is wastage of your invaluable time. You are right.
So, I think the best way is buying a 1050 to extricated ourselves from the predicament.

[VictorLS]

kral2008
I understood long time ago if nevcairiel said no it is forever (I had to buy new GTX750v2 videocard about 100$ for perfect hardware acceleration 4K h265 8bit in WinXP and 10bit in Win7 - GTX1050 can 12bit but have not WinXP drivers - because he were not easy implement only key frame decoding in LAV Video Decoder, but I satisfied with my new videocard and thank nevcairiel one more time about it). But it is very pity because I think it is very easy to implement support h265 10bit in LAV Video Decoder through NVIDIA CUVID like in Linux https://devtalk.nvidia.com/default/topic/965840
WinXP has no problem with very critical problem for many people who watch SAT TV in Win7 and newer OS with files such DXVA_NVidia_bug.ts and 2016-09-20 21-15-33.ts
nevcairiel not said no yet about http://forum.doom9.org/showthread.php?p=1784305#post1784305
So we hope to use "supported" LAV Video Decoder in "supported" Win7-8 in players and DVB programs with NVIDIA CUVID as hardware accelerator before DXVA2 repearing in drivers of nVIDIA - if it is driver problem at all. I have to use "not supported" LAV CUVID Decoder 0.13 in "supported" Win7x64 now (but I prefer "not supported" WinXP with "supported" LAV Video Decoder). I have to uncheck h264 decoding in "supported" LAV Video Decoder - it is very hurts me )
captaiŋadamo
I see "purplish haze" when hardware decoding h265 12bit with CUVID in LAV Video Decoder or software decoding most of h265 10bit with Lentoid HEVC Decoder v2.1.0.2_2015_12_02_r4644 or "green haze" when software decoding all h265 10bit with Elecard HEVC Video Decoder (all both in WinXP and Win7x64). With Mainconcept HEVC Video Decoder software decoding of h265 10bit is well.
But in Linux with philipl's accident discovering h265 10bit hardware acceleration well decoding with CUVID is possible. I am sure in Windows XP-10 it is possible too but ... read first part of my this post.

[captaiŋadamo]

VictorLS, if you think it's so "very easy" to do all the things nev has said no to where are your pull requests to him that adds the features? You should have had all the time in the world to implement it by this point in time.

[nussman]

Nonsense by VictorLS (again) ...
DVB programs with LAV (DXVA) and Win7 or newer works just fine.
Try to setup your system properly instead of thinking about WinXP, Cuvid or other useless feature requests.

[VictorLS]

DVB programs with LAV (DXVA) and Win7 or newer works just fine.
Have you try to play DXVA_NVidia_bug.ts and 2016-09-20 21-15-33.ts with DXVA2 (or even CUVID if your card is nVIDIA and your OS is "supported" and not Win10) on your "perfect tuned" computer before write this? Did you read two pages from http://forum.doom9.org/showthread.php?p=1781141#post1781141 ? Especially http://forum.doom9.org/showthread.php?p=1781444#post1781444
Do you receive Russian's NTV+ provider from 36E? Or BBC or ITV https://www.youtube.com/watch?v=hCCBxKPOI84 and https://www.youtube.com/watch?v=Ek45LblB45k ? It is not my video and not my files. I and all that people of the world (I know much more people with same problem) are wrong and you are right? It is laughing ... I can receive more then 10000 TV channels and I am IT professional and I know what I say - DXVA2 (exaxtly HQ DXVA processing because turning it off in LAV CUVID Decoder giving perfect result in Win7) have bug and this is undiscussible.
I understood one more thing: nevcairiel is perfectionist - maximum quality despite of artifacts and so on ...
Am I wrong? ;)
captaiŋadamo, I think nevcairiel not implement h265 10bit support in CUVID because of noone bit could not be lost, I even think that he tried this with positive result already )
PS. It is a pity but any other decoder (including commercial) have no CUVID based h265 hardware acceleration.

[nevcairiel]

Feel free to use some other decoders if you wish, not forcing you to use LAV, but I can't fix driver bugs, no matter how hard I try. Also the "DXVA_NVidia_bug.ts" stream is broken, the stream just has errors on it, its not fully valid.
The youtube videos you listed are both for an RX480, which isn't even an NVIDIA card, and AMD royally screwed up the drivers for the Polaris cards in regards to DXVA and deinterlacing.

No matter how long you complain, there is nothing for me to change, so you might as well just stop and leave us all alone with your misery.

[nussman]

@VictorLS: Your testfile is broken. Thats what I mean ...

For DVBViewer users LAV Decoder (with dxva) is recommend and used all over the world without problems.
But of course there are "IT Professional WinXP user" as well complaining ...
Noone says LAV is perfect or bugfree, but your WinXP, CUVID posts (again and again) doesnt help!

[VictorLS]

Feel free to use some other decoders if you wish, not forcing you to use LAV
I have already answered in last string of http://forum.doom9.org/showthread.php?p=1784804#post1784804 before I read your post you send in 00:14
but I can't fix driver bugs, no matter how hard I try.
I believe but I wrote how you can fix bug for nVIDIA's videocards in supported Win7-8 http://forum.doom9.org/showthread.php?p=1784305#post1784305
Also the "DXVA_NVidia_bug.ts" stream is broken, the stream just has errors on it, its not fully valid.
Prove it, my proof in attachment. And what about 2016-09-20 21-15-33.ts - broken too? Many of NTV+ channels directly from SAT sometimes broken too (LAV CUVID Decoder without HQ DXVA Processing always decodes without any artifacts)?
The youtube videos you listed are both for an RX480, which isn't even an NVIDIA card, and AMD royally screwed up the drivers for the Polaris cards in regards to DXVA and deinterlacing.
I know many people from many forums which see such artifacts on many nVIDIA's and AMD's (before Polaris too) videocards - Gleb Egorych from http://forum.doom9.org/showthread.php?p=1781444#post1781444 one of them only. I did not understand them before I saw my own eyes in Win7 (when I tried in WinXP all was perfect).
nussman
you saw artifacts on both files? It yours first step to see truth )
is recommend
by whom?
I.e. World Health Organization recommend vaccinations, but it breaks your health )
In Russia we can to refuse from vaccinations yet, you are have do vaccinations.
used all over the world without problems
never say never )
not all use, for example Gleb Egorych not use already, read http://forum.doom9.org/showthread.php?p=1781444#post1781444

[nevcairiel]

I know many people from many forums which see such artifacts on many nVIDIA's and AMD's (before Polaris too) videocards -

Great, then get them all to report the issues to NVIDIA or AMD so the drivers can get fixed. I already told you, I cannot fix driver bugs, and I will not offer silly hacks just because you keep spaming my thread with rude remarks.

Please stop posting on this particular topic. Nothing will happen, and even less so if you keep annoying me and everyone else with it.

[VictorLS]

nevcairiel
I am free man and live in free country Russia and I do what I want to provide truth in the world which always win - you'll see it for example in case of country called Ukraine (right is may be New Russia - Novorossia) now which occupied by USA from 2014 (Victoria Nuland have spoken about 5 billion US dollars spent for revolution in Ukraine).
I knew you'll not prove DXVA_NVidia_bug.ts is "broken" file, because it is not true. I found one more link in this thread http://forum.doom9.org/showthread.php?p=1782481#post1782481 about this issue and I proposed the way to solve this issue in LAV Video Decoder above but you not hear )
Thank you for LAV CUVID Decoder which decodes "broken" files and shows "broken" SAT channels perfectly with hardware acceleration on nVIDIA in Win7-8. I tuned it for decoding h264 and LAV Video Decoder for others and all work perfectly. Once more it is a pity LAV CUVID Decoder can not decode h265.

[captaiŋadamo]

captaiŋadamo, I think nevcairiel not implement h265 10bit support in CUVID because of noone bit could not be lost, I even think that he tried this with positive result already )
PS. It is a pity but any other decoder (including commercial) have no CUVID based h265 hardware acceleration.

Then fork it and make a superior version and then you can be driving the bus. It's open source and all. Being an IT professional of the caliber you brag, it should be a trivial task as you already said that the changes required are very easy.

Otherwise, since nev has repeatedly said no, all you're doing at this point is thread shitting.

[ajp_anton]

Nev: Why don't you just remove CUVID already?

[filler56789]

... and remove Windows XP support as well.
Service Pack 3 is EIGHT years old already.

[Telion]

nevcairiel
I am free man and live in free country Russia
Oh LOL. So you're just trolling the thread here, mkay.

[VictorLS]

It's open source and all.
I know.
Being an IT professional
Do not you know difference between IT professional and professional programmer?
I decide any electrical below 240Volt including Power supply boards, UPSs, servers, computers, printers, scanners, IP-telephones and other such problems and programming not my professional duties - when problem do not solve by changing (or reinstalling) OS setup, registry, add/remove part of programs, dll's and so on I have to just describe problem, collect logs, screenshots and so on to professional progammers solve problems in his programs - they always solve without any additional questions and never say that problems not in they's programs because my description clever enough - I am sure I gave enough info to implement h265 10bit support in LAV Video Decoder. Besides I write simple programs on C# (in college long time ago I learn DOS and Pascal) sometimes to make people's life easier and I know how difficult to read code was written by other guy - my programs so for others. So I am sure that remove 10bit check when NVIDIA CUVID is choosen and add two strings in code with compilation not so difficult for guy who wrote LAV Video Decoder to decode h265 10bit by CUVID.
I just explain my point of view.
Nev: Why don't you just remove CUVID already?
... and remove Windows XP support as well.
After implementing h265 (including 10 and 12 bit - last for GTX10.0) decoding in LAV CUVID Decoder this is good idea to remove CUVID from LAV Video Decoder because users with nVIDIA videocard has potential advantage over users with AMD videocards to watch all SAT channels and play DXVA_NVidia_bug.ts and 2016-09-20 21-15-33.ts without artifacts with CUVID instead of DXVA2 in WinXP-8.
One more such file RussiaHD.ts (7MB) http://rgho.st/6SPGyTTMs
Repeat, I solved problem with artifacts in Win7 by combination of decoders (like my work is finding working combination, assistance other people and finding programmers that wrote not properly working program and deliver them information which help to solve problem) and help to solve it for many others.
you're just trolling the thread here
sometimes, because often there is no anything positive here last time - just nevcairiel's "I will not do" about many (not only mine) problems with LAV Filters. I understand, he have all rights to do nothing with LAV Filters because of freeware and opensource. But sometimes much easier to do something then seems simply say no )

[huhn]

seriously what is so hard to understand about this. it is a driver bug something NVIDIA has to fix. the DXVA decoder has to work.

just go there and tell them that there DXVA decoder, DXVA deinterlancer or what ever is broken and hope they are not ignoring you. end of story.

[clsid]

There is an easy way to disable the CUVID HQ processing mode. Run your player XP compatibility mode. But regardless, any playback issues are because of driver flaws. Using Windows XP is just stupid, certainly if you have new hardware.

[kral2008]

There is an easy way to disable the CUVID HQ processing mode. Run your player XP compatibility mode. But regardless, any playback issues are because of driver flaws. Using Windows XP is just stupid, certainly if you have new hardware.

Let us check if we can run hevc decoding with CUVID in newer versions of windows or not.

Victor's request is not stupid, he has just asked for a new feture in LAV; also he provided screen shots that when some people changed headers, etc. they could make it usable.

Of course, todays, no one wants to buy outdated cards, again I say if this issue could be colved only by simple changes, we ask LAV programmer, kindly, to spend his time to implement and evaluate what Victor mentioned in his post link.

:thanks:

[VictorLS]

it is a driver bug something NVIDIA has to fix. the DXVA decoder has to work.
strange that AMD drivers have same problem )
I'll check Intel next week myself - I not believe yours investigations.
just go there and tell them that there DXVA decoder, DXVA deinterlancer or what ever is broken and hope they are not ignoring you.
When I'll be absolutely sure it's driver issue (I wrote to nVIDIA's support many times and only one thing they not done - enabling custom vertical frequencies via nVIDIA's Control Panel in WinXP when my GT750v2 connected via DVI, but I found small program EnBtn and it works perfectly - I can set 50, 48, 47,952Hz in WinXP via nVIDIA's Control Panel because Settings... button becomes available) I'll write them about artifacts issue.
There is an easy way to disable the CUVID HQ processing mode. Run your player XP compatibility mode.
It works with CUVID in case of MPC-HC with internal LAV Video Decoder, but when I connect external same version of LAV Video Decoder artifacts returns. So DVBViewer shows artifacts too. So, add possibility of choice to disable HQ processing mode in LAV Video Decoder's interface (or automatically switch CUVID-DXVA2 as I mentioned above) is strongly recommended.
Using Windows XP is just stupid, certainly if you have new hardware.
Assume I have license of WinXP (my computer on 3-core CPU AMDx3 460 (was bought ~60$ in a store an year ago for software decoding of h264 1080p 4:2:2 only because hardware decoding 4:2:2 impossible even with new GTX10.0 - because previous 1-core 3000+ could decoding MPEG2 1080p 4:2:2 well only), old AM2 690G PCI-E 1.1 mainboard, DDR2 3GB because of WinXPx86, old DVB-S2 PCI SAT card and comparatively new PCI-E 3.0 GTX750v2 on GM206-150 I bought ~100$ for hardware h265 decoding only) - it do all I want perfectly, except h265 10bit hardware acceleration, I can not buy not bad Win7 for h265 10bit hardware acceleration only, because not on stock - I can buy only very bad Win10 (I tried it) without CUVID, so artifacts will be long time as minimum and I can not see well some programs and files )
Is this stupid? May be I am perfectionist too - I always want achieve great result with minimum money - Ukraine was poor country and now after revolution in 2014 is much more poorer. In Russia I can buy processors and videocards and much more, but I do not want to buy new computer - present computer is perfect for me.

[huhn]

H.264 content may experience blocky corruption when streaming using P2P content players on some Radeon RX 400 series graphics products.

http://support.amd.com/en-us/kb-articles/Pages/Radeon-Software-Crimson-Edition-16.11.2-Release-Notes.aspx

still not enough?

[VictorLS]

still not enough?
of course, not enough. Nothing about cause of blocky there: driver or DXVA in Windows.
As cause of poor life of normal (non-weaponed) people in former Ukraine is revolution 2014 and broken economic relations with Russia - not resistance of Donbass (Novorossia) to underlaw government in Kiev and weaponed nazi from west.

[avih]

Guys, this forum is about video and this thread is about LAV. Please keep it on topic. Thanks.

[VictorLS]

Guys, this forum is about video and this thread is about LAV. Please keep it on topic.
You are quite right, but some words at the end:

...
... If you want discuss it write PM, please.

[ offtopic content above edited out by avih ]


It's not black & white, there are grey zones especially on pesky video files and corner cases.
I mostly agree but I want to dig truth what namely problem of artifacts )
Now I see comparatively long GOP (26-39 from I to I frame) in files with artifacts (when DXVA2 used).

[avih]

@VictorLS, I've edited your message above and removed some offtopic content. Please keep this thread on topic, and feel free to discuss off topic subjects elsewhere, over PMs, etc. Thanks.

Consider this a warning too for everyone involved.

[DaMacFunkin]

Hello I hope someone can help me.
I have a GTX 1060 graphics card, is there anyway I can use Lav in conjunction with the hardware acceleration on the GPU and some other software to re encode HEVC to HEVC at a reasonable speed?
I thought the 1060 was capable of HEVC decode and encode, but I can't find a program to do both.
Thank you.

[huhn]

wrong thread but try this:
http://forum.doom9.org/showthread.php?t=172068

i don't know if it support direct dxva decoding but it supports avisynth and it is possible to feed avisynth with lavfilter so hardware decoding is possible.

just to make that clear you are wasting your time with the nvidia HEVC encoder...
you can better use the AVC hardware encoder which is bad too...

[DaMacFunkin]

Thank you.

[3421]

*****

[CruNcher]

@VictorLS
Try it under Linux with VDPAU DXVA in itself is sometimes wonky when it comes to time critical tasks ;)

But as a IT Professional you should actually know that Windows isn't really a good reliable Foundation for DVB tasks.

Especially from Russia :D

Or why do you think there are no Hardware DVB Players with Windows as Core.

as NikosD said there are corner cases and for DVB resilient playback i would never Personal use any Windows Device for anymore, even normal reliable/fast Video Playback is a adventure ;)

Try Linux + VDPAU

you have nothing to lose its free also no costs involved, there are other solutions as well but those will get really costly.

Or do the most sane thing and externalize the DVB Playback to a Dedicated Hardware based Solution.

[VictorLS]

CruNcher
I am SAT amateur, but I set up H-H (from 103e to 30w) mount and 1,2 meter offset dish with Ku-linear, Ku-circular and C-circular converters by myself.
WinXP with 50Hz output is good enough for me for any DVB task (including receiving Mulistream ,T2-MI, there is some artifacts sometimes with one Ukrainian transponder only because of Mutistream in T2-MI from 4e8 - few very expansive (semi-)professional tuners can receive that at all), except h265 10bit because of ... see this thread above.
With GTX750v2 Win7x64 is good enough too (I reinstall it sometimes) including h265 10bit. Both Windows can work day by day with working DVBViewer and never drop frames, freezes or crashes with strong signal in my case.
I have GalaxyInnovations HD Micro Plus not bad very small tuner (bought in summer 2014 about 60$ for absolute silence only) 3G modem can be inserted in one of two USB ports, but its picture quality via HDMI IMHO is poor with 1080p50 setting because of bad internal deinterlacer, with 1080i50 picture is great (almost as Openbox SX4 I tried) but I can not use BFI technology (to "speed up" liquid crystals) in my monitor BENQ FP241VW called Perfect Motion with 1080i50 and encrypted channels recordings can be played on my tuner only so I prefer WinXP )
When comparatively seldom some playback problems appears with some bad files in Windows I solve them easy by combination of filters or remuxing or TS-Doctor or so on.
About Core: did you mean CoreAVC?
About Linux + VDPAU: I am running Ubuntu from self-made boot flash to solve some professional problems. I have read that h265 10bit is problem too as in WinXP - only CUVID with changes decodes well by dithering to 8bit. Tell me, please, if this is not true or when this problem will be solved - I'll try if will be time.

[el Filou]

But as a IT Professional you should actually know that Windows isn't really a good reliable Foundation for DVB tasks.

Or why do you think there are no Hardware DVB Players with Windows as Core.

as NikosD said there are corner cases and for DVB resilient playback i would never Personal use any Windows Device for anymore, even normal reliable/fast Video Playback is a adventure ;)

Try Linux + VDPAU
Why would Windows not be reliable for DVB? The BDA framework is a tried and tested solution, and since the introduction of EVR and MMCSS media playback has been very reliable.
Any problems with DVB playback come from the graphics card drivers.

There are no Windows based hardware DVB players because manufacturers want to avoid paying a license fee and also Linux can be slimmed down much further than Windows for really specific tasks, but it hasn't anything to do with how good the technical base is.

I am running a HTPC for DVB-C (HD H.264) under Windows 10 myself and I can't see how Linux would be better for me.
And talking about dedicated hardware boxes, when I hear friends describe the experience they have with their provider's official hardware (lag, lack of GUI smoothness, lack of flexibility/removing of features, crashes, total corruption needing a factory reset, etc.), I'm quite happy with my Windows setup

(and LAV Filters are a big part of why I'm happy with it, btw, thanks for everything Nevcairiel! ;) )

[Nintendo Maniac 64]

I asked in the past, but I was drowned out by whatever discussion was occurring at the time so I'll ask again...

In LAVfilters, is there anyway to disable hardware decoding of 1080p while still allowing hardware decoding of 720p?

[nevcairiel]

No, thats not possible. Which hardware can handle 720p but not 1080p? and if you decode 1080p in software, why not lower resolutions as well?

[VictorLS]

I'll check Intel next week myself
Excuse me, huhn, for not believing about Intel - with integrated in Intel's processor videoadapter there is no artifacts while playing DXVA_NVidia_bug.ts and such files in Win7 with both DXVA2 and QuickSync in my experiments too.
Another my experiment: even integrated in chipset for AMD processor old nVIDIA 8200 has artifacts in Win7.

[P.J]

No, thats not possible. Which hardware can handle 720p but not 1080p? and if you decode 1080p in software, why not lower resolutions as well?

My GeForce 8600M GT DDR2 can't handle 1080i60/p60 while Core2 Duo T9300 can decode/de-interlace 1080i60 well.

[kral2008]

Excuse me, huhn, for not believing about Intel - with integrated in Intel's processor videoadapter there is no artifacts while playing DXVA_NVidia_bug.ts and such files in Win7 with both DXVA2 and QuickSync in my experiments too.
Another my experiment: even integrated in chipset for AMD processor old nVIDIA 8200 has artifacts in Win7.

Victor,
According to these links:
https://devtalk.nvidia.com/default/topic/971350/cuda-setup-and-installation/cuda-hw-acceleration-works-for-x264-but-x265-hevc-gives-me-quot-no-cuda-capable-device-is-detected-quot-/
and
https://developer.nvidia.com/nvidia-video-codec-sdk
You can't use CUVID HEVC with FFMPEG on linux even if you have 770 and older cards.
You can compile ffmpeg by association of CUVID HEVC but you can't use it to play files. Of course it compiles well without occuring any error, but you may face the error when you want to play HEVC encoded files.
So, I'm not sure about anything right now.