NVCP 'Change Resolution" Nvidia Color Settings switch from RGB 'Full' to YCbCr422 'Limited' when changing from triples to desktop monitor about displaymagician

[terrymacdonald]

Oh interesting @Globespy - I don't think I've had anyone using the output color format before, so that's quite interesting in of itself.

My gut feel is that either the DP Switch or NVIDIA Driver is impacting this in some way. DisplayMagician simply records the settings from the NVIDIA Driver, and then applies them again when they are needed. DisplayMagician definitely records the Color Format on your computer, as is shown from this snippet from your NV Triples 144Hz profile:

            "HdrColorData": {
                "Version": 131124,
                "Cmd": 0,
                "HdrMode": 2,
                "StaticMetadataDescriptorId": 0,
                "MasteringDisplayData": {
                  "DisplayPrimaryX0": 33935,
                  "DisplayPrimaryY0": 15820,
                  "DisplayPrimaryX1": 13427,
                  "DisplayPrimaryY1": 32128,
                  "DisplayPrimaryX2": 7177,
                  "DisplayPrimaryY2": 2783,
                  "DisplayWhitePointX": 15673,
                  "DisplayWhitePointY": 16455,
                  "MaxDisplayMasteringLuminance": 518,
                  "MinDisplayMasteringLuminance": 815,
                  "MaxContentLightLevel": 518,
                  "MaxFrameAverageLightLevel": 518
                },
                "HdrColorFormat": 0,
                "HdrDynamicRange": 0,
                "HdrBpc": 2
              },
            ....
            "ColorData": {
                "Version": 327704,
                "Size": 0,
                "Cmd": 1,
                "ColorFormat": 0,
                "Colorimetry": 2048,
                "DynamicRange": 2,
                "Bpc": 0,
                "ColorSelectionPolicy": 0,
                "Depth": 0
              },

As you can see above, the HdrColorFormat is recorded as 0 (RGB), and the ColorFormat is recorded as 0 (RGB) and the Colorimetry value is 2048 (NV_COLOR_COLORIMETRY_AUTO). Note - we record both as different structures are used depending if the display is in HDR more or standard mode.

Looking at your Desktop Ultrawide profile, I can see that NVHDR HDR isn't enabled for that monitor, so the normal color mode applies, and it uses the settings from the ColorData object shown below. As you can see, the object uses a ColorFormat of 0 (RGB), and a Colorimetry value of 0 (NV_COLOR_COLORIMETRY_RGB)

            "ColorData": {
                "Version": 327704,
                "Size": 0,
                "Cmd": 1,
                "ColorFormat": 0,
                "Colorimetry": 0,
                "DynamicRange": 2,
                "Bpc": 0,
                "ColorSelectionPolicy": 0,
                "Depth": 0
              },

Now, that shouldn't matter, as the Colorimetery setting of RGB mode should work just as well as the mode of AUTO, as the AUTO mode should resolve to the RGB setting after autodetection, but it's possible that either the NVIDIA Driver, DP Switch or the Ultrawide screen itself that is interfering and setting the RGB setting.

Can you please tell me the manufacturer and model of your DP Switch? If you can send me a link to the manufacturers page for the DP Switch that would be even better. I will have a little dig into the specs to see if there is anything there that could be causing issues.

So what to do?
Well, there are a few things we can test here.

The first test I'd like you to do, is to bypass the DP Switch to see if that is casing issues:

• Disconnect your DP Switch from the PC
• Connect your Ultrawide directly to that now empty DP port on the video card
• Make a new dual screen display profile with only dual screens enabled.
• Make a new test ultrawide display profile with only the ultrawide enabled
• Test swapping between them and see if the problem is still there, or if it has gone away. If the problem has gone away then it is a DP Switch issue. If the problem is still there then the DP Switch is not the issue - it is a NVIDIA Driver or screen issue.

Once you've concluded that first test, then please do the second test below, which will see if we can manually tweak the config to see if we can make it work:

• Connect your Ultrawide back into the DP Switch and connect the DP switch to the PC again
• Close DisplayMagician
• Go to C:\Users<username>\AppData\Local\DisplayMagician\Profiles folder, and rename the DisplayProfiles_2.4.json to something else (do not delete it!).
• Download the Terry_DisplayProfiles_2.4.json file that I have modified below, and save it in the Profiles folder.
• Rename the Terry_DisplayProfiles_2.4.json file to DisplayProfiles_2.4.json
• Restart DisplayMagician, and then see if that works.

Terry_DisplayProfiles_2.4.zip

The tweak that I made to the Terry_DisplayProfiles_2.4.json file was to simply change the Colorimetery setting for the Ultrawide from RGB to AUTO, just in case that was the bit that was causing the Ultrawide to go into the wrong mode.

Let's see the results of your above testing, and then we'll go from there.

Thanks
Terry

[Globespy]

Thank you so much Terry! I will try out your suggestions, but I think your assessment is on the money, but I'm not convinced the DP switch is the problem as this never happened before when I used other NV Surround tools (far inferior to this amazing solution you have - donation will be coming!) to switch between the triples and the desk monitor. I will try your file first, before ruling out the Dp Switch - here's the switch I am using: Amazon.com: ELUTENG Displayport Switch 8K Bidirectional DP 1.4 Switch 8K @60Hz 4K @120hz Displayport Switcher 1 to 2 / 2 in 1 Out with LED Indicator for Monitor Projector TV PC Laptop and More : Electronics <https://www.amazon.com/gp/product/B08JQDMYMY/ref=ppx_yo_dt_b_search_asin_title?ie=UTF8&psc=1> Sean

…

On Sun, Sep 11, 2022 at 4:04 PM terrymacdonald ***@***.***> wrote: Oh interesting @Globespy <https://github.com/Globespy> - I don't think I've had anyone using the output color format before, so that's quite interesting in of itself. My gut feel is that either the DP Switch or NVIDIA Driver is impacting this in some way. DisplayMagician simply records the settings from the NVIDIA Driver, and then applies them again when they are needed. DisplayMagician definitely records the Color Format on your computer, as is shown from this snippet from your *NV Triples 144Hz* profile: "HdrColorData": { "Version": 131124, "Cmd": 0, "HdrMode": 2, "StaticMetadataDescriptorId": 0, "MasteringDisplayData": { "DisplayPrimaryX0": 33935, "DisplayPrimaryY0": 15820, "DisplayPrimaryX1": 13427, "DisplayPrimaryY1": 32128, "DisplayPrimaryX2": 7177, "DisplayPrimaryY2": 2783, "DisplayWhitePointX": 15673, "DisplayWhitePointY": 16455, "MaxDisplayMasteringLuminance": 518, "MinDisplayMasteringLuminance": 815, "MaxContentLightLevel": 518, "MaxFrameAverageLightLevel": 518 }, "HdrColorFormat": 0, "HdrDynamicRange": 0, "HdrBpc": 2 }, .... "ColorData": { "Version": 327704, "Size": 0, "Cmd": 1, "ColorFormat": 0, "Colorimetry": 2048, "DynamicRange": 2, "Bpc": 0, "ColorSelectionPolicy": 0, "Depth": 0 }, As you can see above, the HdrColorFormat is recorded as 0 (RGB), and the ColorFormat is recorded as 0 (RGB) and the Colorimetry value is 2048 (NV_COLOR_COLORIMETRY_AUTO). Note - we record both as different structures are used depending if the display is in HDR more or standard mode. Looking at your *Desktop Ultrawide* profile, I can see that NVHDR HDR isn't enabled for that monitor, so the normal color mode applies, and it uses the settings from the ColorData object shown below. As you can see, the object uses a ColorFormat of 0 (RGB), and a Colorimetry value of 0 (NV_COLOR_COLORIMETRY_RGB) "ColorData": { "Version": 327704, "Size": 0, "Cmd": 1, "ColorFormat": 0, "Colorimetry": 0, "DynamicRange": 2, "Bpc": 0, "ColorSelectionPolicy": 0, "Depth": 0 }, Now, that shouldn't matter, as the Colorimetery setting of RGB mode should work just as well as the mode of AUTO, as the AUTO mode should resolve to the RGB setting after autodetection, but it's possible that either the NVIDIA Driver, DP Switch or the Ultrawide screen itself that is interfering and setting the RGB setting. Can you please tell me the manufacturer and model of your DP Switch? If you can send me a link to the manufacturers page for the DP Switch that would be even better. I will have a little dig into the specs to see if there is anything there that could be causing issues. *So what to do?* Well, there are a few things we can test here. The first test I'd like you to do, is to bypass the DP Switch to see if that is casing issues: - Disconnect your DP Switch from the PC - Connect your Ultrawide directly to that now empty DP port on the video card - Make a new dual screen display profile with only dual screens enabled. - Make a new test ultrawide display profile with only the ultrawide enabled - Test swapping between them and see if the problem is still there, or if it has gone away. If the problem has gone away then it is a DP Switch issue. If the problem is still there then the DP Switch is not the issue - it is a NVIDIA Driver or screen issue. Once you've concluded that first test, then please do the second test below, which will see if we can manually tweak the config to see if we can make it work: - Connect your Ultrawide back into the DP Switch and connect the DP switch to the PC again - Close DisplayMagician - Go to C:\Users<username>\AppData\Local\DisplayMagician\Profiles folder, and rename the DisplayProfiles_2.4.json to something else (do not delete it!). - Download the Terry_DisplayProfiles_2.4.json file that I have modified below, and save it in the Profiles folder. - Rename the Terry_DisplayProfiles_2.4.json file to DisplayProfiles_2.4.json - Restart DisplayMagician, and then see if that works. Terry_DisplayProfiles_2.4.zip <https://github.com/terrymacdonald/DisplayMagician/files/9543619/Terry_DisplayProfiles_2.4.zip> The tweak that I made to the Terry_DisplayProfiles_2.4.json file was to simply change the Colorimetery setting for the Ultrawide from RGB to AUTO, just in case that was the bit that was causing the Ultrawide to go into the wrong mode. Let's see the results of your above testing, and then we'll go from there. Thanks Terry — Reply to this email directly, view it on GitHub <#146 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AB6LHTN2MJ26GK77JFZG3D3V5ZJNLANCNFSM6AAAAAAQJ5SCA4> . You are receiving this because you were mentioned.Message ID: ***@***.***>

-- *"Today I'm not what I think I am.* *I'm not what you think I am.I am what I think you think I am."*

[Globespy]

Hi Terry! Quick update - I went to option 2 first as discussed in my last email, renaming my file to '.old' and using your file renamed as instructed. Whatever you did in your file has resolved the issue, my desk ultrawide showing the correct output color (RGB, Full, 32-bit (Desktop Color Depth), 10bpc (Output Color Depth). Thank you!!!! Please keep up the good work, I don't know why this tool took me so long to find? There's so many hokey options out there that are incredibly temperamental, yet your solution is elegant and works every time. I will be spreading the word with everyone I know in iRacing that uses triples on their racing rig with an additional monitor on their desk. This really should be stickied in the iRacing forums as it will become a MUCH more essential tool given the RTX30 and upcoming RTX40 series Nvidia GPU's will have 3x DP and 2x HDMI 2.1 ports, which will be a problem for many coming from RTX20 series who have been using that USB-C virtual link which is essentially a powered DP port if you use a simple adapter. Until there are more monitors that have HDMI 2.1 ports (mostly 4K monitors that are still crazy overpriced), people like me will have issues without a tool like DisplayMagician. Thanks so much! Sean

…

On Mon, Sep 12, 2022 at 3:56 PM Globespy ***@***.***> wrote: Thank you so much Terry! I will try out your suggestions, but I think your assessment is on the money, but I'm not convinced the DP switch is the problem as this never happened before when I used other NV Surround tools (far inferior to this amazing solution you have - donation will be coming!) to switch between the triples and the desk monitor. I will try your file first, before ruling out the Dp Switch - here's the switch I am using: Amazon.com: ELUTENG Displayport Switch 8K Bidirectional DP 1.4 Switch 8K @60Hz 4K @120hz Displayport Switcher 1 to 2 / 2 in 1 Out with LED Indicator for Monitor Projector TV PC Laptop and More : Electronics <https://www.amazon.com/gp/product/B08JQDMYMY/ref=ppx_yo_dt_b_search_asin_title?ie=UTF8&psc=1> Sean On Sun, Sep 11, 2022 at 4:04 PM terrymacdonald ***@***.***> wrote: > Oh interesting @Globespy <https://github.com/Globespy> - I don't think > I've had anyone using the output color format before, so that's quite > interesting in of itself. > > My gut feel is that either the DP Switch or NVIDIA Driver is impacting > this in some way. DisplayMagician simply records the settings from the > NVIDIA Driver, and then applies them again when they are needed. > DisplayMagician definitely records the Color Format on your computer, as is > shown from this snippet from your *NV Triples 144Hz* profile: > > "HdrColorData": { > "Version": 131124, > "Cmd": 0, > "HdrMode": 2, > "StaticMetadataDescriptorId": 0, > "MasteringDisplayData": { > "DisplayPrimaryX0": 33935, > "DisplayPrimaryY0": 15820, > "DisplayPrimaryX1": 13427, > "DisplayPrimaryY1": 32128, > "DisplayPrimaryX2": 7177, > "DisplayPrimaryY2": 2783, > "DisplayWhitePointX": 15673, > "DisplayWhitePointY": 16455, > "MaxDisplayMasteringLuminance": 518, > "MinDisplayMasteringLuminance": 815, > "MaxContentLightLevel": 518, > "MaxFrameAverageLightLevel": 518 > }, > "HdrColorFormat": 0, > "HdrDynamicRange": 0, > "HdrBpc": 2 > }, > .... > "ColorData": { > "Version": 327704, > "Size": 0, > "Cmd": 1, > "ColorFormat": 0, > "Colorimetry": 2048, > "DynamicRange": 2, > "Bpc": 0, > "ColorSelectionPolicy": 0, > "Depth": 0 > }, > > As you can see above, the HdrColorFormat is recorded as 0 (RGB), and the > ColorFormat is recorded as 0 (RGB) and the Colorimetry value is 2048 > (NV_COLOR_COLORIMETRY_AUTO). Note - we record both as different structures > are used depending if the display is in HDR more or standard mode. > > Looking at your *Desktop Ultrawide* profile, I can see that NVHDR HDR > isn't enabled for that monitor, so the normal color mode applies, and it > uses the settings from the ColorData object shown below. As you can see, > the object uses a ColorFormat of 0 (RGB), and a Colorimetry value of 0 > (NV_COLOR_COLORIMETRY_RGB) > > "ColorData": { > "Version": 327704, > "Size": 0, > "Cmd": 1, > "ColorFormat": 0, > "Colorimetry": 0, > "DynamicRange": 2, > "Bpc": 0, > "ColorSelectionPolicy": 0, > "Depth": 0 > }, > > Now, that shouldn't matter, as the Colorimetery setting of RGB mode > should work just as well as the mode of AUTO, as the AUTO mode should > resolve to the RGB setting after autodetection, but it's possible that > either the NVIDIA Driver, DP Switch or the Ultrawide screen itself that is > interfering and setting the RGB setting. > > Can you please tell me the manufacturer and model of your DP Switch? If > you can send me a link to the manufacturers page for the DP Switch that > would be even better. I will have a little dig into the specs to see if > there is anything there that could be causing issues. > > *So what to do?* > Well, there are a few things we can test here. > > The first test I'd like you to do, is to bypass the DP Switch to see if > that is casing issues: > > - Disconnect your DP Switch from the PC > - Connect your Ultrawide directly to that now empty DP port on the > video card > - Make a new dual screen display profile with only dual screens > enabled. > - Make a new test ultrawide display profile with only the ultrawide > enabled > - Test swapping between them and see if the problem is still there, > or if it has gone away. If the problem has gone away then it is a DP Switch > issue. If the problem is still there then the DP Switch is not the issue - > it is a NVIDIA Driver or screen issue. > > Once you've concluded that first test, then please do the second test > below, which will see if we can manually tweak the config to see if we can > make it work: > > - Connect your Ultrawide back into the DP Switch and connect the DP > switch to the PC again > - Close DisplayMagician > - Go to C:\Users<username>\AppData\Local\DisplayMagician\Profiles > folder, and rename the DisplayProfiles_2.4.json to something else (do not > delete it!). > - Download the Terry_DisplayProfiles_2.4.json file that I have > modified below, and save it in the Profiles folder. > - Rename the Terry_DisplayProfiles_2.4.json file to > DisplayProfiles_2.4.json > - Restart DisplayMagician, and then see if that works. > > Terry_DisplayProfiles_2.4.zip > <https://github.com/terrymacdonald/DisplayMagician/files/9543619/Terry_DisplayProfiles_2.4.zip> > > The tweak that I made to the Terry_DisplayProfiles_2.4.json file was to > simply change the Colorimetery setting for the Ultrawide from RGB to AUTO, > just in case that was the bit that was causing the Ultrawide to go into the > wrong mode. > > Let's see the results of your above testing, and then we'll go from there. > > Thanks > Terry > > — > Reply to this email directly, view it on GitHub > <#146 (comment)>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AB6LHTN2MJ26GK77JFZG3D3V5ZJNLANCNFSM6AAAAAAQJ5SCA4> > . > You are receiving this because you were mentioned.Message ID: > ***@***.***> > -- *"Today I'm not what I think I am.* *I'm not what you think I am.I am what I think you think I am."*

-- *"Today I'm not what I think I am.* *I'm not what you think I am.I am what I think you think I am."*

[terrymacdonald]

@Globespy After seeing the results of your testing, I believe that either one of three things is happening:

• The NVIDIA driver is getting the RGB colorimetry setting from the Ultrawide itself when it is querying it, instead of getting the AUTO colorimetry setting.
• The NVIDIA driver is getting the RGB colorimetry setting from the DP Switch components when it is querying for it, instead of getting the AUTO colorimetry setting.
• The NVIDIA driver is detecting the incorrect RGB colorimetry setting on its own instead of assuming the AUTO colorimetry setting.

Performing that DP Switch removal test would eliminate option #2 from the list above, but there is no real way to test Option#1 or #3.... in any case it's not a DisplayMagician error. There's basically nothing I can do to avoid this issue for you - it's definitely a workaround. I'll mark this issue as 'cantfix' and 'workaround' so others know there is something we can do about it.

For your future reference, The change I made was to change 'Colorimetry' option from 0 to 2048, which changes it from RGB to AUTO. If you strike this issue again, just go into the DisplayProfiles_2.4.json file and search for the profile you want to edit, and perform the step I described above. It should all work fine from there.

You might be interested to know that I'll be releasing v2.5 in a little while, which adds a built in FOV calc (thanks to Markus Ewert!) and adds in the ability to run Apps and Games installed via MS Store! That should hopefully be ready within the next month... I just have a bit more testing to do.

Actually would you be interested in testing DisplayMagician v2.5?

And please do spread the word! I sent a post to Boosted Media to get Will to do a piece on DisplayMagician but he's a bit busy ATM, so I was going to reach out to GamerMuscle to see if he'd be interested.

I'll close this issue for now, so that I can concentrate on the other issues that need fixing.

Thanks for the kind words!
Terry

[Globespy]

Thanks for the feedback and great explanation. If it works I'm happy, worst case is to restart my PC after using triples as that always resolves.
You should also try DaveCam and absolutely Dan Suzuki/Matt Malone - I like him these guys a lot, never been a fan of GamerMuscle constant bashing of iRacing as a core part of his shtick (and his 'tea'), but we can't all like the same things so I just don't watch his channel. :)
I'd be happy to test.
Thanks again for such an amazing app. Truly.

[Globespy]

Hi Terry,
The problem returned and after a bit of research, seems to have been an issue for others in identical/almost identical situations.
Pretty sure the problem is caused by Windows and/or the disappearance of actual monitor specific drivers from the many different manufacturers out there, in favor of these 'Generic Monitor' drivers provided by Microsoft.

The problem mostly occurs as I've found in the exact same conditions as mine - when the monitor goes to sleep/PC goes to sleep/hibernate and then is brought back out of that low power mode, that is when the NVCP resolution changes from what should be RGB/8 or 10bpc/Full to YCbCr422/limited.
Like others I have tried to change cables, and I also tried bypassing the DP Switch as you suggested, but didn't resolve.
I think it's a Windows problem that seemed to show up for people towards the tail end of Win 10 updates where a reliable solution for many seems to be to simply power off the monitor after closing the NVCP to tray (using the monitor controls is fine, no need to yank cables) for 10 seconds and then switching back on. This works for me 100%, but of course it's not ideal.
Some have resolved by installing manufacturer drivers that may be specific to that monitor model, however it seems many drivers are 'catch-all' for so many different models that company might produce, then a 'Generic' version is sent to Microsoft for WHQL signing and that's the problem. This may be impacted further if the user (as in my case) happens to have multiple different models of monitors by the same manufacturer (Gigabyte for me).

Here's a few examples that I'm hoping might give you some ideas on how this may be resolve in Magician?:
https://www.tenforums.com/graphic-cards/167180-nvidia-control-panel-output-color-format-changes-itself.html
https://answers.microsoft.com/en-us/windows/forum/all/windows-10-washed-out-color-after-waking-from/8cc89b60-8ba2-4e88-bb07-eacbcc546530
https://linustechtips.com/topic/1053623-color-format-change-itself-to-ycbcr422-with-8-bit-everytime-i-restart-the-pc/
https://www.nvidia.com/en-us/geforce/forums/discover/279477/-bug-driver-keeps-changing-colour-output-to-ycbcr422-without-the-ability-to-change-to-rgb/ - DDU'ing the driver doesn't work, but interesting how far this goes back.
https://www.monitortests.com/forum/Thread-OC-monitor-stuck-on-YCbCr422-and-wont-go-to-RGB
https://www.reddit.com/r/Windows10/comments/g2ib4k/kb4549951_causing_limited_frame_rate_120hz_and/

Just hoping any of this catches your attention and perhaps you might be able to resolve what's going on? Since less and less manufacturers are providing their own drivers, this situation might get much worse especially for those owning multiple monitors by the same manufacturer, but perhaps different models/resolutions?

[terrymacdonald]

@Globespy this is an awesome amount of information you've found. This will really help me understand the issue better. Unfortunately I highly doubt I'll be able to get DisplayMagician to have an effect. The reason is that DisplayMagician only sees what the CCD driver reports to it, meaning that if there is an issue with what the driver thinks to then that same issue will be seen by DisplayMagician. I think the best bet would be to report this exact same information to Microsoft itself to see if it can get on the display driver development teams issue list some how. You've got such a good list of resources and complaints that it should help them get a good headstart on fixing the problem. I've not discovered a good place to log a ticket with the Microsoft dev teams yet, so if you find the best place to do so then please report back here so I know where to log errors in the future. Thanks Terry

…

On Wed, 21 Sep 2022, 04:16 Globespy, ***@***.***> wrote: Hi Terry, The problem returned and after a bit of research, seems to have been an issue for others in identical/almost identical situations. Pretty sure the problem is caused by Windows and/or the disappearance of actual monitor specific drivers from the many different manufacturers out there, in favor of these 'Generic Monitor' drivers provided by Microsoft. The problem mostly occurs as I've found in the exact same conditions as mine - when the monitor goes to sleep/PC goes to sleep/hibernate and then is brought back out of that low power mode, that is when the NVCP resolution changes from what should be RGB/8 or 10bpc/Full to YCbCr422/limited. Like others I have tried to change cables, and I also tried bypassing the DP Switch as you suggested, but didn't resolve. I think it's a Windows problem that seemed to show up for people towards the tail end of Win 10 updates where a reliable solution for many seems to be to simply power off the monitor after closing the NVCP to tray (using the monitor controls is fine, no need to yank cables) for 10 seconds and then switching back on. This works for me 100%, but of course it's not ideal. Some have resolved by installing manufacturer drivers that may be specific to that monitor model, however it seems many drivers are 'catch-all' for so many different models that company might produce, then a 'Generic' version is sent to Microsoft for WHQL signing and that's the problem. This may be impacted further if the user (as in my case) happens to have multiple different models of monitors by the same manufacturer (Gigabyte for me). Here's a few examples that I'm hoping might give you some ideas on how this may be resolve in Magician?: https://www.tenforums.com/graphic-cards/167180-nvidia-control-panel-output-color-format-changes-itself.html https://answers.microsoft.com/en-us/windows/forum/all/windows-10-washed-out-color-after-waking-from/8cc89b60-8ba2-4e88-bb07-eacbcc546530 https://linustechtips.com/topic/1053623-color-format-change-itself-to-ycbcr422-with-8-bit-everytime-i-restart-the-pc/ https://www.nvidia.com/en-us/geforce/forums/discover/279477/-bug-driver-keeps-changing-colour-output-to-ycbcr422-without-the-ability-to-change-to-rgb/ - DDU'ing the driver doesn't work, but interesting how far this goes back. https://www.monitortests.com/forum/Thread-OC-monitor-stuck-on-YCbCr422-and-wont-go-to-RGB https://www.reddit.com/r/Windows10/comments/g2ib4k/kb4549951_causing_limited_frame_rate_120hz_and/ Just hoping any of this catches your attention and perhaps you might be able to resolve what's going on? Since less and less manufacturers are providing their own drivers, this situation might get much worse especially for those owning multiple monitors by the same manufacturer, but perhaps different models/resolutions? — Reply to this email directly, view it on GitHub <#146 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABLU5LASNOXBLMMUTM4DUM3V7HPMLANCNFSM6AAAAAAQJ5SCA4> . You are receiving this because you modified the open/close state.Message ID: ***@***.***>

[Globespy]

So you do not think this could be caused by the Nvidia driver itself, but you agree that it's much more likely that it's the generic drivers Microsoft supplies?
I do have an update of sorts - Gigabyte did release drivers for the monitors I use, and I was hopeful that when updating them in device manager that this would resolve the issue.
Sadly, it did not which now makes this situation much more complex.

I did find a 'hackaround' solution to this in the interim, which is to simply use your monitor's built-in menu system to turn the monitor off, then wait about 10 seconds and power it back on. The NVCP must be closed during this process, or it won't work, which adds further complexity to what is going on, at least in my very limited understanding of how this all works.
It's a mess really!

[terrymacdonald]

Hi @Globespy, In truth I don't know. It probably is more likely that it is the NVIDIA driver if everyone who has the problem is experiencing issues has the same monitor and an NVIDIA video card, but we won't really know. We would have to be able to inspect the NVIDIA driver as it was doing it's work, but I have absolutely no idea how to do that, and even if it can be done. So we're kinda stuck with the work around you've found I'm afraid. Thanks *Terry *

[Globespy]

Thanks anyway Terry, hopefully a future update to Win 11/Nvidia driver will resolve.
One last piece of info that I'm not sure is relevant, but something I noticed in device manager when I was poking around.

Despite the Gigabyte driver being loaded, I still had this same Event in all of my monitors.
Here's the one for the ultrawide (pretty much the same for the triples):

"Device settings for DISPLAY\GBT3400\5&2bdb4a25&b&UID57606 were not migrated from previous OS installation due to partial or ambiguous device match.

Last Device Instance Id: DISPLAY\GBT3400\5&2bdb4a25&7&UID0
Class Guid: {4d36e96e-e325-11ce-bfc1-08002be10318}
Location Path:
Migration Rank: 0xF00000000000F120
Present: false
Status: 0xC0000719"

Just thought I'd add this just in case it was at all relevant to you.
Thanks again for this awesome software - I sent you a donation the other day.
Cheers!

[terrymacdonald]

Hmmmm not seen that message before. Which service created the event log message? Was it a windows service? What classification was the event log? Was it an Error or just informational? It's hard to say what that means. I know that windows tries to match the display layout to previously detected layouts, so it could simply be that windows tried doing so and couldn't match it. It's good info to have anyway as it may help in the future of someone else experiences something similar. Thank you so much for the donation! It's really lovely to think that over now had over 10000 downloads, and that some kind people such as yourself decided to donate to me. It really does help, as it goes towards my simracing hobby, meaning I buy games in different game libraries and test that they work with DisplayMagician. Thanks Terry

…

On Fri, 23 Sep 2022, 05:06 Globespy, ***@***.***> wrote: Thanks anyway Terry, hopefully a future update to Win 11/Nvidia driver will resolve. One last piece of info that I'm not sure is relevant, but something I noticed in device manager when I was poking around. Despite the Gigabyte driver being loaded, I still had this same Event in all of my monitors. Here's the one for the ultrawide (pretty much the same for the triples): "Device settings for DISPLAY\GBT3400\5&2bdb4a25&b&UID57606 were not migrated from previous OS installation due to partial or ambiguous device match. Last Device Instance Id: DISPLAY\GBT3400\5&2bdb4a25&7&UID0 Class Guid: {4d36e96e-e325-11ce-bfc1-08002be10318} Location Path: Migration Rank: 0xF00000000000F120 Present: false Status: 0xC0000719" Just thought I'd add this just in case it was at all relevant to you. Thanks again for this awesome software - I sent you a donation the other day. Cheers! — Reply to this email directly, view it on GitHub <#146 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABLU5LHO2LCPBMFHLPIIIFTV7SGZRANCNFSM6AAAAAAQJ5SCA4> . You are receiving this because you modified the open/close state.Message ID: ***@***.***>

[Globespy]

This is a very common event that can be seen in the device properties within Device Manager, and you can click the 'List' to see the same in Event Viewer. I wonder if this is perhaps the cause? Maybe time for a fresh install of WIn 11 since this was an upgrade from Win 10 - I thought I had done a clean installation, but I figured I would try the upgrade as it's apparently gotten much better. I'll keep a Macrium image just in case the same issue persists with a fresh installation/wipe of the NVME