mirror of
https://github.com/MonitorControl/MonitorControl.git
synced 2026-05-15 14:15:55 -06:00
[GH-ISSUE #950] Please add support for Lenovo creator extreme #582
Labels
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
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/MonitorControl#582
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @urmelchen2705 on GitHub (Feb 15, 2022).
Original GitHub issue: https://github.com/MonitorControl/MonitorControl/issues/950
Before opening the issue, have you...?
Describe the issue
DDC not working on Lenovo creator extreme
Expected behavior
Control monitor with DDC
Anything else?
No response
Environment Information (please complete the following information)
@the0neyouseek commented on GitHub (Feb 15, 2022):
Hi @urmelchen2705
Please fill out the information about your environment so that we can help debug the issue more effectively.
Could you try using https://github.com/waydabber/m1ddc and see if if works in controlling your monitor ?
@waydabber commented on GitHub (Feb 15, 2022):
Also if you are using HDR please try it in SDR mode and if possible with a standard color mode set in the display. I am interested in this display as I was considering buying one so it would be great to know if it works or not. :)
@waydabber commented on GitHub (Feb 15, 2022):
Also, on Lenovo displays you can long press the Exit button (for 10 secs) to enable/disable DDC/CI so that might help. Please don't use HDMI to connect the display to the Mac as that probably won't work.
@urmelchen2705 commented on GitHub (Feb 15, 2022):
Hi
Ok I will try that later today. The monitor is connected over usb-c
Von meinem iPhone gesendet
@urmelchen2705 commented on GitHub (Feb 15, 2022):
I get this:
@.*** m1ddc % ./m1ddc display list
1 - CreatorXtreme (30AEA662-0000-0000-081F-0104B53C2278)
@.*** m1ddc % ./m1ddc set luminance 50
I2C communication failure: (iokit/?) unknown subsystem error
@urmelchen2705 commented on GitHub (Feb 15, 2022):
DDC was on. No luck yet.
M1dcc give me:
@.*** m1ddc % ./m1ddc display list
1 - CreatorXtreme (30AEA662-0000-0000-081F-0104B53C2278)
@.*** m1ddc % ./m1ddc display 1 set luminance 50
I2C communication failure: (iokit/?) unknown subsystem error
@waydabber commented on GitHub (Feb 15, 2022):
If DDC is enabled in the display and you get this error then something is wrong with the cable or connection maybe (or this display does not support DDC via the USB-C input - which would be strange as it uses displayport alt mode that carries ddc i2c commands all right). It might be that m1ddc is not fully compatible with the new MBP, I didn't try that. You might want to try a simple USB-C to DisplayPort cable if you have one around to see if it works. You can also try other apps like Lunar (@alin23) and see if that works.
Is the display connected directly via a standard USB-C cable provided by the manufacturer?
@alin23 commented on GitHub (Feb 15, 2022):
Me and @urmelchen2705 have been talking over email. He has already tried Lunar and has the same issue.
The monitor blocks DDC for some reason.
I took a look at the monitor manual and user guide and these are the settings that need to be changed for brightness control to be allowed:
If those settings are already in that state, then there's nothing we can do to make it work.
@urmelchen2705 commented on GitHub (Feb 15, 2022):
All settings are in that state but nothing. I’ve tried two original usb-c cables too
@alin23 commented on GitHub (Feb 15, 2022):
I took a look through the monitor database but you seem to be the only one using this monitor with Lunar so far. I have no data on whether the monitor should really support DDC or not. It's possible this is an incompatibility with the M1 DCP (Display Coprocessor) firmware, and hopefully it will be fixed in later updates of macOS.
@waydabber commented on GitHub (Feb 16, 2022):
Oh that's sad as this is a really great display (one that I was considering buying).
But: since this is a FALD/mini-led display, what happens if you use software dimming? If the mini-led control is implemented properly, it should have the same or even superior effect than brightness control via DDC, the hardware backlight should gracefully decrease in intensity while clarity should be retained (somewhat similar to what OLEDs do) so it actually might not make sense to use DDC brightness control anyway. What is your experience with this @urmelchen2705 ? Obviously volume control won't work with DDC being blocked.
@urmelchen2705 commented on GitHub (Feb 16, 2022):
Quick Shade from Mac Appstore works great. I’m using this now.
Monitor Control or Lunar doesn’t because it kills the HDR effect
@urmelchen2705 commented on GitHub (Feb 16, 2022):
Yes the Phillips could be good too. But unavailable yet.
I got the Lenovo monitor for 999 Euro
@waydabber commented on GitHub (Feb 16, 2022):
Hi @urmelchen2705 - if you enable
Avoid gamma table manipulationunderDisplaysin MonitorControl, the app will use the same software technique as QuickShade for dimming. I believe there might be a similar setting in Lunar as well somewhere.@waydabber commented on GitHub (Feb 16, 2022):
... you need to disable
Use hardware DDC controlas well for that to work underDisplays.