github-starred/MonitorControl

Fork 0

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

[GH-ISSUE #197] Display glitches and disconects #146

New issue

Closed

opened 2026-05-05 05:16:31 -06:00 by gitea-mirror · 8 comments

gitea-mirror commented

2026-05-05 05:16:31 -06:00

Owner

Originally created by @thor27 on GitHub (Apr 8, 2020).
Original GitHub issue: https://github.com/MonitorControl/MonitorControl/issues/197

When this app is enabled, sometimes I receive some weird display glitches. I couldn't record it because it doesn't happens always, but it looks like big blocks of gray pixels on the screen and some sound crackling. Sometimes it even shutdown the screen and I have to disconnect and reconnect to come back. If I disable polling it helps a bit.

Mostly what I could notice is that, with polling this happens most of the time I reduce volume or brightness as soon as I raised, and without it it happened once when waking up from sleep.

I don't know exactly what type information will be good to help with this issue, but my monitor is an ASUS MX34VQ Designo Curve Ultra-wide Curved Monitor - 34 inch, UWQHD and my Macbook is a MacBook Pro (15-inch, 2018) running macOS Catalina 10.15.4

Originally created by @thor27 on GitHub (Apr 8, 2020). Original GitHub issue: https://github.com/MonitorControl/MonitorControl/issues/197 When this app is enabled, sometimes I receive some weird display glitches. I couldn't record it because it doesn't happens always, but it looks like big blocks of gray pixels on the screen and some sound crackling. Sometimes it even shutdown the screen and I have to disconnect and reconnect to come back. If I disable polling it helps a bit. Mostly what I could notice is that, with polling this happens most of the time I reduce volume or brightness as soon as I raised, and without it it happened once when waking up from sleep. I don't know exactly what type information will be good to help with this issue, but my monitor is an ASUS MX34VQ Designo Curve Ultra-wide Curved Monitor - 34 inch, UWQHD and my Macbook is a MacBook Pro (15-inch, 2018) running macOS Catalina 10.15.4

gitea-mirror

2026-05-05 05:16:31 -06:00

closed this issue
added the
Status: Abandoned

monitor Issue
labels

gitea-mirror commented

2026-05-05 05:16:39 -06:00

Author

Owner

@kumowoon1025 commented on GitHub (Apr 9, 2020):

and some sound crackling.

Does this display have an audio connection because if not that sounds terrifying.
As far as helpful info, how you connect the display to your computer is an example.

@kumowoon1025 commented on GitHub (Apr 9, 2020): > and some sound crackling. Does this display have an audio connection because if not that sounds terrifying. As far as helpful info, how you connect the display to your computer is an example.

gitea-mirror commented

2026-05-05 05:16:41 -06:00

Author

Owner

@thor27 commented on GitHub (Apr 9, 2020):

Hi! I replaced the cable I used and the visual glitches is gone, but if you move the sound or brightness too fast the screen turns off.

My monitor has audio speakers in it. I use an HDMI cable to connect.

@thor27 commented on GitHub (Apr 9, 2020): Hi! I replaced the cable I used and the visual glitches is gone, but if you move the sound or brightness too fast the screen turns off. My monitor has audio speakers in it. I use an HDMI cable to connect.

gitea-mirror commented

2026-05-05 05:16:43 -06:00

Author

Owner

@JoniVR commented on GitHub (Apr 10, 2020):

See:
https://github.com/the0neyouseek/MonitorControl/wiki/Monitor-Troubleshooting

Unfortunately, besides from pointing you to the general troubleshooting there isn't much we can probably do about it. It could simply be a problem with the implementation of your display manufacturer.

@JoniVR commented on GitHub (Apr 10, 2020): See: https://github.com/the0neyouseek/MonitorControl/wiki/Monitor-Troubleshooting Unfortunately, besides from pointing you to the general troubleshooting there isn't much we can probably do about it. It could simply be a problem with the implementation of your display manufacturer.

gitea-mirror commented

2026-05-05 05:16:46 -06:00

Author

Owner

@kumowoon1025 commented on GitHub (Apr 11, 2020):

I actually don't understand why it works with HDMI in the first place... Where are CEC commands made? Or is it something like Macs with more than one gpu use I2c api for either and translated by gmux?

Is your laptop iGPU only or the dual gpu model? Can try DisplayPort cable instead of HDMI?

@kumowoon1025 commented on GitHub (Apr 11, 2020): I actually don't understand why it works with HDMI in the first place... Where are CEC commands made? Or is it something like Macs with more than one gpu use I2c api for either and translated by gmux? Is your laptop iGPU only or the dual gpu model? Can try DisplayPort cable instead of HDMI?

gitea-mirror commented

2026-05-05 05:16:47 -06:00

Author

Owner

@thor27 commented on GitHub (Apr 11, 2020):

It shouldn't work with HDMI?? As far as I understand about this, HDMI supports CEC just fine, I even use with my chromecast to control it with my TV remote.

it's working fine after using a newer and more modern cable. It only shows a black screen If I move the sliders too fast, but nothing happens with "normal usage". So I think this is not an issue anymore.

It's dual GPU Radeon Pro 555X 4 GB & Intel UHD Graphics 630 1536 MB
I Don't have a USB-C Display port cable to test, unfortunately.

@thor27 commented on GitHub (Apr 11, 2020): It shouldn't work with HDMI?? As far as I understand about this, HDMI supports CEC just fine, I even use with my chromecast to control it with my TV remote. it's working fine after using a newer and more modern cable. It only shows a black screen If I move the sliders too fast, but nothing happens with "normal usage". So I think this is not an issue anymore. It's dual GPU Radeon Pro 555X 4 GB & Intel UHD Graphics 630 1536 MB I Don't have a USB-C Display port cable to test, unfortunately.

gitea-mirror commented

2026-05-05 05:16:50 -06:00

Author

Owner

@kumowoon1025 commented on GitHub (Apr 11, 2020):

@thor27 I'm sorry I guess I put it in a confusing way, I mean I don't understand where CEC support is implemented in this app. It supports DDC/CI, which is a bidirectional I²C interface, which is not the same as CEC, though they do serve a lot of the same purpose. In terms of the implementation details for CEC in HDMI, I think qualitatively I can think of as many differences as I can similarities.

Anyhow, I'm glad it's working better for you, you might want to try adjusting the polling and delay according to the troubleshooting guide @JoniVR pointed you to earlier to make it even more stable.

But HDMI not working very well has been a recurring issue for a while now, and when I looked into it to see if I could help out in fixing it, I could not find the code that handled HDMI/CEC, so I would have thought it wouldn't work with HDMI connections at all, but obviously, it does, and quite well at that for many setups.

I'm thinking maybe it is the gmux chip doing protocol translation in hardware (your dual-GPU MBP has this chip, it's either an fpga or something like a 16-bit general processor That handles graphics switching, eGPU routing, etc. ), or the same API being used for both MCCS and CEC at the moment, if anyone can point me in the right direction or confirm/reject my guesses I'd be much obliged.

@kumowoon1025 commented on GitHub (Apr 11, 2020): @thor27 I'm sorry I guess I put it in a confusing way, I mean I don't understand where CEC support is implemented in this app. It supports DDC/CI, which is a bidirectional I<sup>2</sup>C interface, which is not the same as CEC, though they do serve a lot of the same purpose. In terms of the implementation details for CEC in HDMI, I think qualitatively I can think of as many differences as I can similarities. Anyhow, I'm glad it's working better for you, you might want to try adjusting the polling and delay according to the troubleshooting guide @JoniVR pointed you to earlier to make it even more stable. But HDMI not working very well has been a recurring issue for a while now, and when I looked into it to see if I could help out in fixing it, I could not find the code that handled HDMI/CEC, so I would have thought it wouldn't work with HDMI connections at all, but obviously, it does, and quite well at that for many setups. I'm thinking maybe it is the gmux chip doing protocol translation in hardware (your dual-GPU MBP has this chip, it's either an fpga or something like a 16-bit general processor That handles graphics switching, eGPU routing, etc. ), or the same API being used for both MCCS and CEC at the moment, if anyone can point me in the right direction or confirm/reject my guesses I'd be much obliged.

gitea-mirror commented

2026-05-05 05:16:52 -06:00

Author

Owner

@JoniVR commented on GitHub (Jun 21, 2020):

I'm pretty sure no CEC is implemented, only DDC for control and a private API for internal display control. HDMI is indeed a recurring issue 🙂

@JoniVR commented on GitHub (Jun 21, 2020): I'm pretty sure no CEC is implemented, only DDC for control and a private API for internal display control. HDMI is indeed a recurring issue 🙂

gitea-mirror commented

2026-05-05 05:16:55 -06:00

Author

Owner

@stale[bot] commented on GitHub (Aug 3, 2021):

Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require attention? This issue may be closed if no further activity occurs. Thank you for your contributions.

@stale[bot] commented on GitHub (Aug 3, 2021): Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require attention? This issue may be closed if no further activity occurs. Thank you for your contributions.