Funny, I just started playing with DDC a few days ago. I've got a work (Mac) and a personal laptop (Dell XPS with Linux) that I like switching between. I had a thunderbolt hub, but was getting tired of moving the cable back and forth, and it was also unreliable on the Mac, causing it to heat up and slow down on occasion. I ended up just buying a pure USB hub with a switch, and running a persistent polling bash script…
The journey to controlling external monitors on M1 Macs
171–180 of 188 posts
Re: The journey to controlling external monitors on M1 Macs
#172This seemed neat so I installed Lunar to try out on my M1 MacBook Air with a LG HDR display connected over HDMI. After launching the app my system started freezing so bad I had a hard time closing the app, inputs unresponsive for 30 sec then active for 1 sec to become unresponsive again. I figured I'd try to launch it with my monitor unplugged and worked fine, but after plugging in my monitor again it doesn't connect…
I can’t say for sure what the problem is in your case, but it’s definitely not a problem in Lunar. All the app does is call a macOS function called IOAVServiceWriteI2C to send a standard DDC message to the monitor (something like “set brightness to 30”) In your case, either the dongle or the monitor reacts unexpectedly to that message. What should happen is that the dongle should simply forward that message as it is…
The dongle that's having problems is a "Selore&S-Global USB-C HDMI + DP" if that's something you want to keep on file.
Thanks for the detailed response and all your work making the app possible!
Re: The journey to controlling external monitors on M1 Macs
#173Earlier quoted context omitted.
Why didn't they abstract it, or create a stripped/safe userland option to replace it? If I'm relying on a Mac for work, I can't have them removing essential features from my computer in a simple upgrade. Maybe MacOS needs semantic versioning, or at least some level of communication with the end user about compatibility.
This was never an intended feature. If I understand the article correctly, they were using an undocumented ("private") API which happened to stop working.
Re: The journey to controlling external monitors on M1 Macs
#174Earlier quoted context omitted.
If it's easy, do you mind sharing the hex for some of the colors, such as the background? You've picked a really nice combo of colors that I'd like to bookmark
Sure, the whole website is open source. This is the file with the colors: https://github.com/alin23/alinpanaitiu.com/blob/master/asset... Although I’m not using them all. I just port them from project to project
Re: The journey to controlling external monitors on M1 Macs
#175Earlier quoted context omitted.
Hey, thank you for the support! I completely understand when users go with something more simple like a CLI or MonitorControl. I do the same myself when I don’t really need the features of a complex app. By the way, I’m not sure if I understood correctly but if you need an external ambient light sensor, Lunar supports that out of the box now: https://lunar.fyi/sensor
This is incredibly well realized! Currently I'm working with a sensor homebrewed from a reverse-biased LED with a Darlington-pair amplifier - not what anyone would call accurate, but precise enough to calibrate reliably over the range of light values to be found in my office as long as I keep direct sunlight off the transistors. Between that, a Pi, ddcutil, and the currently unoccupied DisplayPort input on my monitor…
that's clever! I knew LEDs can be used as sensors but I never had the time to try it.
Yeah, I don't know about DDC via the Mac Min HDMI. Weird things are happening with that port.
Some users report it doesn't work at all, some say their monitor crashes when DDC is sent through the port. One user even had the weird issue where sending DDC through the USB-C port to his Thunderbolt monitor causes the message to also be sent to the monitor connected via HDMI.
I'm trying to find a solution but these seems more like bugs in Apple's implementations of the video driver and we'll have to wait for those to get fixed in Monterey.
Re: The journey to controlling external monitors on M1 Macs
#176Earlier quoted context omitted.
Sure, the whole website is open source. This is the file with the colors: https://github.com/alin23/alinpanaitiu.com/blob/master/asset... Although I’m not using them all. I just port them from project to project
Thanks but that URL isn't working for me?
Re: The journey to controlling external monitors on M1 Macs
#177Earlier quoted context omitted.
Thanks but that URL isn't working for me?
I just clicked on it and it works. But here it is in a shorter form in case the length is the problem: https://tinyurl.com/yzck7y9v
Re: The journey to controlling external monitors on M1 Macs
#178Earlier quoted context omitted.
Yes, exactly. I’ve been using IOKit since day one which is pretty much completely banned from App Store apps.
But have you tried? I read first page I got, and it says "it depends" https://developer.apple.com/forums/thread/51595
Re: The journey to controlling external monitors on M1 Macs
#179Earlier quoted context omitted.
I just clicked on it and it works. But here it is in a shorter form in case the length is the problem: https://tinyurl.com/yzck7y9v
Hmm, I clicked on both links on both my phone (4G) and laptop (wifi) and got a 404 error each time. Perhaps it's not publicly accessible, and only accessible when logged in to your Github account. Strange.
Both links should be working now