-
|
I just installed Monterey on my Mac mini M1 with 2 Apple 27" LED cinema Displays and I noticed that there is no longer a way to adjust the brightness, they were stuck on Maximum Brightness. (This was/is a MONTEREY issue NOT MonitorControl) But then I made the mistake of installing MonitorControl (4.0.0-rc1) to see if I could adjust the brightness that way and upon running the app it immediately dimmed the display hooked up via USB-C and a mini displayport adapter to about 30% maximum brightness and it has remained that way ever since, even after quitting the app and restarting the computer. I can dim the display all the way to black if I want via MonitorControl, but maximum brightness is now stuck at around 30%. My display hooked up to the HDMI port remained bright. So I decided to alternate how the displays were connected, hooking the HDMI one to the USB-C, and vice-versa.. and now BOTH displays are permanently dimmed at 30% max! Both displays now have a maximum brightness of 30% even after restarting the computer, disabling MonitorControl, unplugging and plugging in the displays, etc.. Does anyone have any ideas on what I can do to reset them to maximum brightness? It seems like the displays are INTERNALLY stuck at 30% brightness and MonitorControl thinks the 30% is the maximum brightness. Perhaps I need to plug them into another computer and brighten them that way and then plug them back into my computer with MonitorControl not running? Or is there a way to make MonitorControl allow me to brighten them beyond the 30% limitation that it somehow triggered upon running? Thanks so much! Charles |
Beta Was this translation helpful? Give feedback.
Replies: 8 comments 32 replies
-
|
I solved the permanently dimmed screens issue. Here is how I did it (taken from here: https://discussions.apple.com/thread/252063309?answerId=255777656022#255777656022 ) This works in Monterey as well.. doesn't require Big Sur. I downloaded the source code of v3.0.0-rc1 of MonitorControl from here: https://github.com/MonitorControl/MonitorControl/releases/tag/v3.0.0-rc1 Then opened the folder up in Xcode. Did a search for: DDC_HARD_MAX_LIMIT and changed it from 100 to 250 Then RUN the code It asks you to allow it in the Security Preferences.. I just unchecked then checked it again there, since I still had other version of MonitorControl on my computer. I was then able to adjust the brightness of each display to the maximum brightness! I could probably do this in a later version of the source code, but I wanted to do it on a version that someone else had done it on just to be safe. Now my displays are no longer permanently dimmed! Yay! |
Beta Was this translation helpful? Give feedback.
-
|
@waydabber I am using the same setup as you Mini Display to USB-C adapter on M1 Mac Mini. Everything works perfectly, but I can‘t get the microphone to work on FaceTime. Camera works perfectly fine though. Do you have the same issue? |
Beta Was this translation helpful? Give feedback.
-
|
Trying to fix this external Cinema Display stuck at 40% brightness. I tried to install MonitorControl (latest version, 4.1.0), but I am not able to reproduce the fix. I am doing probably something wrong. I am on Monterey 12.4 with a 14'' macbook pro. Any hint what I am doing wrong? Here are my settings:
|
Beta Was this translation helpful? Give feedback.
-
Try setting the minimum value to 0. |
Beta Was this translation helpful? Give feedback.
-
|
On my computer, it has no effect. Weirdly, I have the impression that the DDC max has no effect either. When I change it to 50 or even 10, the max brightness is still the same. Am I supposed to save or activate a setting? |
Beta Was this translation helpful? Give feedback.
-
|
I have the same issue as @pajai under Monterey 12.4, and in addition to that changing the brightness will sometimes cause the monitor to lose signal and show B/W static noise which i can fix by replugging the monitor. |
Beta Was this translation helpful? Give feedback.
-
|
I tried using the method described above on my Apple 27" Thunderbolt display to adjust the DDC max to 250... and it still isn't restoring the previous brightness. I'm getting the same results on both a Mojave MBPro direct thunderbolt in and a Big Sur MBPro with Thunderbolt to USB-C Although I am changing the DDC max to 250, it appears to be stuck at the ~50% brightness mark. 0-50% dimming works, but beyond that it simply stops doing anything from ~50% - 100% I've tried unchecking "Use hardware DDC control" as well as unchecking "Combine hardware and software dimming" and have the same results whether using hardware controls or the software slider. I've also tried checking off and on "Sync brightness changes from Built-in and Apple displays" and this generally just makes the touch bar work when on and not when off. Basically all functionality is fine, it just perma-nerfed the brightness max to 50%, and I'm wondering why the same solution that's working for others isn't working for me. |
Beta Was this translation helpful? Give feedback.
-
|
macOS used to natively have brightness control, built-in audio, and even webcam... but they stop supporting it some time ago. Maybe High Sierra? It definitely isn't working on Mojave. Unfortunately I had no luck with your new suggestion. I will show also include some photos of what happens with the monitor visible in the background as well.
You can see that I have the value set to 255 and as soon as I even click to adjust brightness, it's basically 50%: And here, I open Lunar to do a brightness reset to get it back to full: |
Beta Was this translation helpful? Give feedback.
-
|
Interesting. Did you disable combined dimming in General? If so, is it still changing the brightness via hardware but only up to 50%? Please disable syncing as well so that doesn't interfere in any way just to make sure (but it should not). Can you set the brightness manually via ddcctl https://github.com/kfix/ddcctl to 255 to get the full brightness? (btw it is a shame that Apple stopped supporting their own display which has no actual buttons to be useful with anything other than a mac...) |
Beta Was this translation helpful? Give feedback.
-
|
I have the same problem with my iMac and my MBP running Catalina 10.15.7. But on the MBP, Monitor Control works perfectly when hooked up to a LED Cinema Display, which is an older monitor than the Thunderbolt Display. I've set the brightness manually via ddcctl to 255 to get the full brightness. |
Beta Was this translation helpful? Give feedback.
-
|
I think it would be best to simply blacklist both the Thunderbolt Display and the LED Cinema Display in the next update. Some users seem to have issues while others don't - it might be possible that there are internal firmware differences. Normally these displays were not manufactured with DDC in mind but designed to be controlled by the native Apple method via USB. They seem to be rather unreliable when controlling over DDC. |
Beta Was this translation helpful? Give feedback.
-
|
Tried everything and the only thing that worked for me was using ddcctl and then resetting the brightness/contrast with the -rbc flag. Tried to set the brightness to 255 and that didn't work. Install using Homebrew, |
Beta Was this translation helpful? Give feedback.
-
|
The solution for the brightness and sound worked perfectly. I tried any values beyond 255 and in resulted in sound and brightness going down. So 255 in fact seems the perfect value. |
Beta Was this translation helpful? Give feedback.
-
|
Apple did a couple system software updates since I first posted this and the ability to select the displays as the microphones disappeared whereas they show up as outputs. This happens for other inputs as well such as The RodeCaster Pro (in stereo, shows up in Multi Channel though).. and other inputs. RODE said it's an Apple thing.. so I would use an alternate for the time being. Unless you can set the LED DISPLAY Microphone as System input and select it that way for FaceTime. I can't remember if that works or not. Worth a try. |
Beta Was this translation helpful? Give feedback.
-
|
I can choose the Display as a Input and it works with other Apps. Just FaceTime won’t work, I don’t get it. Does it work in your setup? |
Beta Was this translation helpful? Give feedback.
-
|
It's Apple. One of the system updates recently killed various Mic inputs (including Apple's own LED display mic inputs.) Other companies are aware of the problem and there are workarounds.. like sending the mic input into Blackhole as an aggregate input and accessing it that way.. but I think even doing that, FaceTime won't recognize it. It's really annoying, but not something anyone knows how to fix until Apple fixes it. Just use the mic input of something else for the time being until they fix it. |
Beta Was this translation helpful? Give feedback.
-
|
Thank for the reply! |
Beta Was this translation helpful? Give feedback.
-
|
Btw it works. With you connect it to the iPad it works with the last settings that you set on your Mac (brightness and volume level). |
Beta Was this translation helpful? Give feedback.
-
|
Actually don't think you need MonitorControl for your Cinema Display at all with later versions of MacOS Monterey. Your display settings probably got bungled at some point. Try moving all files in the folder |
Beta Was this translation helpful? Give feedback.
-
|
After dealing with the brightness issue for years (with much of that time
sadly just allowing the display to collect dust) I have found a shockingly
simple fix for my issue:
*I bought a new thunderbolt 2 cable.*
I discovered this when I decided to give it a last troubleshooting attempt,
and noticed that when I pulled up system preferences > displays, the
"brightness" slider didn't appear for the Thunderbolt Display settings. I
figured that was an odd behavior - and perhaps if that function wasn't
available in software, it might mean that the hardware simply isn't making
the connection. This led me to wonder if the degraded quality of the
thunderbolt cable would lead macOS to remove functions from system menus.
It would appear this is exactly the case.
At some point the original attached thunderbolt cable frayed just enough to
remove all *peripheral* functions of the monitor at the same time. (USB
hub, LAN, firewire, webcam, speakers) - yet still allowed the basic display
functionality (although a bit finicky). The fact that the display still
worked - albeit locked at 100% brightness - threw me off for a long time. I
figured it would either be an all-or-nothing connection, or perhaps lose
some features and not others.
Now that I am using a thunderbolt 2 cable directly from the thunderbolt
port on the display to my macbook, everything works perfectly. All
peripherals as well as software brightness controls, keyboard brightness.
The best part of this fix is that you don't have to take the monitor apart
to remove/replace the original cable. You can just leave it unplugged and
use the port. Sure, you lose 1 thunderbolt port - but that's a sacrifice
I'm happy to make!
…On Fri, Sep 9, 2022 at 4:12 AM Rolf Bjaanes ***@***.***> wrote:
Actually don't think you need MonitorControl for your Cinema Display at
all with later versions of MacOS Monterey. Your display settings probably
got bungled at some point. Try moving all files in the folder
~/Library/Preferences/ByHost that starts with
com.apple.windowserver.displays to a different location for backup and
restart your computer. If it doesn't work, try another port on the machine.
If it still doesn't work try one of the other suggestions for
MonitorControl.
—
Reply to this email directly, view it on GitHub
<#739 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ALBFRBGNF3OXJDRQLXJCVZDV5L5RPANCNFSM5GWY43GA>
.
You are receiving this because you were mentioned.Message ID:
<MonitorControl/MonitorControl/repo-discussions/739/comments/3605875@
github.com>
--
Michael Scroggins
***@***.***
|
Beta Was this translation helpful? Give feedback.
-
|
I don’t understand the setup you used to make it work. |
Beta Was this translation helpful? Give feedback.
-
|
Pic 1: Original monitor cable obviously looking pretty rough... but it still will show a display when plugged in. (But brightness can't be adjusted, and all other functionality is gone.) The point of this is to say - I don't think the problem I experienced (dimming to nearly unusable levels) was a direct problem with the Monitor Control software - I think that macOS removes the ability to adjust brightness values if the thunderbolt connection is degraded, even if it still has basic display functionality.
|
Beta Was this translation helpful? Give feedback.
-
|
I was not able to talk to the display via Monitor Control nor Lunar. But I did find a solution: I used this weird little windows tool called Brightness Controler https://www.holstschumacher.dk/p/brightness-controller.html inside Windows 11 running in Parallels 18 on my MacBook Pro with M1 Pro processor. |
Beta Was this translation helpful? Give feedback.
-
|
I am using two Cinema Display 27 monitors for Mac mini M1, one via USB-C to miniDP adaptor an the other via HDMI to DP adaptor through DP to miniDP cable. |
Beta Was this translation helpful? Give feedback.
-
|
@TschonnyCache, @takeichimasato, hello, guys! |
Beta Was this translation helpful? Give feedback.
-
|
I‘m using the same satechi adapter. Thanks for trying out other adapters. Looking forward to your report |
Beta Was this translation helpful? Give feedback.
-
|
@TschonnyCache @freshmeet777 from another account here, my previous message by takeichimasato. |
Beta Was this translation helpful? Give feedback.
-
|
@TschonnyCache @masatotakeichi Also, I'm ordered this one: So, I will try this pair after it's delivering and write a report. To this moment I have tested this adapters, but without success: And, as a temporarily solution, I'm using the Brightness Controller. Thanks to @TschonnyCache! Cheers! |
Beta Was this translation helpful? Give feedback.
-
|
So, as has been promised, here is the report. |
Beta Was this translation helpful? Give feedback.
-
|
@freshmeat777 @TschonnyCache |
Beta Was this translation helpful? Give feedback.
I solved the permanently dimmed screens issue. Here is how I did it (taken from here: https://discussions.apple.com/thread/252063309?answerId=255777656022#255777656022 )
This works in Monterey as well.. doesn't require Big Sur.
I downloaded the source code of v3.0.0-rc1 of MonitorControl from here: https://github.com/MonitorControl/MonitorControl/releases/tag/v3.0.0-rc1
Then opened the folder up in Xcode.
Did a search for: DDC_HARD_MAX_LIMIT and changed it from 100 to 250
Then RUN the code
It asks you to allow it in the Security Preferences.. I just unchecked then checked it again there, since I still had other version of MonitorControl on my computer.
I was then able to adjust the bright…