[GH-ISSUE #1528] Brightness Controls Update Same Monitor #857

Closed
opened 2026-05-05 06:46:52 -06:00 by gitea-mirror · 1 comment
Owner

Originally created by @troywein on GitHub (Mar 10, 2024).
Original GitHub issue: https://github.com/MonitorControl/MonitorControl/issues/1528

Before opening the issue, have you...?

  • Searched for existing issues
  • Looked through the wiki
  • Updated MonitorControl to the latest version (if applicable)

Describe the bug

The application correctly recognized both attached LG displays but both the brightness controls update the same display.

Steps to reproduce

!. change brightness on both monitors....only one display is updated.

Expected behavior

I would assume that the controls for each monitor would update that respective monitor.

Anything else?

No response

Environment Information (please complete the following information)

- macOS version: 14.4
- Mac model: MacBook Pro M1 Max - Clamshell Mode
- MonitorControl version: 4.2.0
- Monitor(s): 2x LG Ultrafine
- Apple Silicon/M1 (yes or no): Yes
Originally created by @troywein on GitHub (Mar 10, 2024). Original GitHub issue: https://github.com/MonitorControl/MonitorControl/issues/1528 ### Before opening the issue, have you...? - [X] Searched for existing issues - [X] Looked through [the wiki](https://github.com/MonitorControl/MonitorControl/wiki) - [X] Updated MonitorControl to the latest version (if applicable) ### Describe the bug The application correctly recognized both attached LG displays but both the brightness controls update the same display. ### Steps to reproduce !. change brightness on both monitors....only one display is updated. ### Expected behavior I would assume that the controls for each monitor would update that respective monitor. ### Anything else? _No response_ ### Environment Information (please complete the following information) ```markdown - macOS version: 14.4 - Mac model: MacBook Pro M1 Max - Clamshell Mode - MonitorControl version: 4.2.0 - Monitor(s): 2x LG Ultrafine - Apple Silicon/M1 (yes or no): Yes ```
Author
Owner

@waydabber commented on GitHub (Oct 3, 2024):

This might be an issue related to display identification. This is a complex issue and won't address it in MonitorControl 4. Recommend switching to BetterDisplay where a number of display identification methods are available to configure which might help with multiple identical display issues.

<!-- gh-comment-id:2391443633 --> @waydabber commented on GitHub (Oct 3, 2024): This might be an issue related to display identification. This is a complex issue and won't address it in MonitorControl 4. Recommend switching to BetterDisplay where a number of display identification methods are available to configure which might help with multiple identical display issues.
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#857
No description provided.