github-starred/MonitorControl

Fork 0

mirror of https://github.com/MonitorControl/MonitorControl.git synced 2026-05-15 14:15:55 -06:00

[GH-ISSUE #6] Identical monitors cannot be distinguished #4

New issue

Closed

opened 2026-05-05 04:40:41 -06:00 by gitea-mirror · 5 comments

gitea-mirror commented

2026-05-05 04:40:41 -06:00

Owner

Originally created by @marknotton on GitHub (Jan 6, 2018).
Original GitHub issue: https://github.com/MonitorControl/MonitorControl/issues/6

Originally assigned to: @the0neyouseek on GitHub.

I was surprised to find that my VP2770-LED monitors supported DDC/CI; allowing your app to partially work.

However, where I have two identical monitors, it seems the app can't tell them apart. In the menu bar, it lists both the monitors. They have the same name. It doesn't matter what monitor I adjust the brightness on, it only adjusts one monitor (my primary display).

Also, the "Default" button wasn't working for me.

Let me know if there is any more information you'd like to know. Or any other tests I can do to help. Thanks for all your time and efforts on this.

Originally created by @marknotton on GitHub (Jan 6, 2018). Original GitHub issue: https://github.com/MonitorControl/MonitorControl/issues/6 Originally assigned to: @the0neyouseek on GitHub. I was surprised to find that my VP2770-LED monitors supported DDC/CI; allowing your app to partially work. However, where I have two identical monitors, it seems the app can't tell them apart. In the menu bar, it lists both the monitors. They have the same name. It doesn't matter what monitor I adjust the brightness on, it only adjusts one monitor (my primary display). _Also, the "Default" button wasn't working for me._ Let me know if there is any more information you'd like to know. Or any other tests I can do to help. Thanks for all your time and efforts on this.

gitea-mirror added the

bug

label 2026-05-05 04:40:41 -06:00

gitea-mirror referenced this issue

2026-05-05 04:40:41 -06:00

[GH-ISSUE #4] Lint #5

gitea-mirror closed this issue

2026-05-05 04:40:45 -06:00

gitea-mirror commented

2026-05-05 04:40:50 -06:00

Author

Owner

@the0neyouseek commented on GitHub (Jan 6, 2018):

Hi @marknotton ,

Thanks for the detailed issuer, I'll look into it and get back to you soon.

@the0neyouseek commented on GitHub (Jan 6, 2018): Hi @marknotton , Thanks for the detailed issuer, I'll look into it and get back to you soon.

gitea-mirror commented

2026-05-05 04:40:52 -06:00

Author

Owner

@the0neyouseek commented on GitHub (Jan 7, 2018):

Hi again @marknotton ,

I've just pushed a commit that will hopefully fix your issue, could you test if it works now? If you don't have XCode, please tell me and I'll send you a dmg of the build.

Have a nice day.

@the0neyouseek commented on GitHub (Jan 7, 2018): Hi again @marknotton , I've just pushed a commit that will hopefully fix your issue, could you test if it works now? If you don't have XCode, please tell me and I'll send you a `dmg` of the build. Have a nice day.

gitea-mirror commented

2026-05-05 04:40:55 -06:00

Author

Owner

@marknotton commented on GitHub (Jan 7, 2018):

Hi @the0neyouseek, you work fast!

I don't have any experience with XCode unfortunately. I have it installed, and I've assigned my dev certificate to the project. But I'm unable to run anything. I'm getting this:

diff: /Podfile.lock: No such file or directory
diff: /Manifest.lock: No such file or directory
error: The sandbox is not in sync with the Podfile.lock. Run 'pod install' or update your CocoaPods installation.

Is there an easy fix for this? Do I need to install/download any dependancies?

Alternatively, you might have to send that dmg of the build.

Thanks :)

@marknotton commented on GitHub (Jan 7, 2018): Hi @the0neyouseek, you work fast! I don't have any experience with XCode unfortunately. I have it installed, and I've assigned my dev certificate to the project. But I'm unable to run anything. I'm getting this: ``` diff: /Podfile.lock: No such file or directory diff: /Manifest.lock: No such file or directory error: The sandbox is not in sync with the Podfile.lock. Run 'pod install' or update your CocoaPods installation. ``` Is there an easy fix for this? Do I need to install/download any dependancies? Alternatively, you might have to send that dmg of the build. Thanks :)

gitea-mirror commented

2026-05-05 04:40:58 -06:00

Author

Owner

@the0neyouseek commented on GitHub (Jan 8, 2018):

Hi,

Yes you need to have Cocoapods installed and then launch the command

$ pod install

from your terminal at the root of the projet.
I'll send you a dmg tonight (~7pm GMT+1) if you still need it.

Edit : Here's a link to the dmg file.

@the0neyouseek commented on GitHub (Jan 8, 2018): Hi, Yes you need to have [Cocoapods](https://cocoapods.org/) installed and then launch the command ```sh $ pod install ``` from your terminal at the root of the projet. I'll send you a dmg tonight ([~7pm GMT+1](https://www.timeanddate.com/worldclock/france/paris)) if you still need it. **Edit :** Here's a link to the [dmg file](https://we.tl/KNL6t7jHew).

gitea-mirror commented

2026-05-05 04:41:00 -06:00

Author

Owner

@the0neyouseek commented on GitHub (Jan 13, 2018):

So, after looking a bit more on how to fix this I found this issue on the DDCCTL repo.
As it seems to be an upstream issue, there's nothing much I can do, so I'm closing this for now and will update if there's any change from DDCCTL.

@the0neyouseek commented on GitHub (Jan 13, 2018): So, after looking a bit more on how to fix this I found this [issue](https://github.com/kfix/ddcctl/issues/17) on the DDCCTL repo. As it seems to be an upstream issue, there's nothing much I can do, so I'm closing this for now and will update if there's any change from DDCCTL.