OSD slider not displayed on MacOS Tahoe · Issue #1782 · MonitorControl/MonitorControl · GitHub
Skip to content

OSD slider not displayed on MacOS Tahoe #1782

Closed

Description

@SRANCO

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

When I change the brightness of the monitor with the keyboard keys, the dimming is not displayed. See the attached video. It's not visible but I change the brightness of my monitor. Compare with the change in volume, there is a gradation, but with the change in brightness, it is absent.

preview.mov

Steps to reproduce

Press de the keys F1 and F2 on the Keyboard to change de monitor brightness.

Expected behavior

We should see the gradation on the native MacOS preview.

Anything else?

No response

Environment Information (please complete the following information)

- macOS version: macOS Tahoe beta 26.0 (25A5346a)
- Mac model: MacBook Pro 2021
- MonitorControl version: 4.3.3 build 7123
- Monitor(s): OMEN HP 24"
- Apple Silicon/M1 (yes or no): yes
- Keyboard used : Apple Magic Keyboard

Activity

  1. waydabber commented on Aug 25, 2025

    @waydabber
    Member

    Note: the latest pre-release version of BetterDisplay has a proper solution for this, I recommend using that application. MonitorControl v4.x will probably not have this fixed (it's a fundamental issue, the native OSD framework does not provide this functionality on Tahoe).

  2. SRANCO commented on Aug 25, 2025

    @SRANCO
    Author

    Thanks, useful answer!

  3. changed the title [-]Gradation not displayed on MacOS Tahoe[/-] [+]OSD slider not displayed on MacOS Tahoe[/+] on Aug 27, 2025
  4. hexeric commented on Sep 16, 2025

    @hexeric

    i second this issue. unfortunate! maybe apple will fix it on their side?
    i do not want to change app, i changed from betterdsiplay to monitorcontrol for a reason.

  5. waydabber commented on Sep 16, 2025

    @waydabber
    Member

    I am working on a version of MonitorControl derived from BetterDisplay with the same feature-set as MonitorControl for a simplified experience. It's not going super fast and I don't have an ETA but eventually the replacement app should solve this issue. Obviously the UI and everything will resemble BetterDisplay (which can be good or bad news, depending on which app UI you prefer :)), just with the limited functionality of MonitorControl.

  6. hexeric commented on Sep 16, 2025

    @hexeric

    great to hear! cool! betterdisplay is not fully free and does/wants too much. thanks for working on a better monitorcontrol ;)

  7. habovh commented on Sep 17, 2025

    @habovh

    I must admit I was a bit reluctant about switching apps as well as I only need to be able to adjust non-Apple displays brightness with the keyboard, but man BetterDisplay is something! You can dial it down as much as you want to only have a brightness slider, or even without a menu item and just the Tahoe native-looking OSD when using keyboard, or you can go to town and explore the rabbit hole of DDC.

    While I can see how the powerful capabilities and licensing may scare people, BetterDisplay is a power user's dream. Awesome work @waydabber!

    I believe there's still value in offering a dead simple brightness adjustment app such as MonitorControl, especially for non-technical folks though and I'll be monitoring. In the meantime, I'm more than happy with BetterDisplay and will likely continue using it :)

  8. hexeric commented on Sep 17, 2025

    @hexeric

    yes i tried it too and concur! amazing BUT super complex and way too much for normal users (monitorcontrol fit that bill). so glad it will live on in a 'lite' version too.

  9. bkarakashev commented on Oct 31, 2025

    @bkarakashev

    Hey @waydabber, I hope you are well. I wonder if you found some time to fix this issue in MonitorControl? Thanks in advance.

  10. waydabber commented on Oct 31, 2025

    @waydabber
    Member

    Yeah, sorry for the lack of progress. Did not gave up creating a MonitorControl variant from BetterDisplay, it's just that I have other coding (and other non-coding) stuff to do as well. I should give this a bit more priority, I know. Stripping BD of all things not needed in MC in a way that things remain neat and sustainable is a more serious undertaking than I originally thought, requiring a lot of careful refactoring. I'll post a build when I have something to share (might take a while though). :)

  11. MotoTimL commented on Dec 6, 2025

    @MotoTimL

    First, thank you for creating such a great app. I think I'm encountering similar behavior mentioned above so I didn't want to create a new issue but just provide more info. The function keys for increasing/decreasing brightness and volume all work for me as do the controls in the panel, but the small display that indicates the changes I am making to either brightness or volume pops up but does not indicate anything, either current level or the changes being made. I'm attaching two screen shots. The first shows the panel working properly from the menu bar, the second shows an empty "slider." This is the one not working. And I should point out that it works on the native MacBook screen without attached monitor. The problem is only happing on the attached monitor.
    Hardware: MacBook Pro (M1), Tahoe 26.1, Asus PA27JCV monitor , USB-C connection.

    Image

    Image

  12. VishalDhayalan commented on Jan 18, 2026

    @VishalDhayalan

    Could this somehow also be related to #1831 ?

  13. wsalame commented on Jan 30, 2026

    @wsalame

    Yes, this is crucial for audio! This is my main use case

  14. hcguersoy commented on Feb 13, 2026

    @hcguersoy

    Upgraded to 26.3 few minutes ago and same behaviour: No OSD slider action for sound volume and brightness visible.

  15. robertjanezic commented on Mar 6, 2026

    @robertjanezic

    Just confirming this is still an issue.

  16. joaqo commented on Mar 14, 2026

    @joaqo

    Still an issue :sad:

  17. waydabber commented on Mar 14, 2026

    @waydabber
    Member

    Yes, this is an issue. I was working on a MonitorControl version derived from BetterDisplay, got halfway done but then started working on a major refactor + adding some new features for BetterDisplay and that halfway-done MonitorControl version got outdated, especially as Apple introduced various changes in macOS as well that further affected the UI.

    Maybe a simple/elegant solution would be just to provide an importable configuration file for BetterDisplay that removes all unneeded stuff from the app menu to make things streamlined (hide all stuff that is not in MonitorControl or would require Pro alongside the Get Pro badge in the app menu which I understand annoys some people who just wants a MonitorControl replacement for Tahoe). App Settings would of course still remain somewhat complex compared to MonitorControl, but most people don't go there regularly.

  18. likaia commented on Apr 5, 2026

    @likaia

    I forked the code and fixed this issue. If you need it, you can install the one I specifically adapted for macOS 10.6.

    https://github.com/likaia/MonitorControl/releases/tag/v1.1.0

    @waydabber @joaqo @hcguersoy @wsalame @SRANCO @MotoTimL @bkarakashev @waydabber

  19. waydabber commented on Apr 5, 2026

    @waydabber
    Member

    I certainly encourage forking or experimenting with this.

  20. likaia commented on Apr 5, 2026

    @likaia

    I certainly encourage forking or experimenting with this.

    Hmm, you're right, the same name does cause ambiguity. I've changed it to a new name: LumaGlass.

  21. arsarsars1 commented on Apr 6, 2026

    @arsarsars1

    I will resolve the issues in the PR today. It should be ready to merge soon. @waydabber.

  22. asentientbot commented on May 21, 2026

    @asentientbot

    a (dumb) workaround i didn't see mentioned yet -- defaults write com.apple.controlcenter EnableSystemBanners -bool false sets sequoia style OSD globally, for anyone else like me that preferred it anyways

  23. waydabber commented on May 21, 2026

    @waydabber
    Member

    @asentientbot - ingenious!

  24. locked and limited conversation to collaborators on May 21, 2026
  25. converted this issue into a discussion #1873 on May 21, 2026
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

    known IssueIssue is known for the latest version of the app

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions