mirror of
https://github.com/MonitorControl/MonitorControl.git
synced 2026-05-15 14:15:55 -06:00
[GH-ISSUE #82] Monitor/GPU/Connection Combinations #65
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#65
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 @reitermarkus on GitHub (May 9, 2019).
Original GitHub issue: https://github.com/MonitorControl/MonitorControl/issues/82
This is a collection of combinations which are known to work. Please comment below with your information so that we can hopefully find a pattern for when a longer delay is needed.
minReplyDelay@JoniVR commented on GitHub (May 9, 2019):
minReplyDelayMore Details
Logs (from DisplayPort, default
minReplyDelay, 100 tries,c8608b1)Let me know if there's anything else you'd like me to test.
@reitermarkus commented on GitHub (May 9, 2019):
Interesting that you actually get a response and “only” the checksum doesn't match. It clearly seems to be returning “something” at least.
@reitermarkus commented on GitHub (May 10, 2019):
@JoniVR, did anything change with the latest changes to
DDC.swift?@JoniVR commented on GitHub (May 10, 2019):
Ok, I ran it again, 100 tries, default
minReplyDelay, Displayport cable,d803f92I don't see much difference, ran it 3 times in total to be sure.
Only difference I can make out is it now says
Display does not support DDCon some linesFull Log
(I wish Github would be full-width so you wouldn't have horizontal scroll bars on these logs)
@reitermarkus commented on GitHub (May 14, 2019):
I added some more logging when the checksum fails.
@JoniVR commented on GitHub (May 15, 2019):
Same as before, on
c8ed85fLog
edit:
I could test directly (perhaps on a separate branch) at the DDC.swift repo if that makes it easier for you?
That way you won't have to commit to MonitorControl every time you add extra logging. Your call, anyways, if we can't get reading to work it's not a problem either way, but I'd be happy to keep providing logs if you think you can figure it out. :)
edit 2:
I just got a different response when doing another build (check near the bottom):
@reitermarkus commented on GitHub (May 17, 2019):
The values at the bottom are the last saved values, so no change here, both reads are still failing.
You'll have to try messing around with the
DDC.swiftrepo yourself, see if you stumble upon anything useful.@JoniVR commented on GitHub (May 17, 2019):
I know that, I usually replace the saved values with (0,0) to make debugging easier. I meant the bottom of the log ;)
I'll playing around with it in somewhere the future to see if there's anything I can find. Thanks for the effort on this.
@reitermarkus commented on GitHub (May 17, 2019):
Yeah, these responses seem pretty random, the only one which comes “close” to a valid response is the first one where we are sending
F1and it should return6E 80 BE, but it returns6E 81 F1.@icecreammatt commented on GitHub (May 20, 2019):
I'm not sure if this project is limited to LG displays or not but this was my testing with my Acer Predator
@donluca commented on GitHub (Jun 16, 2019):
High Sierra 10.13.6
Mac Pro 4,1 -> 5,1
Radeon HD 5870 1GB
Fujitsu P24W-3 (straight DVI-D)
Brightness & Volume work perfectly out of the box!
Iiyama XB2283HSU, identified as "PLX2283H-DP" (Mini-DP to DVI-D)
Brightness & Volume work perfectly out of the box!
I'll be shortly upgrading graphic card and monitors and will report back with new combinations.
@donluca commented on GitHub (Jul 18, 2019):
High Sierra 10.13.6
Mac Pro 4,1 -> 5,1
Radeon HD 5870 1GB
Dell P2014H (Mini-DP to DVI-D)
Brightness & Volume work perfectly out of the box!
@mRs- commented on GitHub (Jan 25, 2020):
same setup and it's not working. maybe because of the HDMI? Currently I have no option to use this with a DisplayPort Cable :/
@SongHoang commented on GitHub (Apr 5, 2020):
I can also say I'm having a freezing issue similar to post #193 on a 650M (Macbook Pro Retina 15" Late 2012) and a Dell U2412M. When I unplug my Dell monitor, I can use my laptop again.
@kumowoon1025 commented on GitHub (Apr 6, 2020):
This is not necessarily an issue with the app, but most likely affects these test results; if I connect a display panel to my Mac through multiple routes (e.g. DP and HDMI on eGPU + DP on another eGPU + built in USB-C/DP or HDMI depending on model) usually one of the connections become non-functional if FreeSync version is changed or turned on/off on the display. Issue doesn't persist through a reboot.
I only have AMD and the built in Intel GPUs but I think it could happen to Nvidia chips as well because sometimes it's the built-in (Intel UHD) graphics that gets disabled.
@SongHoang I might be able to test this out, I have an rMBP with the piece of * 650M chip, you mean the mid-2012 iteration right? (There was no late 2012 15" laptop, iirc)
@SongHoang commented on GitHub (Apr 8, 2020):
My apologies, its a Mid-2012 15" Macbook Pro Retina.
After a bit of playing around, 1.4.0 works per recommendation from other posts, but has a few issues. If I have all the devices already plugged in (Apple Thunderbolt Display + Dell U2412M to both Thunderbolt inputs on Macbook) and launch the application, it'll work fine and I can adjust the brightness. But if I have it already running, and plug in the Dell monitor, it'll freeze just like on v2.0.0. No cases will get v2.0.0 working on my end.
Let me know if I can try any another test cases on my end.
@Joshfindit commented on GitHub (Jul 9, 2020):
Worked right the first time, and with a twist:
Thank you
The brightness controls on the monitor are annoying, and now I'm freee!
@ablackbu commented on GitHub (Jul 14, 2020):
I had set the display's "Input Select" value to DVI instead of the default "Auto" for it to work.
OSD -> Extra -> Input Select -> DVI. When on auto it would not work. Changing to DVI fixed the issue on the other monitor.
2 AOC 21.5'' AOC Monitors
Mac Mini (2018)
MacOS 10.5.5
Hope this helps for someone else. Great App 👍
@toyg commented on GitHub (Jul 23, 2020):
Works great for me, including volume (which MacOS couldn't manage before).
@Willardgmoore commented on GitHub (Aug 29, 2020):
Brightness works fine, but I haven't been able to get the sound to work.
I have a dual monitor set up. I've tried either monitor and the Multi-Output(using speakers from both monitors) that I've set up and the audio won't respond to anything. The popup on the screen looks as though the buttons are working, but the sound doesn't adjust. I also tried the ddcctl suggestion. It runs but the screen icon volume level is also not affected by running
./ddcctl -d 1 -v 30or./ddcctl -d 1 -v 1. I have tried running in single monitor mode and have had the same results.I'm not sure what to try from here. Any suggestions?
@bargald commented on GitHub (Oct 12, 2020):
brightness doesn't work, volume does
@cstrouse commented on GitHub (Oct 26, 2020):
Brightness and volume work out of the box. This is a hackintosh'd Dell PowerEdge T30 using iMac17,1 SMBIOS and running 10.15.7 and 11.0.1.
@Daandelange commented on GitHub (Jan 21, 2021):
Writing works out of the box, thanks a lot ! (shows as
PL2792Q)Volume was instant, for brightness to work I had to reboot with the screen connected (probably nvram related).
Read doesn't seem to work at all.
And for easy copy/paste :
@bargald commented on GitHub (Jan 23, 2021):
everything works for me now on build 721
@lucadiliello commented on GitHub (Mar 10, 2021):
Works with both monitors. However, I have an issue when using both monitors and the Mac in closed lid mode. After having closed the lid, if I connect both monitors very quickly, the Mac freezes. To make the Mac work again, I have to disconnect and connect again the ASUS monitor (no restart required).
@waydabber commented on GitHub (Aug 25, 2021):
I'll close this issue as it served its purpose. Individual monitor problems with the new v3.0.0 version and later can be reported in separate issues. Thank you all for the contribution!