github-starred/MonitorControl

Fork 0

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

[GH-ISSUE #351] EIZO3895 #278

New issue

Closed

opened 2026-05-05 05:40:26 -06:00 by gitea-mirror · 4 comments

gitea-mirror commented

2026-05-05 05:40:26 -06:00

Owner

Originally created by @christianmeier on GitHub (Dec 22, 2020).
Original GitHub issue: https://github.com/MonitorControl/MonitorControl/issues/351

Originally assigned to: @waydabber on GitHub.

Hi, I can't adjust the brightness and contrast via the app.
BigSur
11.1 (20C69)
Monitor: Eizo EV3895

Is this monitor supported / how can I troubleshoot or modify the settings to get the app working.
BR C

Originally created by @christianmeier on GitHub (Dec 22, 2020). Original GitHub issue: https://github.com/MonitorControl/MonitorControl/issues/351 Originally assigned to: @waydabber on GitHub. Hi, I can't adjust the brightness and contrast via the app. BigSur 11.1 (20C69) Monitor: Eizo EV3895 Is this monitor supported / how can I troubleshoot or modify the settings to get the app working. BR C

gitea-mirror

2026-05-05 05:40:26 -06:00

closed this issue
added the
duplicate

monitor Issue
labels

gitea-mirror commented

2026-05-05 05:40:31 -06:00

Author

Owner

@JoniVR commented on GitHub (Dec 27, 2020):

As the issue template (which you seem to have removed?) notes, check out the Monitor Troubleshooting wiki.

@JoniVR commented on GitHub (Dec 27, 2020): As the issue template (which you seem to have removed?) notes, check out the [Monitor Troubleshooting](https://github.com/MonitorControl/MonitorControl/wiki/Monitor-Troubleshooting) wiki.

gitea-mirror commented

2026-05-05 05:40:34 -06:00

Author

Owner

@christianmeier commented on GitHub (Dec 28, 2020):

Hi Joni, thank you for getting back to me - Sorry I did not find the troubleshooting template.
Installed the the tool and it also does not change any parameter.

christianmeier@iMac ~/scripts/ddcctl master  ./ddcctl -d 1 -b 40 -w 20000 ✔  1187  09:56:34
D: NSScreen #1892440164 (3840x1600 0°) 111.00 DPI
I: found 1 external display
I: polling display 1's EDID
I: got edid.serial: 20776100
I: got edid.name: EV3895
D: action: b: 40
D: setting VCP control #16 => 40
E: Failed to send DDC command!

—> Failed to send| I use the DisplayPort on my AMD RX 580 gpu / I run a Hackintosh.

I write an email to Eizo and ask them if they changed the specification. May this type of monitor will not work because the manual says that the contract
and brightness will automatically adjusted.

Thank you for you help - If I get any feedback from EIZO I will post it.

Best regards,
Christian

On 27 Dec 2020, at 20:39, Joni Van Roost notifications@github.com wrote:

As the issue template (which you seem to have removed?) notes, check out the Monitor Troubleshooting https://github.com/MonitorControl/MonitorControl/wiki/Monitor-Troubleshooting wiki.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/MonitorControl/MonitorControl/issues/351#issuecomment-751507897, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABZVEWZRK7ZAENA7GE4EL73SW6EODANCNFSM4VFNGVBA.

@christianmeier commented on GitHub (Dec 28, 2020): Hi Joni, thank you for getting back to me - Sorry I did not find the troubleshooting template. Installed the the tool and it also does not change any parameter. christianmeier@iMac ~/scripts/ddcctl master  ./ddcctl -d 1 -b 40 -w 20000 ✔  1187  09:56:34 D: NSScreen #1892440164 (3840x1600 0°) 111.00 DPI I: found 1 external display I: polling display 1's EDID I: got edid.serial: 20776100 I: got edid.name: EV3895 D: action: b: 40 D: setting VCP control #16 => 40 E: Failed to send DDC command! —> Failed to send| I use the DisplayPort on my AMD RX 580 gpu / I run a Hackintosh. I write an email to Eizo and ask them if they changed the specification. May this type of monitor will not work because the manual says that the contract and brightness will automatically adjusted. Thank you for you help - If I get any feedback from EIZO I will post it. Best regards, Christian > On 27 Dec 2020, at 20:39, Joni Van Roost <notifications@github.com> wrote: > > > As the issue template (which you seem to have removed?) notes, check out the Monitor Troubleshooting <https://github.com/MonitorControl/MonitorControl/wiki/Monitor-Troubleshooting> wiki. > > — > You are receiving this because you authored the thread. > Reply to this email directly, view it on GitHub <https://github.com/MonitorControl/MonitorControl/issues/351#issuecomment-751507897>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABZVEWZRK7ZAENA7GE4EL73SW6EODANCNFSM4VFNGVBA>. >

gitea-mirror commented

2026-05-05 05:40:36 -06:00

Author

Owner

@gustavneustadt commented on GitHub (Jan 4, 2021):

I have the EV2785 and because of the same reason I recently had contact with the german support.

German:
wir verwenden seit einigen Jahren nur noch Controller ohne DDC/CI. Steuerungsaufgaben sind nur über USB und mit unserer Software Screen InStyle möglich. Ich gehe davon aus, dass die anderen Hersteller die Kommunikation mit deren Software ebenfalls über USB vornehemen. Das /CI hat also kaum noch eine Bedeutung.
DDC, also die einseitige Kommunikation wird natürlich weiterhin verwendet. Alle Monitore sind also Plug-and-Play. Sie können über das Signalkabel aber keine Steurungsfunktionen übertragen.

English:
we have been using only controllers without DDC/CI for some years now. Control tasks are only possible via USB and with our Screen InStyle software. I assume that the other manufacturers also communicate with their software via USB. So the /CI has hardly any meaning anymore.
DDC, the one-way communication, is of course still used. So all monitors are plug-and-play. However, they cannot transmit any control functions via the signal cable.

tl;dr
We dont care – use our windows software.

I think it may be possible to reverse engineer the usb protocoll. It may be nothing different than DDC.
I tried using ddcctl via usb-c but had no luck.

EDIT:

ddcutil has support for MCCS – for such monitors from EIZO. Maybe implement it in monitorControl?

@gustavneustadt commented on GitHub (Jan 4, 2021): I have the EV2785 and because of the same reason I recently had contact with the german support. German: wir verwenden seit einigen Jahren nur noch Controller ohne DDC/CI. Steuerungsaufgaben sind nur über USB und mit unserer Software Screen InStyle möglich. Ich gehe davon aus, dass die anderen Hersteller die Kommunikation mit deren Software ebenfalls über USB vornehemen. Das /CI hat also kaum noch eine Bedeutung. DDC, also die einseitige Kommunikation wird natürlich weiterhin verwendet. Alle Monitore sind also Plug-and-Play. Sie können über das Signalkabel aber keine Steurungsfunktionen übertragen. English: we have been using only controllers without DDC/CI for some years now. Control tasks are only possible via USB and with our Screen InStyle software. I assume that the other manufacturers also communicate with their software via USB. So the /CI has hardly any meaning anymore. DDC, the one-way communication, is of course still used. So all monitors are plug-and-play. However, they cannot transmit any control functions via the signal cable. tl;dr `We dont care – use our windows software.` I think it may be possible to reverse engineer the usb protocoll. It may be nothing different than DDC. I tried using [ddcctl](https://github.com/kfix/ddcctl) via usb-c but had no luck. __EDIT:__ [ddcutil](http://www.ddcutil.com/usb/) has support for MCCS – for such monitors from EIZO. Maybe implement it in monitorControl?

gitea-mirror commented

2026-05-05 05:40:38 -06:00

Author

Owner

@waydabber commented on GitHub (Aug 21, 2021):

We'd like to solve this issue here:

https://github.com/MonitorControl/MonitorControl/issues/364

I'll close this thread so we don't have a duplicate issue on this. Please feel free to follow the other issue and contribute with your commands or when the time comes by testing!

Also - what I would like to know if these USB MCCS EIZO displays are controlled by the macOS built in brightness slider or not (as they should be using the same protocol as Apple's displays)? Please let me know in the other thread! Thank you!

@waydabber commented on GitHub (Aug 21, 2021): We'd like to solve this issue here: https://github.com/MonitorControl/MonitorControl/issues/364 I'll close this thread so we don't have a duplicate issue on this. Please feel free to follow the other issue and contribute with your commands or when the time comes by testing! Also - what I would like to know if these USB MCCS EIZO displays are controlled by the macOS built in brightness slider or not (as they should be using the same protocol as Apple's displays)? Please let me know in the other thread! Thank you!