[GH-ISSUE #835] [Aorus CV27Q] Monitor connection crashes after finite amount of inputs/transitions #530

New issue

Closed

opened 2026-05-05 06:11:32 -06:00 by gitea-mirror · 1 comment

gitea-mirror commented

2026-05-05 06:11:32 -06:00

Owner

Originally created by @desmondw on GitHub (Dec 7, 2021).
Original GitHub issue: https://github.com/MonitorControl/MonitorControl/issues/835

Originally assigned to: @waydabber on GitHub.

Before opening the issue, have you...?

Searched for existing issues
Read through the Monitor-Troubleshooting Wiki
Updated MonitorControl to the latest version (if applicable)

Describe the issue

Both the brightness and volume slider initially work but then the monitor connection crashes. To reproduce:

Increase or decrease the volume or brightness slider through either the keyboard or the UI.
Note that initially it works as expected
Continue to slide value up and down a couple times and notice that the OSD still reflects your input, but that the brightness or volume has stopped changing
Wait a couple of seconds for the connection to the monitor to die (which requires unplugging and plugging back in to reconnect)

Note that changing the values successfully and then waiting does not instigate the issue. It instead appears to occur after a specific number of inputs or transition amounts.

For example, I lowered the brightness with the UI slider, waited a minute, then adjusted with the brightness via keyboard before seeing the issue appear again. In this case it appeared to require less keyboard inputs, suggesting a shared input/transition cap before the crash occurs.

Expected behavior

Not crash the monitor

Anything else?

I was able to use ddcctl without any issue, repeatedly toggling brightness between 10 and 90 - e.g. ddcctl -d 1 -b 10

Monitor Cable(s)/Connection(s): MacBook Pro (16-inch, 2019) -> USB-C Digital AV Multiport Adapter -> 4k HDMI 2.1 cable -> Aorus CV27Q
Video of bug
Monitor specs

Environment Information (please complete the following information)

- macOS version: 12.0.1 Monterey
- Mac model: MacBook Pro (16-inch, 2019)
- MonitorControl version: v4.0.2
- Monitor(s): Aorus CV27Q
- Monitor Cable(s)/Connection(s): MacBook Pro (16-inch, 2019) -> USB-C Digital AV Multiport Adapter -> 4k HDMI 2.1 cable -> Aorus CV27Q
- Apple Silicon/M1 (yes or no): no

Originally created by @desmondw on GitHub (Dec 7, 2021). Original GitHub issue: https://github.com/MonitorControl/MonitorControl/issues/835 Originally assigned to: @waydabber on GitHub. ### Before opening the issue, have you...? - [X] Searched for existing issues - [X] Read through [the Monitor-Troubleshooting Wiki](https://github.com/MonitorControl/MonitorControl/wiki/Monitor-Troubleshooting) - [X] Updated MonitorControl to the latest version (if applicable) ### Describe the issue Both the brightness and volume slider initially work but then the monitor connection crashes. To reproduce: 1. Increase or decrease the volume or brightness slider through either the keyboard or the UI. 2. Note that initially it works as expected 3. Continue to slide value up and down a couple times and notice that the OSD still reflects your input, but that the brightness or volume has stopped changing 4. Wait a couple of seconds for the connection to the monitor to die (which requires unplugging and plugging back in to reconnect) Note that changing the values successfully and then waiting does not instigate the issue. It instead appears to occur after a specific number of inputs or transition amounts. For example, I lowered the brightness with the UI slider, waited a minute, then adjusted with the brightness via keyboard before seeing the issue appear again. In this case it appeared to require less keyboard inputs, suggesting a shared input/transition cap before the crash occurs. ### Expected behavior Not crash the monitor ### Anything else? I was able to use [ddcctl](https://github.com/kfix/ddcctl) without any issue, repeatedly toggling brightness between 10 and 90 - e.g. `ddcctl -d 1 -b 10` - Monitor Cable(s)/Connection(s): MacBook Pro (16-inch, 2019) -> [USB-C Digital AV Multiport Adapter](https://www.apple.com/shop/product/MUF82AM/A/usb-c-digital-av-multiport-adapter) -> [4k HDMI 2.1 cable](https://www.amazon.com/gp/product/B073RBWVBL) -> [Aorus CV27Q](https://www.amazon.com/gp/product/B07X3Y9VTS/) - [Video of bug](https://drive.google.com/file/d/11QkJJU2fOpaYt7Kc2qNJmbJhR26y2_Si/view?usp=sharing) - Monitor specs ![monitor](https://user-images.githubusercontent.com/1052705/145084854-d99c2a8d-2fa1-4a53-90be-ef712cbb685a.jpg) ### Environment Information (please complete the following information) ```markdown - macOS version: 12.0.1 Monterey - Mac model: MacBook Pro (16-inch, 2019) - MonitorControl version: v4.0.2 - Monitor(s): Aorus CV27Q - Monitor Cable(s)/Connection(s): MacBook Pro (16-inch, 2019) -> USB-C Digital AV Multiport Adapter -> 4k HDMI 2.1 cable -> Aorus CV27Q - Apple Silicon/M1 (yes or no): no ```

gitea-mirror

2026-05-05 06:11:32 -06:00

closed this issue
added the
monitor Issue
label

gitea-mirror commented

2026-05-05 06:11:39 -06:00

Author

Owner

@waydabber commented on GitHub (Dec 8, 2021):

Hi, you might want to try disabling Enable smooth brightness transitions as that will severely decrease the number of commands sent to the display, and avoid using the slider, use instead the keyboard, or if you use the slider, do not scroll it but point and click to a direct value. If the display is having a firmware problem with handling too many ddc requests (possibly a register is overflowing inside), this might help.

@waydabber commented on GitHub (Dec 8, 2021): Hi, you might want to try disabling `Enable smooth brightness transitions` as that will severely decrease the number of commands sent to the display, and avoid using the slider, use instead the keyboard, or if you use the slider, do not scroll it but point and click to a direct value. If the display is having a firmware problem with handling too many ddc requests (possibly a register is overflowing inside), this might help.

gitea-mirror referenced this issue

2026-05-05 07:05:16 -06:00

[PR #550] [MERGED] 3.0.0 bug fixes and some enhancements #1124