github-starred/MonitorControl

Fork 0

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

[GH-ISSUE #107] No mute after update to version 1.6.0 #78

New issue

Closed

opened 2026-05-05 04:58:37 -06:00 by gitea-mirror · 11 comments

gitea-mirror commented

2026-05-05 04:58:37 -06:00

Owner

Originally created by @iBubelo on GitHub (Jun 22, 2019).
Original GitHub issue: https://github.com/MonitorControl/MonitorControl/issues/107

The MonitorControl 1.5.2 used to work just perfectly on my AOC Q2577W. But since I've updated to 1.6.0 I can't mute the sound. Behavior is similar to #94.
Reverting to 1.5.2 fixed the issue.

Originally created by @iBubelo on GitHub (Jun 22, 2019). Original GitHub issue: https://github.com/MonitorControl/MonitorControl/issues/107 The MonitorControl 1.5.2 used to work just perfectly on my AOC Q2577W. But since I've updated to 1.6.0 I can't mute the sound. Behavior is similar to #94. Reverting to 1.5.2 fixed the issue.

gitea-mirror

2026-05-05 04:58:37 -06:00

closed this issue
added the
bug

in progress
labels

gitea-mirror commented

2026-05-05 04:58:42 -06:00

Author

Owner

@JoniVR commented on GitHub (Jun 22, 2019):

Could perhaps be that your monitor doesn't support the ddc mute command implemented in #96. Maybe we could work a fallback into the advanced prefs panel but it'll probably for later versions then.

I'll try to provide a test build in the future but I'm currently too swamped with other stuff.

@JoniVR commented on GitHub (Jun 22, 2019): Could perhaps be that your monitor doesn't support the ddc mute command implemented in #96. Maybe we could work a fallback into the advanced prefs panel but it'll probably for later versions then. I'll try to provide a test build in the future but I'm currently too swamped with other stuff.

gitea-mirror commented

2026-05-05 04:58:44 -06:00

Author

Owner

@iBubelo commented on GitHub (Jun 22, 2019):

Thank you for swift reply! I'll be happy to help with testing.

@iBubelo commented on GitHub (Jun 22, 2019): Thank you for swift reply! I'll be happy to help with testing.

gitea-mirror commented

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

Author

Owner

@robertbressi commented on GitHub (Jul 5, 2019):

Actually, I noticed there's one case which still doesn't work properly - that is, going down from 1 bar to mute.

What should happen is:

At 2 bars, press down = 1 bar
At 1 bar, press down = mute (crossed out speaker icon)
At mute, press up = 1 bar
At 1 bar, press up = 2 bars

What actually happens is:

At 2 bars, press down = 1 bar
At 1 bar, press down = 0 bars
At 0 bars, press down = mute (crossed out speaker icon)
At mute, press up = 1 bar
At 1 bar, press up = 2 bars

@iBubelo: Does the above explanation match your experienced behavior?

The other thing is that, on my Samsung monitor, 1 bar = 9 volume, 0 bars = 3 volume, so the volume control doesn't allow me to decrease the volume as much as would be possible.

@robertbressi commented on GitHub (Jul 5, 2019): Actually, I noticed there's one case which still doesn't work properly - that is, going down from 1 bar to mute. What should happen is: - At 2 bars, press down = 1 bar - At 1 bar, press down = mute (crossed out speaker icon) - At mute, press up = 1 bar - At 1 bar, press up = 2 bars What actually happens is: - At 2 bars, press down = 1 bar - At 1 bar, press down = 0 bars - At 0 bars, press down = mute (crossed out speaker icon) - At mute, press up = 1 bar - At 1 bar, press up = 2 bars @iBubelo: Does the above explanation match your experienced behavior? The other thing is that, on my Samsung monitor, 1 bar = 9 volume, 0 bars = 3 volume, so the volume control doesn't allow me to decrease the volume as much as would be possible.

gitea-mirror commented

2026-05-05 04:58:48 -06:00

Author

Owner

@innovia commented on GitHub (Aug 13, 2019):

i have the dell u3419 can't use mute at tall but running the command line utility ddcctl -d 1 -v 0 works

@innovia commented on GitHub (Aug 13, 2019): i have the dell u3419 can't use mute at tall but running the command line utility ddcctl -d 1 -v 0 works

gitea-mirror commented

2026-05-05 04:58:50 -06:00

Author

Owner

@robertbressi commented on GitHub (Aug 13, 2019):

@innovia: What happens if you run ddcctl -d 1 -m \?

@robertbressi commented on GitHub (Aug 13, 2019): @innovia: What happens if you run `ddcctl -d 1 -m \?`

gitea-mirror commented

2026-05-05 04:58:52 -06:00

Author

Owner

@innovia commented on GitHub (Aug 20, 2019):

@scorpiondev

 ddcctl -d 1 -m
D: NSScreen #724074197 (3440x1440 0°) 109.00 DPI
I: found 1 external display
I: polling display 1's EDID
I: got edid.serial: B0GP5T2
I: got edid.name: DELL U3419W

@innovia commented on GitHub (Aug 20, 2019): @scorpiondev ``` ddcctl -d 1 -m D: NSScreen #724074197 (3440x1440 0°) 109.00 DPI I: found 1 external display I: polling display 1's EDID I: got edid.serial: B0GP5T2 I: got edid.name: DELL U3419W ```

gitea-mirror commented

2026-05-05 04:58:54 -06:00

Author

Owner

@robertbressi commented on GitHub (Aug 20, 2019):

@innovia: You need to add the /? to the end of that command so we can see the results :)

@robertbressi commented on GitHub (Aug 20, 2019): @innovia: You need to add the ` /?` to the end of that command so we can see the results :)

gitea-mirror commented

2026-05-05 04:58:55 -06:00

Author

Owner

@innovia commented on GitHub (Aug 21, 2019):

@scorpiondev

➜ ddcctl -d 1 -m \?
D: NSScreen #724074197 (3440x1440 0°) 109.00 DPI
I: found 1 external display
I: polling display 1's EDID
I: got edid.serial: B0GP5T2
I: got edid.name: DELL U3419W
D: action: m: ?
D: querying VCP control: #141 =?
I: VCP control #141 (0x8d) = current: 30, max: 100

@innovia commented on GitHub (Aug 21, 2019): @scorpiondev ``` ➜ ddcctl -d 1 -m \? D: NSScreen #724074197 (3440x1440 0°) 109.00 DPI I: found 1 external display I: polling display 1's EDID I: got edid.serial: B0GP5T2 I: got edid.name: DELL U3419W D: action: m: ? D: querying VCP control: #141 =? I: VCP control #141 (0x8d) = current: 30, max: 100 ```

gitea-mirror commented

2026-05-05 04:58:57 -06:00

Author

Owner

@robertbressi commented on GitHub (Aug 21, 2019):

@innovia, thanks for that - if I were to take a wild guess, it looks like your monitor maps the mute control to speaker volume, as evidenced by current: 30, max: 100 as compared to my monitor (output below) where the same control has current: 2, max: 2 (value of 1 is muted, value of 2 is not).

➜ ddcctl -d 1 -m \?
D: NSScreen #188974799 (3440x1440 0°) 110.00 DPI
I: found 1 external display
I: polling display 1's EDID
I: got edid.name: C34J79x
I: got edid.serial: HTRK800598
D: action: m: ?
D: querying VCP control: #141 =?
I: VCP control #141 (0x8d) = current: 2, max: 2

@JoniVR: I'm happy to work on both the issue I pointed out in my previous post (feel free to raise a separate issue if you see the need), and also check whether the mute command value has a max above 2 and fallback to setting the speaker volume to 0 - I can get to these later this week or on the weekend.

@robertbressi commented on GitHub (Aug 21, 2019): @innovia, thanks for that - if I were to take a wild guess, it looks like your monitor maps the mute control to speaker volume, as evidenced by **current: 30, max: 100** as compared to my monitor (output below) where the same control has **current: 2, max: 2** (value of 1 is muted, value of 2 is not). ``` ➜ ddcctl -d 1 -m \? D: NSScreen #188974799 (3440x1440 0°) 110.00 DPI I: found 1 external display I: polling display 1's EDID I: got edid.name: C34J79x I: got edid.serial: HTRK800598 D: action: m: ? D: querying VCP control: #141 =? I: VCP control #141 (0x8d) = current: 2, max: 2 ``` @JoniVR: I'm happy to work on both the issue I pointed out in my previous post (feel free to raise a separate issue if you see the need), and also check whether the mute command value has a max above 2 and fallback to setting the speaker volume to 0 - I can get to these later this week or on the weekend.

gitea-mirror commented

2026-05-05 04:58:59 -06:00

Author

Owner

@JoniVR commented on GitHub (Aug 22, 2019):

@scorpiondev Sounds good to me, no pressure though, feel free to do it whenever you have time or feel like it :)

@JoniVR commented on GitHub (Aug 22, 2019): @scorpiondev Sounds good to me, no pressure though, feel free to do it whenever you have time or feel like it :)

gitea-mirror commented

2026-05-05 04:59:02 -06:00

Author

Owner

@innovia commented on GitHub (Feb 18, 2020):

Its working for me - thanks for the fix

@innovia commented on GitHub (Feb 18, 2020): Its working for me - thanks for the fix

gitea-mirror referenced this issue

2026-05-05 07:02:42 -06:00

[PR #78] [MERGED] Stop using agvtool. #1032