[GH-ISSUE #434] no support Viewsonic VX3211-4K #346

Closed
opened 2026-05-05 05:48:01 -06:00 by gitea-mirror · 8 comments
Owner

Originally created by @jeske on GitHub (May 2, 2021).
Original GitHub issue: https://github.com/MonitorControl/MonitorControl/issues/434

image

This is a Viewsonic VX3211-4K, not recognized. The monitor has DDC/CI support of some kind (it's turned on in the on screen menu)..

I did some searching, but couldn't easily find any documentation of the DDC commands supported. I'll keep looking.

Originally created by @jeske on GitHub (May 2, 2021). Original GitHub issue: https://github.com/MonitorControl/MonitorControl/issues/434 <img width="654" alt="image" src="https://user-images.githubusercontent.com/15093/116798982-2bc28100-aab2-11eb-9a00-d32508cea91c.png"> This is a Viewsonic VX3211-4K, not recognized. The monitor has DDC/CI support of some kind (it's turned on in the on screen menu).. I did some searching, but couldn't easily find any documentation of the DDC commands supported. I'll keep looking.
gitea-mirror 2026-05-05 05:48:01 -06:00
Author
Owner

@milosivanovic commented on GitHub (May 11, 2021):

Are you using M1 by any chance? If so, MonitorControl doesn't work on M1 yet as per https://github.com/MonitorControl/MonitorControl/issues/323.

I have a (different) supported monitor that also shows up as Unknown on M1 but it worked on my previous Intel-based MacBook.

<!-- gh-comment-id:838045425 --> @milosivanovic commented on GitHub (May 11, 2021): Are you using M1 by any chance? If so, MonitorControl doesn't work on M1 yet as per https://github.com/MonitorControl/MonitorControl/issues/323. I have a (different) supported monitor that also shows up as Unknown on M1 but it worked on my previous Intel-based MacBook.
Author
Owner

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

Hi, please test one of the latest 3.0.0 betas with M1 support and report back if it works + please close the issue. Thank you!

<!-- gh-comment-id:901668467 --> @waydabber commented on GitHub (Aug 19, 2021): Hi, please test one of the latest 3.0.0 betas with M1 support and report back if it works + please close the issue. Thank you!
Author
Owner

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

Hi, we have relased the 3.0.0 version. Could you please test if this issue is resolved and report back? Thank you!

<!-- gh-comment-id:903128666 --> @waydabber commented on GitHub (Aug 21, 2021): Hi, we have relased the [3.0.0 version](https://github.com/MonitorControl/MonitorControl/releases/tag/v3.0.0-rc1). Could you please test if this issue is resolved and report back? Thank you!
Author
Owner

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

I'll close this one since it should be solved. If there is any issue with this, please feel free to comment and ask for a reopen! Thank you!

<!-- gh-comment-id:905380369 --> @waydabber commented on GitHub (Aug 25, 2021): I'll close this one since it should be solved. If there is any issue with this, please feel free to comment and ask for a reopen! Thank you!
Author
Owner

@jeske commented on GitHub (Aug 26, 2021):

Just checking in. I installed 3.0.0 on my M1 Mac Mini, and it correctly detects and controls both brightness and volume on my Viewsonic VX3211-4K display.

The only oddness i noticed, is that in the displays panel, the "use hardware DDC control" option is unchecked and greyed out. I would expect it either to be checked and greyed out, or not greyed out at all.. since it is obviously using DDC to control my display.

Maybe instead of meaning to "use ddc control" this option means to "use hardware vs software ddc control"?

image

<!-- gh-comment-id:906783973 --> @jeske commented on GitHub (Aug 26, 2021): Just checking in. I installed 3.0.0 on my M1 Mac Mini, and it correctly detects and controls both brightness and volume on my Viewsonic VX3211-4K display. The only oddness i noticed, is that in the displays panel, the "use hardware DDC control" option is unchecked and greyed out. I would expect it either to be checked and greyed out, or not greyed out at all.. since it is obviously using DDC to control my display. Maybe instead of meaning to "use ddc control" this option means to "use hardware vs software ddc control"? ![image](https://user-images.githubusercontent.com/15093/131043947-08b5d6b2-76f5-49a5-8e73-b46ca654d90e.png)
Author
Owner

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

Hi @jeske - can you please help me by describing what kind of connection do you use with your display? Do you use HDMI or USB-C? Thank you!

<!-- gh-comment-id:906979418 --> @waydabber commented on GitHub (Aug 27, 2021): Hi @jeske - can you please help me by describing what kind of connection do you use with your display? Do you use HDMI or USB-C? Thank you!
Author
Owner

@jeske commented on GitHub (Aug 27, 2021):

HDMI

<!-- gh-comment-id:907241981 --> @jeske commented on GitHub (Aug 27, 2021): HDMI
Author
Owner

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

@jeske, I'd advise to use the USB-C port if possible on your M1 mini as it allows for hardware display brightness control using DDC. Both the 2018 Intel mini and the new M1 mini blocks DDC communication through the HDMI port so we use a technique called gamma table manipulation to dim the brightness instead in this case. This has great results but it is better to use hardware controls and even better to combine the two methods (you can do this by enabling "Further lower brightness via software dimming").

Hope this helps!

<!-- gh-comment-id:907424931 --> @waydabber commented on GitHub (Aug 27, 2021): @jeske, I'd advise to use the USB-C port if possible on your M1 mini as it allows for hardware display brightness control using DDC. Both the 2018 Intel mini and the new M1 mini blocks DDC communication through the HDMI port so we use a technique called gamma table manipulation to dim the brightness instead in this case. This has great results but it is better to use hardware controls and even better to combine the two methods (you can do this by enabling "Further lower brightness via software dimming"). Hope this helps!
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/MonitorControl#346
No description provided.