hi @hagncola - does it work well with 4.0.1? We could add a setting for this.

Hi, it work´s in the meanwhile. I use USB-C to HDMI cable instead of USB-C to USB-C for the second monitor (Mac Mini M1)
I found only one issue (i don´t know if it´s related to last version). If i use the the built in autostart option, after restart the "old brightness" does not apply -- always 100 %. If i use the autostart option from monterey and disbale the built in autostart it works.

Interesting. Maybe it is related to how quickly the display gets responsive maybe? You could try this with v4.0.1 as well.

As i wrote, now all is working fine with 4.02. Never touch running system :)

Works amazing with a Spectre monitor, great work!

@dyasol - does hardware brightness control work with Lunar when you force set the ddc max to 255? If so and it does not work with MC using the same setting (DDC brightness max set to 255) then somehow Apple TB display is not fully compatible with the way MC tries to control it. LED Cinema Display users tend to report success with MC, for Thunderbolt display users the results are mixed so far using DDC.

@dyasol The native brightness control still works for Thunderbolt systems on all macOS systems. I have data about working Apple Native protocol on these displays for Catalina, Big Sur and Monterey, albeit only on newer Mac devices.

I'm not sure why it isn't working for you. Maybe the new macOS versions dropped DisplayServices support for older Macbooks.

I've compiled a Lunar beta here with the 255 limit automatically applied for detected Thunderbolt displays: https://files.lunar.fyi/Lunar-5.1.2-beta14.zip

You might need to do a Full Reset in Lunar if the 100 limit is stored in settings.

@dyasol - does hardware brightness control work with Lunar when you force set the ddc max to 255? If so and it does not work with MC using the same setting (DDC brightness max set to 255) then somehow Apple TB display is not fully compatible with the way MC tries to control it. LED Cinema Display users tend to report success with MC, for Thunderbolt display users the results are mixed so far using DDC.

Forcing ddc max to 255 does not seem to work in DDCctrl, MC or Lunar. Only doing a Brightness/contrast or full reset in Lunar seems to accomplish that.

@dyasol The native brightness control still works for Thunderbolt systems on all macOS systems. I have data about working Apple Native protocol on these displays for Catalina, Big Sur and Monterey, albeit only on newer Mac devices.

I'm not sure why it isn't working for you. Maybe the new macOS versions dropped DisplayServices support for older Macbooks.

I've compiled a Lunar beta here with the 255 limit automatically applied for detected Thunderbolt displays: https://files.lunar.fyi/Lunar-5.1.2-beta14.zip

You might need to do a Full Reset in Lunar if the 100 limit is stored in settings.

I am running Catalina on a 2012 MBP with my TB display, so I agree, they probably dropped DisplayServices support on old hardware.

I was so excited but unfortunately MC did not work for me either. After installation, it decreased my screen brightness even further. I have a Cinema Display with MacBook Air (Apple M1 chip) running Monterey.

This is probably a display firmware problem.

So I connected a Windows PC (DP to DP cable) and that can control the volume using the volume keys on the keyboard without any app installed. Not sure if that bit of info helps but thought I'd mention. No luck with the Mac though.

@ajaffarali Windows controls a software volume (dimming the volume in software before it reaches the monitor).

DDC-based apps like MonitorControl and Lunar change the monitor volume in hardware (the same value that you can see in the monitor settings using its physical buttons).

If you're trying to achieve what Windows is doing, SoundSource can do that for macOS

Gotcha. Since MonitorControl (and Lunar for that matter) don't work for volume levels on my Samsung G9, I'll use SoundSource that does the trick and is good enough for me.

Appreciate your help.