"Sync brightness from Built-in and Apple displays" stops working after sleep · Issue #922 · MonitorControl/MonitorControl · GitHub
Skip to content

"Sync brightness from Built-in and Apple displays" stops working after sleep #922

Closed
Closed
"Sync brightness from Built-in and Apple displays" stops working after sleep#922
Labels
bugIssue is a bug (e.g. Crash, …)

Description

@patrickrushton
patrickrushton
opened on Jan 30, 2022

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

Syncing brightness from my MacBook Pro 2019 to my Dell display with hardware DDC works fine... until my Mac sleeps. After a sleep cycle, the brightness changes caused by the Ambient light sensor are no longer synced to the external display.

I have verified MonitorControl is still running in Activity Monitor, and brightness changes made by the keyboard shortcuts in MonitorControl are applied successfully to the external display.

If I quick and relaunch MonitorControl, then syncing will resume until the next sleep cycle.

Steps to reproduce

  1. Launch MonitorControl with Sync brightness changes enabled.
  2. Put the Mac to sleep
  3. Cover the light sensor on the Macbook or change the built-in display brightness in System Preferences

Expected behavior

Brightness on both on the displays should adjust. Instead, only the built-in display brightness changes while the external display brightness remains constant.

Anything else?

image
image
image

Environment Information (please complete the following information)

- macOS version: 12.1
- Mac model: MacBook Pro (16-inch, 2019)
- MonitorControl version: 4.0.2
- Monitor(s): DELL U2713HM
- Apple Silicon/M1 (yes or no): no

Activity

  1. waydabber commented on Feb 1, 2022

    @waydabber
    waydabber
    on Feb 1, 2022
    Member

    Do you have this issue only with ambient light sensor? If you change the brightness using the built-in (macOS native) brightness slider, what happens?

  2. waydabber
    added
    investigatingWe're looking into this issue
    on Feb 1, 2022

  3. patrickrushton commented on Feb 1, 2022

    @patrickrushton
    patrickrushton
    on Feb 1, 2022
    Author

    Hi, yes as mentioned in step 3 syncing to the external display also stops working when I change the built-in display brightness in System Preferences. The built-in display brightness changes, but the external display doesn't change. I can still use the brightness keys to adjust the external display, but syncing breaks.

  4. waydabber
    added
    bugIssue is a bug (e.g. Crash, …)
    and removed
    investigatingWe're looking into this issue
    on Feb 1, 2022

  5. waydabber commented on Feb 1, 2022

    @waydabber
    waydabber
    on Feb 1, 2022
    Member

    All right. We'll look into this, thanks for the report!

  6. patrickrushton commented on Feb 8, 2022

    @patrickrushton
    patrickrushton
    on Feb 8, 2022
    Author

    To clarify this issue. I've noticed that it's not necessary for the Macbook to fully go to sleep in order for syncing to break.

    If I have an application running that prevents sleep (or when Music.app is playing) the displays will turn off after the period of inactivity specified in System Preferences.

    When the displays wake up again, brightness syncing will be broken until I quit and restart MonitorControl.

  7. michaelbonert commented on Feb 8, 2022

    @michaelbonert
    michaelbonert
    on Feb 8, 2022

    Hi, I just want to add, that I have the same issue under this conditions:

    - macOS version: 12.1
- Mac model: iMac (27-inch, 2020)
- MonitorControl version: 4.0.2
- Monitor(s): DELL P2720DC
- Apple Silicon/M1 (yes or no): no

    I noticed additionaly that after sleep the brightness sliders in den menu didn't react, if brightness is changed automatically by the built-in sensor. They react only if brightness is changed by keys or by the sliders itself.

  8. leoskyrocker commented on Mar 24, 2022

    @leoskyrocker
    leoskyrocker
    on Mar 24, 2022
    - macOS version: 12.3
- Mac model: Macbook Pro (2019)
- MonitorControl version: 4.0.2
- Monitor(s): HP 24es
- Apple Silicon/M1 (yes or no): no

    Not sure if it's the same issue, but I noticed that some of the folks above are getting different behaviors than mine, but essentially they all experience some sort of sync issue.

    To clarify, there are 4 types of controls I tried:

    1. The slider on the touch bar (macbook pro native)
    2. The brightness buttons (not a slider) on the same touch bar, when the menu is expanded
    3. The brightness buttons on my PC layout keyboard ('F1' & 'F2') (which should be sending the same signals as 2)
    4. The brightness slider from MonitorControl in the menu bar (I have it setup as control all so it's probably working regardless of the sync option)

    My sync setting is checked, and after sleep I noticed that 1 stops working while 2 and 3, 4 still works.

  9. waydabber commented on Mar 27, 2022

    @waydabber
    waydabber
    on Mar 27, 2022
    Member

    2 will send proper keyboard commands which are intercepted by MonitorControl so 2,3,4 is the same. So the issue affects only reading 1. upon sleep. We'll have to look into that.

  10. lsy66666 commented on Apr 2, 2022

    @lsy66666
    lsy66666
    on Apr 2, 2022
    - macOS version: 12.3
- Mac model: Macbook Pro (2019)
- MonitorControl version: 4.0.2
- Monitor(s): T270LG
- Apple Silicon/M1 (yes or no): no

    我也遇到了这个问题。希望能修复，感谢。

  11. pizza496 commented on Apr 6, 2022

    @pizza496
    pizza496
    on Apr 6, 2022
    • macOS version: 12.3
    • Mac model: Macbook Pro (2020)
    • MonitorControl version: 4.0.2 build 6965
    • Monitor(s): S24H85x
    • Apple Silicon/M1 (yes or no): no

    I'm also experiencing this issue.

  12. te6-in commented on Jul 26, 2022

    @te6-in
    te6-in
    on Jul 26, 2022
    - macOS version: 12.5
- Mac model: MacBook Pro (13-inch, 2018)
- MonitorControl version: 4.1.0 build 7034
- Monitor(s): HP 5DQ99AA
- Apple Silicon/M1 (yes or no): no

    I'm experiencing the same issue on the latest available version. Type 2, 3, and 4 work, but Type 1 nor the sliders in the control center and System Preferences won't work.

    By the way, thanks for this fantastic software!

  13. andrew-stupchuk commented on Sep 16, 2022

    @andrew-stupchuk
    andrew-stupchuk
    on Sep 16, 2022

    I'm also experiencing this issue.

    - macOS version: 12.5.1
- Mac model: MacBook Pro (16-inch, 2019)
- MonitorControl version: 4.1.0 build 7034
- Monitor(s): Dell s2721dgfa
- Apple Silicon/M1 (yes or no): no

  14. fnwbr commented on Apr 7, 2023

    @fnwbr
    fnwbr
    on Apr 7, 2023

    Now on Ventura and still experiencing this.

    - macOS version: 13.3
- Mac model: MacBook Pro (16-inch, 2019)
- MonitorControl version: 4.1.0 build 7034
- Monitor(s): Dell U3223QE
- Apple Silicon/M1 (yes or no): no

  15. silver886 commented on Aug 27, 2023

    @silver886
    silver886
    on Aug 27, 2023

    I'm also experiencing this issue.

    - macOS version: 12.6.8 (21G725)
- Mac model: MacBook Pro (15-inch, 2017)
- MonitorControl version: 4.1.0 build 7034
- Monitor(s): HP E24d G4 Display * 2
- Apple Silicon/M1 (yes or no): no

  16. Porencephaly commented on Dec 9, 2023

    @Porencephaly
    Porencephaly
    on Dec 9, 2023

    I'm also having this issue.

    - macOS version: 13.6.1
- Mac model: iMac (27-inch, 2017)
- MonitorControl version: 4.2.0
- Monitor(s): Dell P2222H
- Apple Silicon/M1 (yes or no): no

  17. waydabber commented on Oct 3, 2024

    @waydabber
    waydabber
    on Oct 3, 2024
    Member

    Hopefully this issue is resolved with the latest version. If not, will reopen. :)

  18. waydabber
    closed this as completedon Oct 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugIssue is a bug (e.g. Crash, …)

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions