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.

 

Go Back   Doom9's Forum > Hardware & Software > Software players

Reply
 
Thread Tools Search this Thread Display Modes
Old 21st January 2021, 01:06   #1481  |  Link
QBhd
QB the Slayer
 
QBhd's Avatar
 
Join Date: Feb 2011
Location: Toronto
Posts: 697
I have been on Auto since day 1... but like you I am not sure if it is correct or not. I may do a few measurements this week... maybe

QB
__________________
QBhd is offline   Reply With Quote
Old 21st January 2021, 14:05   #1482  |  Link
quietvoid
Registered User
 
Join Date: Jan 2019
Location: Canada
Posts: 570
I've read that it just increases saturation artificially, but it's weird to name an option that way.
quietvoid is offline   Reply With Quote
Old 21st January 2021, 19:36   #1483  |  Link
chros
Registered User
 
chros's Avatar
 
Join Date: Mar 2002
Posts: 2,323
Quote:
Originally Posted by quietvoid View Post
I've updated my 2018 to 05.30.10, reset all settings.
No improvement for Dolby Vision black levels, contrast 99 looks weird.
Cheers. According to Vincent, they just recently fixed the CX DV black issue with the 2nd firmware release, not before.

Quote:
Originally Posted by quietvoid View Post
I'm questioning one thing, what do you guys have set for Color Gamut in HDR?
Auto looks less saturated than Wide, with all my inputs (FireTV stick, madVR).
But I don't know if Wide is accurate.
I also use Auto (Cinema preset default) with HDR10. The interesting part is that I tried it with Cinema Home preset, and "Extended" is the very same as Auto (Cinema) and not "Wide"!

Quote:
Originally Posted by QBhd View Post
I have been on Auto since day 1... but like you I am not sure if it is correct or not. I may do a few measurements this week... maybe
That would be nice, I only measured SDR.

Quote:
Originally Posted by quietvoid View Post
I've read that it just increases saturation artificially, but it's weird to name an option that way.
Which option? Wide?
__________________
Ryzen 5 2600,Asus Prime b450-Plus,16GB,MSI GTX 1060 Gaming X 6GB(v398.18),Win10 LTSC 1809,MPC-BEx64+LAV+MadVR,Yamaha RX-A870,LG OLED77G2(2160p@23/24/25/29/30/50/59/60Hz) | madvr config
chros is offline   Reply With Quote
Old 21st January 2021, 19:39   #1484  |  Link
quietvoid
Registered User
 
Join Date: Jan 2019
Location: Canada
Posts: 570
Quote:
Originally Posted by chros View Post
Which option? Wide?
Yes, Wide.
quietvoid is offline   Reply With Quote
Old 22nd January 2021, 03:26   #1485  |  Link
SamuriHL
Registered User
 
SamuriHL's Avatar
 
Join Date: May 2004
Posts: 5,351
Quote:
Originally Posted by quietvoid View Post
I've updated my 2018 to 05.30.10, reset all settings.
Not available for me yet. Didn't even know they put a new build out. Typical.
__________________
HTPC: Windows 11, AMD 5900X, RTX 3080, Pioneer Elite VSX-LX303, LG G2 77" OLED
SamuriHL is offline   Reply With Quote
Old 22nd January 2021, 03:33   #1486  |  Link
SamuriHL
Registered User
 
SamuriHL's Avatar
 
Join Date: May 2004
Posts: 5,351
[05.30.10]
1. Improved disconnection in certain apps after software update

Really? Yawn.
__________________
HTPC: Windows 11, AMD 5900X, RTX 3080, Pioneer Elite VSX-LX303, LG G2 77" OLED
SamuriHL is offline   Reply With Quote
Old 22nd January 2021, 04:31   #1487  |  Link
quietvoid
Registered User
 
Join Date: Jan 2019
Location: Canada
Posts: 570
The 05.30.02 update had a lot of issues with WiFi slowing down significantly and even dropping.
They didn't mess around to publish a hotfix.
Basically these last updates just add AirPlay support.
quietvoid is offline   Reply With Quote
Old 22nd January 2021, 05:35   #1488  |  Link
Asmodian
Registered User
 
Join Date: Feb 2002
Location: San Jose, California
Posts: 4,406
I am very happy to report that firmware 03.21.16 seems to have solved my near black banding problem when sending full range RGB to my 48" LG CX.

After recalibrating with the new firmware (which was needed) I am happy running 10 bit RGB full 120 Hz to the display, though I still have madVR dithering to 8 bit to reduce banding.
__________________
madVR options explained
Asmodian is offline   Reply With Quote
Old 22nd January 2021, 07:20   #1489  |  Link
SamuriHL
Registered User
 
SamuriHL's Avatar
 
Join Date: May 2004
Posts: 5,351
Where's that one finger salute emoji..... Lmao! I'm glad they fixed it for you. I just wish they'd maybe back port a few fixes. Sigh

Sent from my SM-G975U using Tapatalk
__________________
HTPC: Windows 11, AMD 5900X, RTX 3080, Pioneer Elite VSX-LX303, LG G2 77" OLED
SamuriHL is offline   Reply With Quote
Old 23rd January 2021, 21:08   #1490  |  Link
chros
Registered User
 
chros's Avatar
 
Join Date: Mar 2002
Posts: 2,323
Quote:
Originally Posted by SamuriHL View Post
I'm glad they fixed it for you.
Better later than never But seriously, 9 months after releasing a product ... finally DV is maybe good now

Quote:
Originally Posted by chros View Post
You can pick up scenes as well, share the timestamps and that's it.
- let's use 800/75 then for now
-- "disabled avgHL ceiling" enabled
-- "don't add peak nits" enabled
-- all the other unnecessary options disabled (contrast/shadow recovery, dynamic clipping, sky strength)
- that means DTN will kick in at ~184 FALL (if frame peak > DPL)
- the question is what FALL/scene combo DTN is really needed and is there any scene in the title when DTN is unnecessary with these settings
-- if we can come up with a DTN value at the end for this title then that'd be the best

One more important thing:
- madvr can/does result in different ADPLs during playback vs still images!

The Grinch is very bright, so it's easy to find scenes like this:
- 1: 00:02:05 - 00:03:20 (2985 - 4784)
- 2: 00:06:45 - 00:07:25 (9699 - 10658)
- 3: 00:13:10 - 00:14:00 (18930 - 20130)
-- this scene is interesting, there are frames when frame peak is only ~430 but FALL is >200.
- 4: 00:16:00 - 00:16:45 (23006 - 24086)
So, I had a little time to play with these (I added frame numbers to scenes as well), in short:
- I disabled (!) DTN for "normal" content (in my default HDR10 profile)

Here is why, DTN cause more harm than good with "normal" content:
- I haven't seen any frames that needs DTN (dimming)
- madvr works with scenes:
-- it resets on scene changes
-- within a scene it slowly corrects itself
--- often happens that there are high FALL frames for only couple of seconds that still unnecessarly dim the following frames in the same scenes

The real question is what contents are "normal" for us high DPL users, based on avgHL or frame peak or something else (as we already talked about it). I bet 95% of the content we come across today are like this.

What clear now is that the current implementation of DTN is completely wrong for high DPLs, meaning we definitely can't use 1 profile settings for all the content we have.
__________________
Ryzen 5 2600,Asus Prime b450-Plus,16GB,MSI GTX 1060 Gaming X 6GB(v398.18),Win10 LTSC 1809,MPC-BEx64+LAV+MadVR,Yamaha RX-A870,LG OLED77G2(2160p@23/24/25/29/30/50/59/60Hz) | madvr config

Last edited by chros; 23rd January 2021 at 21:13.
chros is offline   Reply With Quote
Old 23rd January 2021, 21:38   #1491  |  Link
SamuriHL
Registered User
 
SamuriHL's Avatar
 
Join Date: May 2004
Posts: 5,351
LG hasn't given me a whole lot of reasons to upgrade my C8. Lower max nit level. Still screwed up DV (may be fixed finally?! WOO?). PC mode still not 100% awesome. I mean they're getting better but I'd need a flawless panel to get me to want to upgrade. I want to see what the hell they've done this year because the Cx (not to be confused with the CX LOL) line didn't get the upgraded panel tech this year. WTF? They really know how to confuse people.
__________________
HTPC: Windows 11, AMD 5900X, RTX 3080, Pioneer Elite VSX-LX303, LG G2 77" OLED
SamuriHL is offline   Reply With Quote
Old 23rd January 2021, 22:41   #1492  |  Link
chros
Registered User
 
chros's Avatar
 
Join Date: Mar 2002
Posts: 2,323
I agree, and not to mention new panel issues: horizontal banding, grid pattern, etc.
For me the biggest issue with separating Gx from Cx is that these will have different firmwares! What a mess this will be
__________________
Ryzen 5 2600,Asus Prime b450-Plus,16GB,MSI GTX 1060 Gaming X 6GB(v398.18),Win10 LTSC 1809,MPC-BEx64+LAV+MadVR,Yamaha RX-A870,LG OLED77G2(2160p@23/24/25/29/30/50/59/60Hz) | madvr config
chros is offline   Reply With Quote
Old 24th January 2021, 00:36   #1493  |  Link
Asmodian
Registered User
 
Join Date: Feb 2002
Location: San Jose, California
Posts: 4,406
I am hoping all models get the new panels in 2022 and re-unify the Cx and Gx.

Quote:
Originally Posted by SamuriHL View Post
PC mode still not 100% awesome.
I agree that it isn't 100% awesome but the newest firmware on the 2020 models solved my last significant issue with PC mode. Banding seems similar in PC mode v.s. HDMI mode now, in both HDR and SDR.

I can always get more picky, and there are plenty of imperfections when I do, but PC mode has improved so much since my C7 that I have to be happy about it. At least for a bit.
__________________
madVR options explained

Last edited by Asmodian; 24th January 2021 at 02:39. Reason: x not X.. C0 G0 would have been less confusing than CX and GX if they didn't want C10 and G10
Asmodian is offline   Reply With Quote
Old 24th January 2021, 00:54   #1494  |  Link
aron7awol
Registered User
 
Join Date: Dec 2020
Posts: 136
Quote:
Originally Posted by chros View Post
So, I had a little time to play with these (I added frame numbers to scenes as well), in short:
- I disabled (!) DTN for "normal" content (in my default HDR10 profile)

Here is why, DTN cause more harm than good with "normal" content:
- I haven't seen any frames that needs DTN (dimming)
- madvr works with scenes:
-- it resets on scene changes
-- within a scene it slowly corrects itself
--- often happens that there are high FALL frames for only couple of seconds that still unnecessarly dim the following frames in the same scenes

The real question is what contents are "normal" for us high DPL users, based on avgHL or frame peak or something else (as we already talked about it). I bet 95% of the content we come across today are like this.

What clear now is that the current implementation of DTN is completely wrong for high DPLs, meaning we definitely can't use 1 profile settings for all the content we have.
Did you have sky detection turned on? I found DTN to not do very much with The Grinch with it on, which sounds like what you want it to do.
aron7awol is offline   Reply With Quote
Old 24th January 2021, 01:17   #1495  |  Link
chros
Registered User
 
chros's Avatar
 
Join Date: Mar 2002
Posts: 2,323
It was off as per instructions along with the others. My point is that based on those 4 scenes TG doesn't need DTN!
__________________
Ryzen 5 2600,Asus Prime b450-Plus,16GB,MSI GTX 1060 Gaming X 6GB(v398.18),Win10 LTSC 1809,MPC-BEx64+LAV+MadVR,Yamaha RX-A870,LG OLED77G2(2160p@23/24/25/29/30/50/59/60Hz) | madvr config
chros is offline   Reply With Quote
Old 24th January 2021, 01:42   #1496  |  Link
aron7awol
Registered User
 
Join Date: Dec 2020
Posts: 136
Quote:
Originally Posted by chros View Post
It was off as per instructions along with the others. My point is that based on those 4 scenes TG doesn't need DTN!
Okay, but sky detection seems to work perfectly on that movie to lower FALL so that DTN does little/nothing, which seems to be exactly what you want on those scenes. Otherwise, you have to lower DTN in order to stop it from kicking in and see how that lower DTN works with other content.

Sky detection is designed to work hand-in-hand with DTN (it modifies FALL only for the DTN calc and does nothing else), so I think it's premature to conclude that the current implementation of DTN is completely wrong for high DPLs when we've only tested a single DTN and only without sky detection doing its job to lower targets in flat skies which are abundant in The Grinch.

I think if you enable sky detection on those scenes you will come to quite the opposite conclusion, that the targeting actually ends up very close to where you want it on those scenes with the 75 DTN.

Last edited by aron7awol; 24th January 2021 at 01:46.
aron7awol is offline   Reply With Quote
Old 24th January 2021, 12:32   #1497  |  Link
chros
Registered User
 
chros's Avatar
 
Join Date: Mar 2002
Posts: 2,323
Quote:
Originally Posted by aron7awol View Post
Okay, but sky detection seems to work perfectly on that movie to lower FALL so that DTN does little/nothing, which seems to be exactly what you want on those scenes. Otherwise, you have to lower DTN in order to stop it from kicking in and see how that lower DTN works with other content.
Yes, it helps, bit still not perfect, DTN is triggered once in scene 2 (although just for a short time), but in scene 4 similar thing happens than without it:
- "disable avgHL ceiling" disabled
- avgHL ceiling: 2x
- sky strength: 100

Quote:
Originally Posted by aron7awol View Post
that the targeting actually ends up very close to where you want it
And that is my point: it doesn't. I think TG (that is an extreme example of "normal" contents) doesn't need DTN at all.

So, if someone comes across these type of contents (e.g. maxCLL < 1300-1600 nits) that benefit from DTN then please share it (with timestamps).
__________________
Ryzen 5 2600,Asus Prime b450-Plus,16GB,MSI GTX 1060 Gaming X 6GB(v398.18),Win10 LTSC 1809,MPC-BEx64+LAV+MadVR,Yamaha RX-A870,LG OLED77G2(2160p@23/24/25/29/30/50/59/60Hz) | madvr config
chros is offline   Reply With Quote
Old 24th January 2021, 13:53   #1498  |  Link
aron7awol
Registered User
 
Join Date: Dec 2020
Posts: 136
So let's focus on those scenes where it is doing what you don't want it to do, even with sky detection enabled.

For each of those scenes make a note of:
With sky detection enabled, what is FALL, and what is the resulting target?
If you lower avgHL multiplier further, is there a point where it kicks in?
Does changing the sky max width 10 vs 20 or the hill settings help ?
aron7awol is offline   Reply With Quote
Old 24th January 2021, 22:25   #1499  |  Link
aron7awol
Registered User
 
Join Date: Dec 2020
Posts: 136


Did some testing of those same scenes to see what impact the avgHL ceiling and sky detection would have on those frames which result in targets >800 with just DTN 75:

1. Sky detection lowered the target down to 800 in 4 out of the 6 frames.
2. In the two remaining frames, a 2.5x avgHL ceiling lowered the target down to 800.
3. Thus, running sky detection and a 2.5x avgHL ceiling resulted in a target of 800 in all of the frames tested.

I went back at the end to one of those two frames (6:59 shown at the bottom of the list) where sky detection didn't lower the target, and tested Dynamic Clipping to see if it would have any impact. A value as low as 20 lowered the target down to 800 alone.

So I think this is a good exercise showing the power of the ancillary functions of the algo, where we see each of them able to chip in and lower targets in certain cases, and although one of them alone didn't do that completely, when enabled together they can combine to give us the targets we want. And let's keep in mind we haven't even established that 75 DTN is what we want, but it still shows that DTN can work for this particular movie with sky and avgHL ceiling enabled.

I added a column to the far right showing the maximum DTN for each frame that would result in a target of 800. I think that columns shows nicely that relying on just a single DTN FALL multiplier to end up at the right targets is an exercise in futility, and that some ancillary functions are essentially required in order to get good targets. I don't see this as a knock on DTN, it's just that FALL alone only tells us so much, and so the FALL multiplier is just one piece of the puzzle.

So @chros, I think if you run through The Grinch with sky detection on and a 2.5x avgHL ceiling (I'm leaving DC off for now because of the order-of-operations error when used concurrently with sky detection) you'll be very happy with the resulting targets. The question then becomes, are there any frames where that combo results in a target we aren't happy with? We now need to find those so we can take the next steps.

Edit: I went back through with those settings and found a frame at 2:20 which resulted in a target >800. The target was 830, which was avgHLx2.5 and so avgHL was 332 for this frame. Lowering DTN to 65 lowered the target to 800. Additionally, I switched back and forth between the 800 and 830 target for this frame and really couldn't tell any difference anyway.

Edit2: Also forgot to mention that 2.75x works almost as well as 2.50x to keep those targets down. It resulted in some that were something like 806 nits instead of 800 but that's inconsequential. Just wanted to mention it because 2.50x might be a little lower than we want for some other stuff like The Meg. FWIW, my previous testing had found an avgHL multiplier that was approximately 70% of FALL multiplier seemed to work well, which in this case would be 3.05x for the 800/75 combo. That is the exact combo I liked a lot with The Meg: 800/75 3.00x. This is good, I think, that combo of settings actually works quite well on both The Grinch and The Meg. I might choose something in between 2.75x and 3.00x if that were possible.

Last edited by aron7awol; 25th January 2021 at 15:39.
aron7awol is offline   Reply With Quote
Old 25th January 2021, 23:20   #1500  |  Link
chros
Registered User
 
chros's Avatar
 
Join Date: Mar 2002
Posts: 2,323
Thanks for the detailed post, but I got different results than you, how is this possible?
Here are the 2 frames (that cause the issues in scene 2 and 4, you can you ctrl+g in mpcbe to jump there (note that directshow isn't not frame accurate seeking), and btw there's a new repeat A-B feature in the latest mpc-be beta (under Play -> Repeat) that is really useful for testing scenes )

Here's my settings (note that I still use b119, not the newest):
- note I used my SDR monitor for reading data from it (not image comparison, for that I used the TV)
-- calibration is set to bt2020 (although just the measured peak changes with e.g. bt709)
- lum method and desat options doesn't seem to change anything
- max width of sky strength doesn't seem to change anything either (using these 2 frames)

1. @7:12 frame 10361: frame peak 990 (vs 977), FALL 321.4 nits (vs 324)
- 2.5x avgHL: 990 (vs 977)
- sky100: 823 (vs 800) (FALL 188.62)
- 2.5x avgHL + sky100: 823 (vs 800) (so sky detection does the job here alone)

Now I wonder where the different values come from in your vs my case...

2. @16:17 frame 23434: frame peak 809, FALL 465 nits
- 2.5x avgHL: 809
- sky100: 809 (FALL 443.49)
- 2.5x avgHL + sky100: 809

This is the first frame of the scene, it's seemingly harmless, but that's (and the following high FALL frames) the cause for dimming other frames unnecessarely here.
__________________
Ryzen 5 2600,Asus Prime b450-Plus,16GB,MSI GTX 1060 Gaming X 6GB(v398.18),Win10 LTSC 1809,MPC-BEx64+LAV+MadVR,Yamaha RX-A870,LG OLED77G2(2160p@23/24/25/29/30/50/59/60Hz) | madvr config
chros is offline   Reply With Quote
Reply

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT +1. The time now is 00:39.


Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2024, vBulletin Solutions Inc.