github-starred/MonitorControl

Fork 0

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

[GH-ISSUE #427] No sound from the monitor, just stops working randomly #340

New issue

Closed

opened 2026-05-05 05:46:53 -06:00 by gitea-mirror · 18 comments

gitea-mirror commented

2026-05-05 05:46:53 -06:00

Owner

Originally created by @tierpinho on GitHub (Apr 21, 2021).
Original GitHub issue: https://github.com/MonitorControl/MonitorControl/issues/427

Checklist

I have searched for existing issues
I have looked through the wiki
I have updated MonitorControl to the latest version

Describe the bug
The Monitor Control software works in terms of making the volume UI go up/down but the actual sound from the monitor just stops working. If I switch back the laptop volume, it works fine.

To Reproduce
Tap the volume buttons and nothing works.

Expected behaviour
The keyboard buttons should enable the function of volume (+/-) and sound should be heard.

Environment Information (please complete the following information):

macOS version: OSX 11.2.3
MonitorControl version: Latest
Monitor(s): LG49WL95

Originally created by @tierpinho on GitHub (Apr 21, 2021). Original GitHub issue: https://github.com/MonitorControl/MonitorControl/issues/427 **Checklist**  - [x] I have searched for existing issues - [x] I have looked through [the wiki](https://github.com/MonitorControl/MonitorControl/wiki) - [x] I have updated MonitorControl to the latest version *Describe the bug* The Monitor Control software works in terms of making the volume UI go up/down but the actual sound from the monitor just stops working. If I switch back the laptop volume, it works fine. *To Reproduce* Tap the volume buttons and nothing works. *Expected behaviour* The keyboard buttons should enable the function of volume (+/-) and sound should be heard. *Environment Information (please complete the following information):* macOS version: OSX 11.2.3 MonitorControl version: Latest Monitor(s): LG49WL95

gitea-mirror

2026-05-05 05:46:53 -06:00

closed this issue
added the
bug

feedback needed from reporter
labels

gitea-mirror commented

2026-05-05 05:47:01 -06:00

Author

Owner

@wilbit commented on GitHub (Jul 29, 2021):

I happened with me on version 2.2.0.
I reverted back to 2.1.0 and issue is gone.
But, I assume it is not your case, according to the issue's timeline, you should be using version 2.1.0...

@wilbit commented on GitHub (Jul 29, 2021): I happened with me on version 2.2.0. I reverted back to 2.1.0 and issue is gone. But, I assume it is not your case, according to the issue's timeline, you should be using version 2.1.0...

gitea-mirror commented

2026-05-05 05:47:04 -06:00

Author

Owner

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

Does brightness control work well, onty the volume control has problem? Thank you!

@waydabber commented on GitHub (Aug 20, 2021): Does brightness control work well, onty the volume control has problem? Thank you!

gitea-mirror commented

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

Author

Owner

@wilbit commented on GitHub (Aug 20, 2021):

I don't use brightness control, so, I don't know.
I will test and let you know.

@wilbit commented on GitHub (Aug 20, 2021): I don't use brightness control, so, I don't know. I will test and let you know.

gitea-mirror commented

2026-05-05 05:47:10 -06:00

Author

Owner

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

Ok! I'd like to understand whether DDC control generally works or not.

@waydabber commented on GitHub (Aug 20, 2021): Ok! I'd like to understand whether DDC control generally works or not.

gitea-mirror commented

2026-05-05 05:47:14 -06:00

Author

Owner

@wilbit commented on GitHub (Aug 20, 2021):

Huh, Release 2.2.0 does not exist anymore, I cannot download binaries to check...
With my current 2.1.0, I almost have no issues.

@wilbit commented on GitHub (Aug 20, 2021): Huh, Release 2.2.0 does not exist anymore, I cannot download binaries to check... With my current 2.1.0, I almost have no issues.

gitea-mirror commented

2026-05-05 05:47:17 -06:00

Author

Owner

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

Do you have the binaries to share?

@wilbit commented on GitHub (Aug 21, 2021): Do you have the binaries to share?

gitea-mirror commented

2026-05-05 05:47:21 -06:00

Author

Owner

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

Hi, no unfortunatelly, 2.2.0 was broken, that's why it was pulled. You should wait a bit, later today (if things go well) we plan to release 3.0.0 RC1 - that's the one you should test! Thank you! :)

@waydabber commented on GitHub (Aug 21, 2021): Hi, no unfortunatelly, 2.2.0 was broken, that's why it was pulled. You should wait a bit, later today (if things go well) we plan to release 3.0.0 RC1 - that's the one you should test! Thank you! :)

gitea-mirror commented

2026-05-05 05:47:23 -06:00

Author

Owner

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

I'll close this issue for now, I hope the new 3.0.0 fixed the issue. Please feel free to comment if the issue persists so we can reopen this issue! Thank you!

@waydabber commented on GitHub (Aug 25, 2021): I'll close this issue for now, I hope the new 3.0.0 fixed the issue. Please feel free to comment if the issue persists so we can reopen this issue! Thank you!

gitea-mirror commented

2026-05-05 05:47:25 -06:00

Author

Owner

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

Yes, I have installed version 3.0.0rc1 for 2 days and don't see the issue so far.

@wilbit commented on GitHub (Aug 25, 2021): Yes, I have installed version 3.0.0rc1 for 2 days and don't see the issue so far.

gitea-mirror commented

2026-05-05 05:47:27 -06:00

Author

Owner

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

Amazing, thank you for the response!

@waydabber commented on GitHub (Aug 25, 2021): Amazing, thank you for the response!

gitea-mirror commented

2026-05-05 05:47:30 -06:00

Author

Owner

@wilbit commented on GitHub (Aug 28, 2021):

The issue exists =(

The symptoms:

Monitor control is not able to set volume level to zero. It decreases the volume level to zero according to DisplayIcon and monitor's embedded volume control window, but I still can hear sound (very quiet). Mute button works the same, it decreases the sound, but does not set to zero.
When I increase sound by monitor's controls by 1, and then decrease it to zero - I don't hear sound anymore, BUT, after that MonitorControl stops to work. According to DisplayIcon, MonitorControl changes the volume level, but it does not. And not just that, monitor's embedded controls also stops to work - they change the volume level according to embedded volume control window, but there is no any effect.
When I turn off and turn on my monitor, everything is get back to item 1.
MonitorControl's restarting changes nothing.
Back to the brightness control - it works, no issues

Info:

MonitorControl 3.0.0 Build 2869 Intel
Monitor Samsung C34J791WTI 34", connected via USB-C (previously mentioned LG by a mistake)
macOS BigSur 11.5.2

@wilbit commented on GitHub (Aug 28, 2021): The issue exists =( The symptoms: 1. Monitor control is not able to set volume level to zero. It decreases the volume level to zero according to DisplayIcon and monitor's embedded volume control window, but I still can hear sound (very quiet). Mute button works the same, it decreases the sound, but does not set to zero. 2. When I increase sound by monitor's controls by 1, and then decrease it to zero - I don't hear sound anymore, BUT, after that MonitorControl stops to work. According to DisplayIcon, MonitorControl changes the volume level, but it does not. And not just that, monitor's embedded controls also stops to work - they change the volume level according to embedded volume control window, but there is no any effect. 3. When I turn off and turn on my monitor, everything is get back to item 1. 4. MonitorControl's restarting changes nothing. 5. Back to the brightness control - it works, no issues Info: - MonitorControl 3.0.0 Build 2869 Intel - Monitor Samsung C34J791WTI 34", connected via USB-C (previously mentioned LG by a mistake) - macOS BigSur 11.5.2

gitea-mirror commented

2026-05-05 05:47:33 -06:00

Author

Owner

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

Hi,

yes, the LG 34"s are known to have issues regarding volume control. This seems to be a firmware issue. You might want to try what happens if you activate Enable Mute DDC command under Displays in the Advanced settings area (you need to enable Show advanced settings under Displays in General to have this option).

@waydabber commented on GitHub (Aug 28, 2021): Hi, yes, the LG 34"s are known to have issues regarding volume control. This seems to be a firmware issue. You might want to try what happens if you activate `Enable Mute DDC command` under Displays in the Advanced settings area (you need to enable `Show advanced settings under Displays` in General to have this option).

gitea-mirror commented

2026-05-05 05:47:36 -06:00

Author

Owner

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

See this thread as well, it's about an other LG 34" having issues with volume control: https://github.com/MonitorControl/MonitorControl/issues/170

@waydabber commented on GitHub (Aug 28, 2021): See this thread as well, it's about an other LG 34" having issues with volume control: https://github.com/MonitorControl/MonitorControl/issues/170

gitea-mirror commented

2026-05-05 05:47:38 -06:00

Author

Owner

@wilbit commented on GitHub (Aug 28, 2021):

yes, the LG 34"s are known to have issues regarding volume control. This seems to be a firmware issue. You might want to try what happens if you activate Enable Mute DDC command under Displays in the Advanced settings area (you need to enable Show advanced settings under Displays in General to have this option).

Well, Enable Mute DDC command fixes the issue with not zero volume level and makes MonitorControl "usable". But still, from time to time volume control does not work after it's set to zero. After few attempts (to zero and back) it works again.

@wilbit commented on GitHub (Aug 28, 2021): > yes, the LG 34"s are known to have issues regarding volume control. This seems to be a firmware issue. You might want to try what happens if you activate `Enable Mute DDC command` under Displays in the Advanced settings area (you need to enable `Show advanced settings under Displays` in General to have this option). Well, `Enable Mute DDC command` fixes the issue with not zero volume level and makes MonitorControl "usable". But still, from time to time volume control does not work after it's set to zero. After few attempts (to zero and back) it works again.

gitea-mirror commented

2026-05-05 05:47:40 -06:00

Author

Owner

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

You seem to have the same issue as #170 then. I plan to make a test build which does not set the volume to 0 but only uses the mute/unmute command if Enable Mute DDC is on. Maybe to make sure, I'll issue these commands repeat. That might fix the issue, but I don't have a display like this to test.

@waydabber commented on GitHub (Aug 28, 2021): You seem to have the same issue as #170 then. I plan to make a test build which does not set the volume to 0 but only uses the mute/unmute command if `Enable Mute DDC` is on. Maybe to make sure, I'll issue these commands repeat. That might fix the issue, but I don't have a display like this to test.

gitea-mirror commented

2026-05-05 05:47:41 -06:00

Author

Owner

@wilbit commented on GitHub (Aug 29, 2021):

I have updated my https://github.com/MonitorControl/MonitorControl/issues/427#issuecomment-907596011, my monitor is Samsung, not LG, @waydabber

@wilbit commented on GitHub (Aug 29, 2021): I have updated my https://github.com/MonitorControl/MonitorControl/issues/427#issuecomment-907596011, my monitor is Samsung, not LG, @waydabber

gitea-mirror commented

2026-05-05 05:47:42 -06:00

Author

Owner

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

Interesting turn of events. :)

@waydabber commented on GitHub (Aug 29, 2021): Interesting turn of events. :)

gitea-mirror commented

2026-05-05 05:47:45 -06:00

Author

Owner

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

@wilbit can you try the build posted under the https://github.com/MonitorControl/MonitorControl/issues/170 issue and report back there? We better continue the discussion in that thread. Thank you!

@waydabber commented on GitHub (Aug 30, 2021): @wilbit can you try the build posted under the https://github.com/MonitorControl/MonitorControl/issues/170 issue and report back there? We better continue the discussion in that thread. Thank you!