-
Notifications
You must be signed in to change notification settings - Fork 164
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Contrast option not working properly with DisplayPort #600
Comments
Could you read Contributing Guidelines and post probe.log? How to produce the log is explained in Reporting section of readme. |
With both HDMI and DP at the same time, for HDMI I can change contrast, it's also marked as "true" on the log, not with DP. But sometimes with DP when removing HDMI somehow detects contrast. Still when I reboot pc or monitor, 90% of the time contrast setting is lost. |
Thank you for the log. |
Hey! Thanks for your help, still doesn't work, I executed monitorian /preclear "(the id)" on the CMD. It seems it did something since it opened monitorian when executed, but still couldn't change the contrast. I tried executing it from the hidden menu aswell. But I couldn't find a way to execute that prompt. Wrote the prompt but tried different buttons to execute and it didn't seem to do anything. Is there another way to make monitorian think it has enabled contrast? And hopefully the contrast bar works. Also, does it make any sense for u that when I connect HDMI and then go back to DP sometimes the contrast setting stays fixed? Sorry for bothering and thanks for replying that fast EDIT: Sorry I didn't realise I'm on another account 😅🙏🏼, I'm the same person |
If you run this app with |
When connecting the monitor via DisplayPort, the brightness works, but contrast doesn't.
If I switch to HDMI then DisplayPort again, it fixes sometimes.
Also, if I turn the monitor off then on, first it may bug and not let u control anything (that's normal ig), after some seconds or another off/on it works for brightness, but contrast fails more times.
The text was updated successfully, but these errors were encountered: