Asus ProArt Display PA348CGV - not detected (but work with other software)

[olegolegoleg]

Hi! The Asus ProArt Display PA348CGV monitor is not detected:

But I am able to change brigtness via ScreenBright app (it is also using DDC/CI):

Also DDC/CI is enabled for sure:

Interesting, that after reinstall or update of the nVidia dirver (my GPU is GT 1030) Monitorian detects monitor correctly 1 time and allow to change brigtness.

I've genereted and added probe.log: probe.log

[emoacht]

Thanka for the log. The probe.log indicates that your monitor did not report its capabulities at all but getting/setting brightness was successful. For such weird monitor, preclear option can be used. https://github.com/emoacht/Monitorian/issues/270#issuecomment-998347584

[olegolegoleg]

Hi @emoacht, thanks you very much! Now all works with "/preclear + DeviceInstanceId" argument. The probe.log contains DeviceInstanceId in 2 formats (lower and upper case and only upper case letters):

• DISPLAY\\AUS342E\\5&27a40ad2&0&UID184576
• DISPLAY\\AUS342E\\5&27A40AD2&0&UID184576

In my case only first (lower+upper) works – DISPLAY\\AUS342E\\5&27a40ad2&0&UID184576

The compleate target in the shortcut: "C:\Program Files (x86)\Monitorian\Monitorian.exe" /preclear "DISPLAY\\AUS342E\\5&27a40ad2&0&UID184576"

Thanks again, really nice app! Feel free to close the ticket

[emoacht]

Yes, the ID is case-sensitive. It is because the device instance ID obtained by Device Context method is used internally to compare IDs and case-insensitive comparison requires a bit more cost than case-sensitive one. But perhaps the difference is neglisible. I will consider it.

[ryankhart]

I seem to have the same issue with my Asus monitor. It's an Asus PB278. probe.log operation.log

However, I was able to work around the issue and get it resolved, at least temporarily, by using the instructions found here.

[emoacht]

Changed 97766cca7a10f3493a8b38937b28aa111654ca89