[GH-ISSUE #288] Brightness function not working for MX279 monitor #227

Closed
opened 2026-05-05 05:27:43 -06:00 by gitea-mirror · 2 comments
Owner

Originally created by @marfier on GitHub (Sep 16, 2020).
Original GitHub issue: https://github.com/MonitorControl/MonitorControl/issues/288

Checklist

Describe the issue
The volume functions works, but not the brightness function.

Expected behavior
For the brightness function to work.

Additional context
As per the Monitor Troubleshooting guide, I used ddcctl and ran ./ddcctl -d 1 -b 30, but I had no luck.

Environment Information (please complete the following information):

  • macOS version: 10.15.6
  • MonitorControl version: 2.0.0
  • Monitor(s): MX279
  • Mac model: MacBook Air 2020
  • Monitor Cable(s)/Connection(s): (e.g. DisplayPort) HDMI
Originally created by @marfier on GitHub (Sep 16, 2020). Original GitHub issue: https://github.com/MonitorControl/MonitorControl/issues/288 **Checklist** <!-- Before you submit your issue, please make sure to check the following boxes by putting an x in the [ ] (don't: [x ], [ x], do: [x]) --> - [x] I have searched for existing issues - [x] I have looked through [the Monitor Troubleshooting wiki](https://github.com/MonitorControl/MonitorControl/wiki/Monitor-Troubleshooting) - [x] I have updated MonitorControl to the latest version **Describe the issue** The volume functions works, but not the brightness function. **Expected behavior** For the brightness function to work. <!-- **Screenshots** If applicable, add screenshots to help explain your problem. --> **Additional context** As per the Monitor Troubleshooting guide, I used `ddcctl` and ran `./ddcctl -d 1 -b 30`, but I had no luck. **Environment Information (please complete the following information):** - macOS version: 10.15.6 - MonitorControl version: 2.0.0 - Monitor(s): MX279 - Mac model: MacBook Air 2020 - Monitor Cable(s)/Connection(s): (e.g. DisplayPort) HDMI
gitea-mirror 2026-05-05 05:27:43 -06:00
Author
Owner

@JoniVR commented on GitHub (Sep 19, 2020):

If it doesn't work with ddcctl either then I'm afraid it's probably simply bad implementation of the VESA spec..? Did you try the different cables etc? (probably won't do much if volume already works but worth a shot).

<!-- gh-comment-id:695205083 --> @JoniVR commented on GitHub (Sep 19, 2020): If it doesn't work with ddcctl either then I'm afraid it's probably simply bad implementation of the VESA spec..? Did you try the different cables etc? (probably won't do much if volume already works but worth a shot).
Author
Owner

@marfier commented on GitHub (Sep 22, 2020):

I fixed this issue by resetting my integrated monitor config on the OSD. It turns out my monitor does support DDC, but there was an issue with the config. Thank you for such a great software!

<!-- gh-comment-id:696605656 --> @marfier commented on GitHub (Sep 22, 2020): I fixed this issue by resetting my integrated monitor config on the OSD. It turns out my monitor does support DDC, but there was an issue with the config. Thank you for such a great software!
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/MonitorControl#227
No description provided.