Sometimes failing to switch to correct PC resolution@hz - chooses TV resolution instead about displaymagician

[terrymacdonald]

Hi, I've looked through the logs you sent, and DisplayMagician appears to work correctly in the last four runs that you performed before generating the Support ZIP File. I also checked the Display Profiles, and your Home Theater profile is correctly set to 3840x2160x60.000Hz : "Extra": {

"Flags": 524288, "RefreshRate": 60, "FrequencyInMillihertz": 60000, "VerticalAspect": 900, "HorizontalAspect": 1600, "HorizontalPixelRepetition": 1, "TimingStandard": 406849793, "Name": "EDID-Detailed:3840x2160x60.000Hz" }

I did notice that your HDMI connection appears to go through from your NVIDIA RTX 3080 to a Denon AVR system. This potentially could be part of the problem. I've had a few people where their AV receiver caused an issue for them. You could try to bypass your Denon AVR system and go directly to your LG TV and see if the problem disappears? Another thing that causes issues like this is having very long HDMI cables. How long are your cables? Are they over 4m in length? You could move the TV closer to your PC and then try to use it with a short cable and see if the problem disappears. You should be able to eliminate both the Denon AVR unit and the cable length with a bit of testing. If you are still having issues even after the testing I;ve suggested above, then it's more likely that your LG TV itself is at fault here. I have known some TV's to not always set themselves correctly when receiving resolution commands. Monitor's seem to be more reliable, but even that's not always true of TV's. I'd try and see if there are any firmware updates for your LG TV. It is possible even a NVIDIA Driver or Windows Display Settings issue, but that is far less likely. In any case it is highly unlikely to be a DisplayMagician problem. DisplayMagician makes use of the NVIDIA, AMD and Windows API calls, so intermittent problems are generally a hardware or driver issue. If something reliably breaks and is repeatable then it could be a DisplayMagician problem, but intermittent issues are 99% hardware or driver issues. Hope that help clarify a little bit, and please drop a note back here after you've done some of the testing I've suggested above. Thanks *Terry* Message ID: <terrymacdonald/DisplayMagician/issue/158/issue_event/7747680918

…

@github.com>

[GibbousWaximus]

Hi Terry, thanks for your attention on this and also for the amazing software.
To clarify, the issue I'm seeing is when switching to my "Main" profile. The target resolution is the PC resolution 4k@120, but sometimes what gets set is the TV resolution 4k@60. I haven't looked at the contents of the support file, but I'll look through what's in there and see if I can find the example of the issue that occurred yesterday.

[terrymacdonald]

Hi, I've already checked the log files, and DisplayMagician reported no errors. This lines up with what is written earlier, as from DisplayMagician's point of view everything worked i.e. DisplayMagician asked the NVIDIA and windows display APIs to both apply some settings, and they replied with an answer saying that did that successfully. The fact that you experienced an issue yesterday and that there are no unexpected errors in the DisplayMagician log files makes me suspect the Denon AVR a little more. I strongly recommend performing those test steps that I mentioned in my last email, so that you can be sure what part of your setup is causing the problem. Hope that helps. I'm going to close the issue for now and Mark it as a 'notabug', as I don't think it's an issue with DisplayMagician, but that is an issue with some of the components of your system. I'm more than happy for you to keep replying with the results of your testing, and of you find something that points to DisplayMagician being the cause then we can reopen the issue and keep working on it. Thanks Terry

…

On Tue, 8 Nov 2022, 01:37 GibbousWaximus, ***@***.***> wrote: Hi Terry, thanks for your attention on this and also for the amazing software. To clarify, the issue I'm seeing is when switching to my "Main" profile. The target resolution is the PC resolution ***@***.***, but sometimes what gets set is the TV resolution ***@***.*** I haven't looked at the contents of the support file, but I'll look through what's in there and see if I can find the example of the issue that occurred yesterday. — Reply to this email directly, view it on GitHub <#158 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABLU5LAYWV7GQ2B5ENK5JWTWHDZX7ANCNFSM6AAAAAARYRA3YM> . You are receiving this because you were assigned.Message ID: ***@***.***>

[GibbousWaximus]

I'm willing to accept that this might just be an nvidia issue, or an LG issue I can't do anything about, but I also want to clarify that the issue is not with the display you focused on. I have two LG TV's connected. One is the "Hometheater" connection and that goes through the Denon AVR, that display is not the issue.

The display at issue is the other LG TV and it has a direct connection from the video card to the TV with a short, high quality cable.
From the config, this is the relevant display:
"DisplayId": 2147881089,
"Details": {
"Version": 65664,
"Rotation": 0,
"Scaling": 6,
"RefreshRateInMillihertz": 120000,
"Flags": 0,
"ConnectorType": 97,
"TvFormat": 556,
"TimingOverride": 0,
"Timing": {
"HVisible": 3840,
"HBorder": 0,
"HFrontPorch": 176,
"HSyncWidth": 88,
"HTotal": 4400,
"HSyncPol": 0,
"VVisible": 2160,
"VBorder": 0,
"VFrontPorch": 8,
"VSyncWidth": 10,
"VTotal": 2250,
"VSyncPol": 0,
"ScanMode": 0,
"Pclk": 118800,
"Extra": {
"Flags": 0,
"RefreshRate": 120,
"FrequencyInMillihertz": 120000,
"VerticalAspect": 9,
"HorizontalAspect": 16,
"HorizontalPixelRepetition": 1,
"TimingStandard": 494931318,
"Name": "CTA-861G:#118: 3840x2160x119.880Hz/P"
}
}
I'll see if I can induce the issue and if I think I have something new to add I'll update this ticket.
Thanks!

[terrymacdonald]

Oh sorry, I completely missed that in the email as you rightly pointed out! Thanks Terry

…

On Tue, 8 Nov 2022, 07:30 GibbousWaximus, ***@***.***> wrote: I'm willing to accept that this might just be an nvidia issue, or an LG issue I can't do anything about, but I also want to clarify that the issue is not with the display you focused on. I have two LG TV's connected. One is the "Hometheater" connection and that goes through the Denon AVR, that display is not the issue. The display at issue is the *other* LG TV and it has a direct connection from the video card to the TV with a short, high quality cable. From the config, this is the relevant display: "DisplayId": 2147881089, "Details": { "Version": 65664, "Rotation": 0, "Scaling": 6, "RefreshRateInMillihertz": 120000, "Flags": 0, "ConnectorType": 97, "TvFormat": 556, "TimingOverride": 0, "Timing": { "HVisible": 3840, "HBorder": 0, "HFrontPorch": 176, "HSyncWidth": 88, "HTotal": 4400, "HSyncPol": 0, "VVisible": 2160, "VBorder": 0, "VFrontPorch": 8, "VSyncWidth": 10, "VTotal": 2250, "VSyncPol": 0, "ScanMode": 0, "Pclk": 118800, "Extra": { "Flags": 0, "RefreshRate": 120, "FrequencyInMillihertz": 120000, "VerticalAspect": 9, "HorizontalAspect": 16, "HorizontalPixelRepetition": 1, "TimingStandard": 494931318, "Name": "CTA-861G:#118 <#118>: 3840x2160x119.880Hz/P" } } I'll see if I can induce the issue and if I think I have something new to add I'll update this ticket. Thanks! — Reply to this email directly, view it on GitHub <#158 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABLU5LCQDWI6O73UZD4UOSLWHFDF5ANCNFSM6AAAAAARYRA3YM> . You are receiving this because you were assigned.Message ID: ***@***.***>

[terrymacdonald]

@GibbousWaximus,

Just checking in to see if you've still been having the problem with your "Main" profile, and if you have whether you've been able to figure out a pattern for when it occurs? I'm kinda at a loss for what to test next to be honest after re-reading this issue, so I'm really hoping that it's either righted itself with a display driver update, or that you've noticed a pattern that we can use to figure out some other tests....

Thanks
Terry

[terrymacdonald]

Hi @GibbousWaximus,

I'll close this issue for now but please reopen this issue of you start experiencing the same issue again. I'm hoping that you'll be able to discover another interesting bit of information if it fits happen again that will let us unlock what is going on here, but for now I'll close this issue so that I know where I'm up to trusting the rest of the open issues.

Please return this issue if you have the same problem again, or create a new issuer if you get a different problem.

Thanks
Terry