Processing Ajax...

Title

Message

Confirm

Confirm

Confirm

Confirm

Are you sure you want to delete this item?

Confirm

Are you sure you want to delete this item?

Confirm

Are you sure?

User Image
Terrence Jones
2 discussion posts
I have a situation where monitor profiles are not behaving as expected.

I have four displays, two over DisplayPort, two via USB-C (DP-Alt). The displays don't seem to be enumerated consistently, and thus Windows orders them differently on boot vs resume from standby etc. That is, the Identity Numbers displayed in DisplayFusion change.

To make matters worse, the two DP-Alt displays are cheap panels that report identical EDID info (serial number, etc.) I used the CRU (ToastyX, Custom Resolution Utility) to give them unique Device ID, Name, Serial Numbers. See below for how these displays are currently identified by MonitorInfoView.

DisplayFusion still does not reliably recognize these displays after resuming from standby or manually connecting/disconnecting the cables; applying a profile often causes one of the displays to be marked as disabled. See below for how DisplayFusion "sees" these displays per a profile export. I see that DisplayFusion did not recognize the modified serial number, but does see the unique custom MakeModel.

I have tried saving profiles with the "Monitor ID Detection Mode Override" both in its default (empty) state and with the value of "1".

MultiMonitorTool, with its "Use Serial Number in Load Config" setting, does correctly manage these displays.

Is there a way to have DisplayFusion support my scenario? Specifically, it seems that identifying the displays via MakeModel and SerialNumber would be ideal while ignoring device paths, etc.

Thanks

MonitorInfoView
---------------
Display A
Name : \\.\DISPLAY48
Device ID : PCI\VEN_8086&DEV_46A6&SUBSYS_89C0103C&REV_0C
Device Key : \Registry\Machine\System\CurrentControlSet\Control\Video\{E591323B-A5E7-11EF-A52A-E073E72BE9F2}\0002
Monitor ID : MONITOR\NPD0B04\{4d36e96e-e325-11ce-bfc1-08002be10318}\0035
Short Monitor ID : NPD0B04
Monitor Key : \Registry\Machine\System\CurrentControlSet\Control\Class\{4d36e96e-e325-11ce-bfc1-08002be10318}\0035
Monitor Name : N3-A
Monitor Serial Number: N3 20241104A

Display B
Name : \\.\DISPLAY49
Device ID : PCI\VEN_8086&DEV_46A6&SUBSYS_89C0103C&REV_0C
Device Key : \Registry\Machine\System\CurrentControlSet\Control\Video\{E591323B-A5E7-11EF-A52A-E073E72BE9F2}\0003
Monitor ID : MONITOR\NPD0B04\{4d36e96e-e325-11ce-bfc1-08002be10318}\0034
Short Monitor ID : NPD0B04
Monitor Key : \Registry\Machine\System\CurrentControlSet\Control\Class\{4d36e96e-e325-11ce-bfc1-08002be10318}\0034
Monitor Name : N3-B
Monitor Serial Number: N3 20241104B

"Monitor0_Json"="{\"UniqueID\":{\"DeviceId\":1,\"MakeModel\":\"DELL U2722D\",\"SerialNumber\":\"1095848012\",\"ManufactureCode\":\"DEL\",\"ManufactureProductCode\":\"16941\",\"ManufactureYear\":2021,\"ManufactureWeek\":46,\"DisplaySizeInches\":27.0,\"FallbackDevicePath\":\"\\\\\\\\?\\\\DISPLAY#DEL422D#4&20320f8f&0&UID8261#{e6f07b5f-ee97-4a90-b076-33f57bf4eaa7}\"},\"MakeModel\":\"DELL U2722D\",\"DeviceIdRaw\":1,\"IsAttached\":true,\"BoundsX\":0,\"BoundsY\":0,\"BoundsWidth\":2560,\"BoundsHeight\":1440,\"RefreshRateNum\":24150000,\"RefreshRateDen\":402832,\"RefreshRateInterlaced\":false,\"Orientation\":0,\"DisplayConfigScaling\":1,\"MonitorAddSource\":2,\"DpiScalingPercent\":100,\"Splits\":[]}"
"Monitor1_Json"="{\"UniqueID\":{\"DeviceId\":2,\"MakeModel\":\"DELL U2722D\",\"SerialNumber\":\"1095782476\",\"ManufactureCode\":\"DEL\",\"ManufactureProductCode\":\"16941\",\"ManufactureYear\":2021,\"ManufactureWeek\":46,\"DisplaySizeInches\":27.0,\"FallbackDevicePath\":\"\\\\\\\\?\\\\DISPLAY#DEL422D#4&20320f8f&0&UID12613#{e6f07b5f-ee97-4a90-b076-33f57bf4eaa7}\"},\"MakeModel\":\"DELL U2722D\",\"DeviceIdRaw\":2,\"IsAttached\":true,\"BoundsX\":-2560,\"BoundsY\":0,\"BoundsWidth\":2560,\"BoundsHeight\":1440,\"RefreshRateNum\":24150000,\"RefreshRateDen\":402832,\"RefreshRateInterlaced\":false,\"Orientation\":0,\"DisplayConfigScaling\":1,\"MonitorAddSource\":2,\"DpiScalingPercent\":100,\"Splits\":[]}"
"Monitor2_Json"="{\"UniqueID\":{\"DeviceId\":3,\"MakeModel\":\"N3-A\",\"SerialNumber\":\"539234564\",\"ManufactureCode\":\"NPD\",\"ManufactureProductCode\":\"2820\",\"ManufactureYear\":2024,\"ManufactureWeek\":45,\"DisplaySizeInches\":16.0,\"FallbackDevicePath\":\"\\\\\\\\?\\\\DISPLAY#NPD0B04#4&20320f8f&0&UID16965#{e6f07b5f-ee97-4a90-b076-33f57bf4eaa7}\"},\"MakeModel\":\"N3-A\",\"DeviceIdRaw\":3,\"IsAttached\":true,\"BoundsX\":91,\"BoundsY\":1440,\"BoundsWidth\":1200,\"BoundsHeight\":1920,\"RefreshRateNum\":16747000,\"RefreshRateDen\":279110,\"RefreshRateInterlaced\":false,\"Orientation\":3,\"DisplayConfigScaling\":1,\"MonitorAddSource\":2,\"DpiScalingPercent\":125,\"Splits\":[]}"
"Monitor3_Json"="{\"UniqueID\":{\"DeviceId\":4,\"MakeModel\":\"N3-B\",\"SerialNumber\":\"539234564\",\"ManufactureCode\":\"NPD\",\"ManufactureProductCode\":\"2820\",\"ManufactureYear\":2024,\"ManufactureWeek\":45,\"DisplaySizeInches\":16.0,\"FallbackDevicePath\":\"\\\\\\\\?\\\\DISPLAY#NPD0B04#4&20320f8f&0&UID24646#{e6f07b5f-ee97-4a90-b076-33f57bf4eaa7}\"},\"MakeModel\":\"N3-B\",\"DeviceIdRaw\":4,\"IsAttached\":true,\"BoundsX\":1291,\"BoundsY\":1440,\"BoundsWidth\":1200,\"BoundsHeight\":1920,\"RefreshRateNum\":16747000,\"RefreshRateDen\":279110,\"RefreshRateInterlaced\":false,\"Orientation\":1,\"DisplayConfigScaling\":1,\"MonitorAddSource\":2,\"DpiScalingPercent\":125,\"Splits\":[]}"
19 days ago  • #1
Owen Muhlethaler (BFS)'s profile on WallpaperFusion.com
This isn't something we currently support, but we have a feature request open to detect the monitors based on the device path rather then the ID, which would probably fix this up. I've added your vote to it, we'll let you know if it's something we add in the future.

thanks!
18 days ago  • #2
User Image
Terrence Jones
2 discussion posts
Thanks for the update...

I've come to learn that this a common problem with cheap displays. I'm sure an ability by DisplayFusion to handle the situation would benefit many.

In addition to the display profiles having trouble, taskbar settings are unreliable.

I was able to work around my profile problem using a PowerShell script devloped around MultiMonitorTool API.

Thanks
17 days ago  • #3
Subscribe to this discussion topic using RSS
Was this helpful?  Login to Vote(-)  Login to Vote(-)