[GH-ISSUE #1782] OSD slider not displayed on MacOS Tahoe #983

New issue

Open

opened 2026-05-05 06:59:19 -06:00 by gitea-mirror · 21 comments

gitea-mirror commented 2026-05-05 06:59:19 -06:00

Owner

Copy link

Originally created by @SRANCO on GitHub (Aug 24, 2025).
Original GitHub issue: https://github.com/MonitorControl/MonitorControl/issues/1782

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.

https://github.com/user-attachments/assets/b039d355-e43d-4403-9f4b-7373416e9305

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

Originally created by @SRANCO on GitHub (Aug 24, 2025). Original GitHub issue: https://github.com/MonitorControl/MonitorControl/issues/1782 ### 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 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. https://github.com/user-attachments/assets/b039d355-e43d-4403-9f4b-7373416e9305 ### 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) ```markdown - 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 ```

gitea-mirror added the

known Issue

label 2026-05-05 06:59:19 -06:00

gitea-mirror commented 2026-05-05 06:59:23 -06:00

Author

Owner

Copy link

@waydabber commented on GitHub (Aug 25, 2025):

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).

<!-- gh-comment-id:3219118994 --> @waydabber commented on GitHub (Aug 25, 2025): Note: the latest pre-release version of [BetterDisplay](https://betterdisplay.pro) 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).

gitea-mirror commented 2026-05-05 06:59:25 -06:00

Author

Owner

Copy link

@SRANCO commented on GitHub (Aug 25, 2025):

Thanks, useful answer!

<!-- gh-comment-id:3220681765 --> @SRANCO commented on GitHub (Aug 25, 2025): Thanks, useful answer!

gitea-mirror commented 2026-05-05 06:59:26 -06:00

Author

Owner

Copy link

@hexeric commented on GitHub (Sep 16, 2025):

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.

<!-- gh-comment-id:3297958245 --> @hexeric commented on GitHub (Sep 16, 2025): 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.

gitea-mirror commented 2026-05-05 06:59:27 -06:00

Author

Owner

Copy link

@waydabber commented on GitHub (Sep 16, 2025):

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.

<!-- gh-comment-id:3298160118 --> @waydabber commented on GitHub (Sep 16, 2025): 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.

gitea-mirror commented 2026-05-05 06:59:28 -06:00

Author

Owner

Copy link

@hexeric commented on GitHub (Sep 16, 2025):

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

<!-- gh-comment-id:3298196935 --> @hexeric commented on GitHub (Sep 16, 2025): great to hear! cool! betterdisplay is not fully free and does/wants too much. thanks for working on a better monitorcontrol ;)

gitea-mirror commented 2026-05-05 06:59:29 -06:00

Author

Owner

Copy link

@habovh commented on GitHub (Sep 17, 2025):

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 :)

<!-- gh-comment-id:3302623890 --> @habovh commented on GitHub (Sep 17, 2025): 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 :)

gitea-mirror commented 2026-05-05 06:59:31 -06:00

Author

Owner

Copy link

@hexeric commented on GitHub (Sep 17, 2025):

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.

<!-- gh-comment-id:3302635137 --> @hexeric commented on GitHub (Sep 17, 2025): 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.

gitea-mirror commented 2026-05-05 06:59:34 -06:00

Author

Owner

Copy link

@bkarakashev commented on GitHub (Oct 31, 2025):

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

<!-- gh-comment-id:3472252586 --> @bkarakashev commented on GitHub (Oct 31, 2025): Hey @waydabber, I hope you are well. I wonder if you found some time to fix this issue in MonitorControl? Thanks in advance.

gitea-mirror commented 2026-05-05 06:59:36 -06:00

Author

Owner

Copy link

@waydabber commented on GitHub (Oct 31, 2025):

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). :)

<!-- gh-comment-id:3473452982 --> @waydabber commented on GitHub (Oct 31, 2025): 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). :)

gitea-mirror commented 2026-05-05 06:59:38 -06:00

Author

Owner

Copy link

@MotoTimL commented on GitHub (Dec 6, 2025):

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.

<!-- gh-comment-id:3620882707 --> @MotoTimL commented on GitHub (Dec 6, 2025): 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.  

gitea-mirror commented 2026-05-05 06:59:40 -06:00

Author

Owner

Copy link

@VishalDhayalan commented on GitHub (Jan 18, 2026):

Could this somehow also be related to #1831 ?

<!-- gh-comment-id:3765266816 --> @VishalDhayalan commented on GitHub (Jan 18, 2026): Could this somehow also be related to #1831 ?

gitea-mirror commented 2026-05-05 06:59:42 -06:00

Author

Owner

Copy link

@ghost commented on GitHub (Jan 26, 2026):

Adding in: this is all sliders, not just brightness. Audio, too. Would love to see a fix for this but it's a quality of life issue, not a functionality issue.

<!-- gh-comment-id:3800967645 --> @ghost commented on GitHub (Jan 26, 2026): Adding in: this is all sliders, not just brightness. Audio, too. Would love to see a fix for this but it's a quality of life issue, not a functionality issue.

gitea-mirror commented 2026-05-05 06:59:44 -06:00

Author

Owner

Copy link

@wsalame commented on GitHub (Jan 30, 2026):

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

<!-- gh-comment-id:3825385285 --> @wsalame commented on GitHub (Jan 30, 2026): Yes, this is crucial for audio! This is my main use case

gitea-mirror commented 2026-05-05 06:59:45 -06:00

Author

Owner

Copy link

@hcguersoy commented on GitHub (Feb 13, 2026):

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

<!-- gh-comment-id:3897507795 --> @hcguersoy commented on GitHub (Feb 13, 2026): Upgraded to 26.3 few minutes ago and same behaviour: No OSD slider action for sound volume and brightness visible.

gitea-mirror commented 2026-05-05 06:59:49 -06:00

Author

Owner

Copy link

@robertjanezic commented on GitHub (Mar 6, 2026):

Just confirming this is still an issue.

<!-- gh-comment-id:4013603962 --> @robertjanezic commented on GitHub (Mar 6, 2026): Just confirming this is still an issue.

gitea-mirror commented 2026-05-05 06:59:51 -06:00

Author

Owner

Copy link

@joaqo commented on GitHub (Mar 14, 2026):

Still an issue :sad:

<!-- gh-comment-id:4059627517 --> @joaqo commented on GitHub (Mar 14, 2026): Still an issue :sad:

gitea-mirror commented 2026-05-05 06:59:53 -06:00

Author

Owner

Copy link

@waydabber commented on GitHub (Mar 14, 2026):

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.

<!-- gh-comment-id:4061079651 --> @waydabber commented on GitHub (Mar 14, 2026): 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.

gitea-mirror commented 2026-05-05 06:59:54 -06:00

Author

Owner

Copy link

@likaia commented on GitHub (Apr 5, 2026):

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

<!-- gh-comment-id:4188928513 --> @likaia commented on GitHub (Apr 5, 2026): 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

gitea-mirror commented 2026-05-05 06:59:56 -06:00

Author

Owner

Copy link

@waydabber commented on GitHub (Apr 5, 2026):

I certainly encourage forking or experimenting with this.

• There is the fork of @likaia (although I am not sure whether using the same name and a random new version number is a good idea, see my take on this here: https://github.com/MonitorControl/MonitorControl/discussions/1856#discussioncomment-16455466)
• Also there is a PR that aims to address this by @arsarsars1 (although it's a bit unfinished) - https://github.com/MonitorControl/MonitorControl/pull/1827

<!-- gh-comment-id:4188999403 --> @waydabber commented on GitHub (Apr 5, 2026): I certainly encourage forking or experimenting with this. - There is the fork of @likaia (although I am not sure whether using the same name and a random new version number is a good idea, see my take on this here: https://github.com/MonitorControl/MonitorControl/discussions/1856#discussioncomment-16455466) - Also there is a PR that aims to address this by @arsarsars1 (although it's a bit unfinished) - https://github.com/MonitorControl/MonitorControl/pull/1827

gitea-mirror commented 2026-05-05 06:59:58 -06:00

Author

Owner

Copy link

@likaia commented on GitHub (Apr 5, 2026):

I certainly encourage forking or experimenting with this.

• There is the fork of @likaia (although I am not sure whether using the same name and a random new version number is a good idea, see my take on this here: macOS 26 compatibility notes and reference implementation #1856 (comment))
• Also there is a PR that aims to address this by @arsarsars1 (although it's a bit unfinished) - Fix UI display issues and improve macOS Tahoe/Sequoia support #1827

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

<!-- gh-comment-id:4189114671 --> @likaia commented on GitHub (Apr 5, 2026): > I certainly encourage forking or experimenting with this. > > * There is the fork of [@likaia](https://github.com/likaia) (although I am not sure whether using the same name and a random new version number is a good idea, see my take on this here: [macOS 26 compatibility notes and reference implementation #1856 (comment)](https://github.com/MonitorControl/MonitorControl/discussions/1856#discussioncomment-16455466)) > * Also there is a PR that aims to address this by [@arsarsars1](https://github.com/arsarsars1) (although it's a bit unfinished) - [Fix UI display issues and improve macOS Tahoe/Sequoia support #1827](https://github.com/MonitorControl/MonitorControl/pull/1827) Hmm, you're right, the same name does cause ambiguity. I've changed it to a new name: LumaGlass.

gitea-mirror commented 2026-05-05 07:00:00 -06:00

Author

Owner

Copy link

@arsarsars1 commented on GitHub (Apr 6, 2026):

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

<!-- gh-comment-id:4190972112 --> @arsarsars1 commented on GitHub (Apr 6, 2026): I will resolve the issues in the PR today. It should be ready to merge soon. @waydabber.

gitea-mirror referenced this issue 2026-05-05 07:08:22 -06:00

[PR #983] [MERGED] Update Taiwan Chinese translations #1227

Sign in to join this conversation.

No Branch/Tag specified

Branches Tags

main

develop

github-pages

v4.3.3

v4.3.2

v4.2.0

v4.1.0

v4.0.2

v4.0.1

v4.0.0

v4.0.0-rc1

v4.0.0-beta2

v4.0.0-beta1

v3.1.1

v3.1.0

v3.0.0

v3.0.0-rc2

v3.0.0-rc1

v3.0.0-beta8

v3.0.0-beta7

v3.0.0-beta6

v3.0.0-beta5

v3.0.0-beta4

v3.0.0-beta3

v3.0.0-beta2

v3.0.0-beta1

v2.1.0

v2.0.0

v1.7.1

v1.7.0

v1.6.0

v1.5.2

v1.5.0

v1.4.0

1.3.1

v1.3

v1.2.2

v1.3.0

v1.2.1

v1.2

v1.1

v1.0

Labels

Clear labels   

Status: Abandoned

  

arm64

  

beta

  

beta

  

bug

  

done

  

duplicate

  

enhancement

  

feedback needed from reporter

  

in progress

  

invalid

  

investigating

  

known Issue

  

monitor Issue

  

pull-request

Mirrored from GitHub Pull Request

  

translation

  

unable to reproduce

  

unreleased

  

x86

No labels

Status: Abandoned

arm64

beta

beta

bug

done

duplicate

enhancement

feedback needed from reporter

in progress

invalid

investigating

known Issue

monitor Issue

pull-request

translation

unable to reproduce

unreleased

x86

Milestone

Clear milestone

No items

No milestone

Projects

Clear projects

No items

No project

Assignees

Clear assignees

No assignees

1 participant

Notifications

Subscribe

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#983

No description provided.