Welcome to Doom9's Forum, THE in-place to be for everyone interested in DVD conversion. Before you start posting please read the forum rules. By posting to this forum you agree to abide by the rules. |
1st August 2020, 19:35 | #23981 | Link |
Registered User
Join Date: Oct 2016
Posts: 896
|
I don't know about Sat as I'm using cable, but I don't understand why TV providers would use certain unusual codec profiles if hardly anybody would be able to receive them?
__________________
HTPC: Windows 10 22H2, MediaPortal 1, LAV Filters/ReClock/madVR. DVB-C TV, Panasonic GT60, Denon 2310, Core 2 Duo E7400 oc'd, GeForce 1050 Ti 536.40 |
1st August 2020, 22:55 | #23982 | Link | |
Registered User
Join Date: Mar 2009
Location: Russian Crimea
Posts: 335
|
So you receive and watch DVB-C - I'm DVB-S2(X).
Quote:
|
|
11th August 2020, 04:06 | #23984 | Link |
Registered User
Join Date: Dec 2008
Posts: 4
|
Question regarding LAV Splitter's queue. Would any problems arise if I were to set the Maximum Queue Memory to, say, almost as much ram as I have?
I just got a new hard drive, and it's the loudest thing ever when at low read/write speeds, say the normal 8-14mbs while playing a film. My idea to solve this is to basically have it queue up as much as possible as it's playing, which forces the drive into ~250mbs speeds, which lo and behold, produces no hard drive noise at all. And if I do do this, do I increase the queue packets too? And to what? I guess my main question is, am I damaging my hard drive or my ram? Haha. Or maybe if there's a better way to get higher read speeds during film playback. Last edited by Rusty100; 11th August 2020 at 04:20. |
11th August 2020, 06:50 | #23985 | Link | |
Registered User
Join Date: Dec 2002
Posts: 5,565
|
To quote the author:
Quote:
|
|
12th August 2020, 00:02 | #23986 | Link |
Moderator
Join Date: Feb 2005
Location: Spain
Posts: 6,890
|
Posts deleted by Rule 6:
6) No warez, cracks, serials or illegally obtained copyrighted content! Links to content of a questionable nature (e.g. anything you don't own and/or have downloaded), asking for, offering, or asking for help/helping to process such content in any way or form is not tolerated.
__________________
BeHappy, AviSynth audio transcoder. |
12th August 2020, 13:56 | #23987 | Link | |
Registered User
Join Date: Oct 2015
Posts: 29
|
Quote:
That clarification the developer wrote can stand on its own without any context, it could help someone who has the same issues in the future. |
|
13th August 2020, 11:41 | #23990 | Link |
Registered User
Join Date: Aug 2010
Location: Athens, Greece
Posts: 2,901
|
You are one of a kind, but too strict.
All rules are made to be broken, sometimes.
__________________
Win 10 x64 (19042.572) - Core i5-2400 - Radeon RX 470 (20.10.1) HEVC decoding benchmarks H.264 DXVA Benchmarks for all |
15th August 2020, 05:59 | #23991 | Link |
Registered User
Join Date: Dec 2008
Posts: 4
|
Oh great. That's good info, thank you! Setting the queue to around 10gb of my available 16, seeking is still quite fast thankfully. For some reason, after the high speeds die down as I hit the maximum allowance, the noise doesn't return during playback. Like forcing it into prolonged high speeds to begin with negates eventual low-speed noise. Go figure. I can't believe hard drives are still like this sometimes. I hate seagate.
|
16th August 2020, 19:05 | #23992 | Link |
German doom9/Gleitz SuMo
Join Date: Oct 2001
Location: Germany, rural Altmark
Posts: 6,753
|
I just noticed that some hardware decoders (in my case, Nvidia PureVideo on GTX 1660 Super) may fail decoding AVC with 8 bpc in high resolutions (4K UHD and beyond). Using DXVA2 native or CUVID, I noticed heavy distortions (motion vector related, I guess?) which did not appear without hardware accelerated decoding (avcodec mode). Decoding AVC with 10 bpc or HEVC was fine.
Anyone interested in details? Any suggestions how to possibly configure LAV Filters to fall back automatically in this case? |
16th August 2020, 19:48 | #23993 | Link |
Registered User
Join Date: Aug 2010
Location: Athens, Greece
Posts: 2,901
|
A sample of the mentioned 4K H.264 8bit clip would help.
I could test it.
__________________
Win 10 x64 (19042.572) - Core i5-2400 - Radeon RX 470 (20.10.1) HEVC decoding benchmarks H.264 DXVA Benchmarks for all |
16th August 2020, 19:51 | #23994 | Link | |
Registered User
Join Date: Aug 2010
Location: Athens, Greece
Posts: 2,901
|
Quote:
All HW decoders of three (AMD, Intel, nVidia) stop at 4K regarding H.264 decoding.
__________________
Win 10 x64 (19042.572) - Core i5-2400 - Radeon RX 470 (20.10.1) HEVC decoding benchmarks H.264 DXVA Benchmarks for all |
|
17th August 2020, 07:28 | #23995 | Link |
German doom9/Gleitz SuMo
Join Date: Oct 2001
Location: Germany, rural Altmark
Posts: 6,753
|
Nightsky_2160p.mp4 - watch the bottom left third at around 2 seconds for the most obvious glitches, there are a few more at the bottom.
It happens as well on a GTX 1050 Ti. |
17th August 2020, 08:25 | #23996 | Link |
Registered Developer
Join Date: Mar 2010
Location: Hamburg/Germany
Posts: 10,344
|
Strictly speaking hardware decoders are (typically) limited to Level 5.1 or 5.2, your file is Level 6.0, so it might as well exceed the supported rates of the decoder. What part of it does actually exceed anything, I can't say without a much deeper investigation.
I suppose maybe I should limit the level to 5.1 (or 5.2). I have historically not added many level checks because the levels are often wrong - at least on the lower end, but I guess anyone encoding something at level 6.0 or higher will know what they are doing. My first best guess is that the size of the DPB is being exceeded as Level 5.1/5.2 do not allow 8 ref frames for 4K, and level 6 allows up to 16. If you wanted to confirm, you could re-encode with at most 5 ref frames to stay within the limits of level 5.2 (or directly enforce level 5.2 limits, if possible) The resolution alone wouldn't cause this, as we've been decoding 4K H264 content for years now, so the above assumption with the DPB seems most likely.
__________________
LAV Filters - open source ffmpeg based media splitter and decoders Last edited by nevcairiel; 17th August 2020 at 11:30. |
17th August 2020, 11:54 | #23997 | Link |
Registered User
Join Date: Aug 2010
Location: Athens, Greece
Posts: 2,901
|
I'll take a look at the sample when I return home, but since you have already tried Pascal and Turing decoders, I'll try Polaris and Haswell H.264 HW decoders.
The truth is that 8K H.264 is not commercial and H.264 HW decoders have left behind supporting only 4K, although x264 and other encoders can encode H.264 at 8K resolution. As nevcairiel said, probably someone could encode 4K H.264 at higher level than L5.x which was the highest level at the 4K H.264 era of HW decoders and is mainly used for 4K encoding. Haswell's and probably onwards Intel's HW H.264 is the fastest (even from Turing) and I have already tested 4K H.264 L5.2 Ref 16 with huge bandwidth (1Gbps) and with success. However, I haven't tried before 4K H.264 at L6.x using any HW decoder. Interesting.
__________________
Win 10 x64 (19042.572) - Core i5-2400 - Radeon RX 470 (20.10.1) HEVC decoding benchmarks H.264 DXVA Benchmarks for all |
17th August 2020, 12:32 | #23998 | Link |
German doom9/Gleitz SuMo
Join Date: Oct 2001
Location: Germany, rural Altmark
Posts: 6,753
|
The slow and very predictable motion of stars in a nightsky timelapse seems to benefit from long range references. Not much surprising. I guess a very verbose log could reveal interesting details.
I limited the references to 5 (and accordingly the level to 5.1); as expected, no glitches spotted in DXVA2 HW mode. |
17th August 2020, 20:14 | #23999 | Link |
Registered User
Join Date: Aug 2010
Location: Athens, Greece
Posts: 2,901
|
I tried all HW modes of Intel iGPU (QuickSync, DXVA2 CB, DXVA2 Native, D3D11) and AMD RX 470 (DXVA2 CB, DXVA2 native and D3D11) that LAV Video (latest nightly) provides with EVR-CP and MPC-VR renderers.
Both HW decoders appear to have exactly the same issue with image distortion, as you mentioned using Pascal and Turing. The only interesting point I want to report is QuickSync that falls back automatically to SW decoding. I don't know if LAV or Intel's MediaSDK are responsible for this behavior, but it seems that it is what you asked for.
__________________
Win 10 x64 (19042.572) - Core i5-2400 - Radeon RX 470 (20.10.1) HEVC decoding benchmarks H.264 DXVA Benchmarks for all |
18th August 2020, 07:23 | #24000 | Link |
German doom9/Gleitz SuMo
Join Date: Oct 2001
Location: Germany, rural Altmark
Posts: 6,753
|
It may be the safe way to assume, according to Murphy's Law, that material flagged as "beyond hardware limits" regarding Profile@Level will probably cause issues, and fall back to software decoding. With or without a choice for the user in the UI. I don't expect any smarter solution than a P@L based decision. A decoding error that happened in a hardware decoder would probably not even be detectable by LAV Filters as the process using it, only by the human eyes.
|
Tags |
decoders, directshow, filters, splitter |
Thread Tools | Search this Thread |
Display Modes | |
|
|