For a command-line option, ddcctl (https://github.com/kfix/ddcctl) works nicely in my experience, with a Dell Ultrasharp connected via USB-C.
I have a script hacked together to fetch the internal display's brightness once a minute and apply it, with a scaling factor, to the external, so that they're both effectively controlled by the laptop's ambient light sensor. It's really nice for working in a room with lots of windows.
A more batteries-included alternative, which appears to also provide brightness sync, is Lunar (https://lunar.fyi/). I haven't had a chance to try it, but the Github repo makes it look pretty solid.
Thanks for mentioning Lunar! I'm the developer of the app.
I've had a lot of feedback on it and users really helped me to fix most of the use cases so please give it a try. It has a lot of options to make it work just the way you want.
And if it doesn't, feel free to send me feedback. I'm still developing new features for it like weather aware adaptive brightness (for less brightness on those cloudy days), an external USB light sensor (for Mac Minis, clamshell mode Macbooks or even Hackintoshes) and a new curve fitting algorithm to better adapt the 0-100 curve when you adjust the brightness manually.
Would you expect Gatekeeper on High Sierra to just refuse to run a current build outright, without even the usual bypass options? I'm not sure if my IT department has been continuing the war against its own users, or maybe I've just put off updating too long.
Lunar is signed and notarized with a paid developer certificate so I don’t think gatekeeper could block it in anyway.
It’s possible that in High Sierra you are missing the Swift 5 runtime. You can find details about this in the troubleshooting section of the GitHub readme.
That did the trick, thanks! Weird that the error details would talk about code signing when the problem was a missing runtime, but go figure.
I've switched over to using Lunar as of this morning, following the runtime install. Unfortunately, it looks like today's going to be cloudy straight through, so I don't know that I'll get the best opportunity to see the app strut its stuff right away. That said, the UX has been very solid thus far, and I like the extensive configurability even if I have no intention of using more than about 5% of it.
I wasn't sure if a Lenovo Monitor Plugged in via VGA to a Dell Dock to my MBP 13" would support DDC.
MonitorControl wasn't able to control my Brightness, it just set it to lowest level. This made me realise that there was some support to DDC, I tried trouble shooting using ddctl which was able to set the values, but not poll it.
Finally tried Lunar (https://lunar.fyi/) and it works like a charm. It's more of a set it and forget approach and has a unique UI.
I did recently write a script to read the room brightness value from a Hue Light Sensor and adjust my external monitor brightness, with some smoothing applied. It was triggered by being stuck at home like everyone else.
Funny how similar thought processes can be sometimes. I’m now up to motorising my blinds so that the light sensor also controls the blinds to keep the room at the same light level through the day.
Not all that similar, I think. I did mine precisely so I can always keep the blinds open and also not get eyestrain.
I miss the roof deck at work. This time of year, weather and meeting schedule permitting, I'd typically spend somewhere between four and sixteen hours a week up there, enjoying the heat and watching ospreys, gulls, and the occasional peregrine while I waited for builds or test runs or whatever.
I think like many folks lately, I seem to have developed a touch of agoraphobia this year. But I need to at least be able to see outside, or I start to forget I exist.
No, but the only thing in it that isn't trivial or already discussed is the invocation for getting the internal display's current brightness values, which is this:
I also have absolutely no idea this was possible. Just tested it on my 2015 MBP with relatively cheap AOC 27" 4K and DisplayPort and it works perfectly!
Great codebase. I stumbled on this while trying to figure out how to programmatically control screen brightness in a macOS app. Turns out that this is far more difficult than imagined. Even controlling just the built-in screen, something I assumed would be included in Apple's libraries, was not included. The source code in MonitorControl is very well written and commented and helped me catch the mistakes I was doing in my very hacky solution.
Doing anything on macOS is more difficult than I imagine it to be. For example, writing an alt-tab-type app, enumerating the list of apps and their windows. Good luck.
The famous Dropbox Mac finder hack. It may have been mythologized a little, as Rajiv Eranki was probably the genius hacker who figured it out.
> Here’s that rare Steve Jobs story, one that’s never been told, about the company that got away. Jobs had been tracking a young software developer named Drew Houston, who blasted his way onto Apple’s radar screen when he reverse-engineered Apple’s file system so that his startup’s logo, an unfolding box, appeared elegantly tucked inside. Not even an Apple SWAT team had been able to do that.
> Rajiv Eranki (early employee, no longer at Dropbox) did much of the reverse-engineering required to get the our file overlay icons onto files in the Finder, and also to get us into context menus.
I have often wondered if you could exploit a monitor over the DDC bus sending i2c commands. There have just got to be memory corruption bugs in the display controller code.
They probably also typically have some flash memory, so perhaps one could permanently reprogram a monitor after the exploit?
Could monitors be malicious and exploit vulnerabilities in computers by sending corrupted data over the DDC bus?
The crazy thing is that computers send +5V over the DDC bus to the monitor so that they are able to read data even if the monitor is powered off and not connected to the mains! So, simply connecting something to the computer's display port could be enough.
I don't have a touchbar mac to test, but does it work with external non-apple displays? Via Karabiner you can configure keys to change the external display brightness. Works great on a Thunderbolt Display. Completely ignores my Dell / LG.
The main reason why I think this wouldn't work is because in the display properties there's no brightness slider for non Apple external displays. There is one for Apple displays.
That's not necessary. There is ddcci-dkms which can be built against the running kernel and signed as all the other modules. I use it on both Ubuntu (via shim + grub) and Arch (via direct boot).
This allows controlling the screen brightness from the usual places (gnome power menu thingy or via light for the i3 crowd). See the Arch Linux Wiki for more info [0].
An eye saver with this ultra lightweight 16" USB-C travel monitor I picked up.
On resume from suspend the monitor always dims down to some ridiculously low setting, and without `ddcutil` I'd have to manually adjust the brightness via hardware toggle. As a workaround for the limitation of the monitor I just have a bash script that invokes `ddcutil` on resume from suspend - wonderful :)
Oh wow great, I hope this works for me too! I have an LG 4K screen and the LG tool to change brightness and contrast is really terrible, it has some stupid built-in fake Picture in Picture mode which is constantly flashing red borders around the screen when you use it. And the UI is really bad and slow.
This little menubar control looks like just what I wanted.
Edit: Yes it works great! On my LG24UD58. Perfect!
Unfortunately it doesn't seem to work with my Eizo L568 but that's ancient. And I think it had some special USB-based control method. But really glad to be able to get rid of the LG software now.
PS: You have to enable the contrast with a tickbox, otherwise that slider is not shown.
The iMac light sensor controls the brightness of both monitors automatically. You can even insert a fixed offset to match the absolute brightness of both monitors.
But my Mac has no brightness sensor (it's a mini). I use the screen with my PC and a raspberry pi as well so I couldn't use an iMac, though I have one at the office (if I ever go back there...). It's really a shame they got rid of the target display function, this would have been perfect :(
If this works for you, please also give Lunar[1] a try! It's free, and has a handy mode where it can sync your already adaptive built-in brightness to the external monitors.
I'm the developer of Lunar so feel free to ask any questions about it.
Not if only someone could figure out how to make external monitors on mac actually work consistently. Macos still tends to not pick up the correct refresh rate or even the monitor itself.
On Linux you can do the same with ddccontrol. I wrote an article last year explaining how I have my monitor automatically dim at night, in combination with Redshift:
I would love to be able to donate to continued development & support of this software - it's great! There doesn't appear to be a Patreon/tip jar but I'd love to contribute if there is one.
This works great in my setup:
MBP 15-Inch, 2018,
macOS Catalina 10.15.5,
Installed via Homebrew Cask,
LG 34" 5k2k 34WK95U-W via Thunderbolt 3,
Sonnet Echo 11 Thunderbolt 3 Dock,
Dell U3417W 34" via HDMI via Echo 11 Dock.
Volume and brightness work on both displays. Contrast only works on the Dell (after enabling in the preferences) - no big deal. I can adjust brightness on both displays at the same time via the keyboard... that is spectacular. Volume controls work as expected - finally!! Fantastic!!
For those on Windows there's Twinkle Tray, works remarkably well. It has the ability to set timers, which I set to dim my monitor at night and increase the brightness during the day.
You could try Lunar[1] for that issue. It supports any number of monitors and contains a workaround that seems to also work with multiple identical monitors that can't be uniquely identified through their EDID data.
There are still some issues with some multiple port docks but so far that only turned out to be hardware related.
I'm the developer of Lunar so feel free to ask any questions about it.
If you like keyboard shortcuts you might like to give Lunar[1] a try. It also has shortcuts for changing contrast and volume of the monitor as well as do that automatically for you based on the builtin monitor brightness or the sun elevation in your location.
OMG, thank you so much danso and all the developers of this app! This is the biggest inconvenience and overall PITA docking my MBP, it annoys me constantly on a daily basis. just tried it out, it's like my prayers were answered!
Might be useful to some: LG Ultrafine 4k/5k brightness can be controlled with the touch bar. Press the Brightness icon on the touch bar and two sliders show up, one for your mac and one for the LG.
You could try Lunar[1] for that. It syncs your builtin monitor brightness to all your external monitors. As long as you have adaptive brightness enabled on your Macbook, the external monitors will also be adaptive.
Does anyone have trouble with their Macbook recognizing an external display? I have a new 2020 Macbook Pro and it struggles to recognize my Samsung display. I often have to reboot the Mac for it to be recognized.
I’ve got issues where macOS sees both monitors but won’t send output to both every time I come out of sleep. Like one of the displays will turn on like it has signal, then hang for a second and go back to sleep, repeat. I use a program called disable monitor, which shows all the profiles for the display. For some reason when one doesn’t connect it goes into the first profile for the resolution/refresh rate/color depth, then I manually select the third and it connects right away
I wonder wether there's some problem with the usb-c alternate modes and their implementations / drivers.
Below are a bunch of my experiences with this which shows that behaviours are all over the place which kind of excludes an outright broken OS or piece of equipment. To me it looks much more like a compatibility issue.
I don't own a usb-c mac, but I've never had any problems whatsoever with my 2013 retina, always works perfectly even with 4k@60Hz screens.
I have a desktop PC which exhibits the same kind of weird behaviour you have. It has a thunderbolt 3 / usb-c / dp connector which is downright awful.
I've managed to connect an Apple thunderbolt display to it with official tb2 -> tb3 adapter, it works well most of the time. Put the computer to sleep though and the screen never comes back on. Sometimes it doesn't detect the USB ports on it either. Mostly works if I force the thunderbolt mode to DisplayPort only in the bios.
I've next connected a regular usb-c monitor to it (DP alternate mode + usb2 for peripherals). Works great in bios. Mostly works on Linux. On windows it turns off when getting to the login screen. I don't know how, but I've managed to get it to work exactly once. When I turned the computer back on the next morning, it was again off on the windows login screen. The monitor IS detected, it shows up in the Display Preferences if I connect it to both usb-c and display port. It just won't turn on.
On Linux, it kinda works. I would say there's a 50/50 chance it won't detect it at 60 Hz. Sometimes, if it works at 60Hz, if the display goes to sleep it won't come back on at 60Hz. I guess at least there is some output, so it's got that going over windows.
I found an option on the bios to enable "high speed display output". No idea what exactly that means, it didn't do anything.
This same screen works perfectly with a usb-c (no thunderbolt) laptop on linux. Never had any issue, always detected as 4k@60Hz.
I believe that the difficulty of controlling external monitor brightness is a significant factor in almost all people running external displays too bright (often much too bright). Because the standard software that comes out of the box doesn’t let you adjust the brightness of external monitors in any operating system I know of, and adjusting brightness by pressing buttons on the monitor’s on-screen display is invariably a pain.
Windows has two completely different APIs for adjusting screen brightness: one seems to only work on internal displays, the other seems to only work on external displays. I say “seems to” because they don’t document these facts, this is just what I observe by fiddling with the APIs. And only the first one is exposed anywhere in the UI: in Settings → System → Display (where you change the screen resolution and such) it lets you change the brightness of an internal display, but says something like “you can’t adjust the brightness of this device” for external monitors.
Laptop brightness keys (what Linux calls XF86BrightnessUp and XF86BrightnessDown) can’t be remapped by any means I know of. I don’t know of any way of being notified when the internal display brightness changes, either. I think you can poll the value, though it’s three years since I prodded this stuff and my memory is vague. Even so, it’d always be a delayed reaction. Kinda wish I were back on my last laptop where I used Arch Linux + i3 and handled XF86Brightness{Up,Down} myself.
(That brings me to my second major annoyance about built-in monitor brightness control software: stepping by a linear 10% the whole way is stupid; something like a logarithmic scale is much more sensible. The difference between 1% and 10% is at least as important in low lighting as the difference between 10% and 50%. I wrapped xbacklight to make it logarithmic on Arch, but I can’t do that on Windows, where the keys just jump by 10%. Similar deal with phone brightness, the difference two millimetres makes at the left end of the scale is more than the whole right hand half of the scale. Who on earth thought linear brightness was the right thing? Do they know nothing about human perception of brightness? Why is this obviously-badly-wrong practice universally adopted?)
What would be rather nice would be the ability to calibrate internal and external displays to match, so that the brightness of connected external displays could match my internal monitor immediately, following my chosen curve.
As it is, I use ScreenBright and script it so I can do both my external displays at once. (Now, I could reimplement the needed functionality from the relevant API in a short time, but ScreenBright does the job so I don’t bother.) I tend to type `b 20` in the mornings, sometimes `b 40` in the afternoons, and `b 0` in the evening. Seldom do I want to go past 40%. As I said, most people run their external monitors too bright, often much too bright.
DDC was afaik never officially supported, and whatever they did with the connection path means that there's enough reports of "crash whole OS trying to change brightness of display"
I have a script hacked together to fetch the internal display's brightness once a minute and apply it, with a scaling factor, to the external, so that they're both effectively controlled by the laptop's ambient light sensor. It's really nice for working in a room with lots of windows.
A more batteries-included alternative, which appears to also provide brightness sync, is Lunar (https://lunar.fyi/). I haven't had a chance to try it, but the Github repo makes it look pretty solid.