mirror of
https://github.com/MonitorControl/MonitorControl.git
synced 2026-05-15 14:15:55 -06:00
[GH-ISSUE #1822] Slide volume control to 0(it mutes) , Slide to any value more than 0 , it remains muted until you unmute using monitor buttons #1004
Labels
No labels
Status: Abandoned
arm64
beta
beta
bug
done
duplicate
enhancement
feedback needed from reporter
in progress
invalid
investigating
known Issue
monitor Issue
pull-request
translation
unable to reproduce
unreleased
x86
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/MonitorControl#1004
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @Mohamed-Muzamil-Personal on GitHub (Dec 5, 2025).
Original GitHub issue: https://github.com/MonitorControl/MonitorControl/issues/1822
Before opening the issue, have you...?
Describe the bug
When the volume slider is dragged all the way down to 0, the audio correctly mutes. However, after this point, increasing the volume again does not unmute the sound, and the output remains muted even though the slider is moved back up.
I have m4 macbook air with latest OS, Have latest version of Monitor control , connected to monitor via Type c to DP cable. I have Lg 27up650 4k Monitor.
Steps to reproduce
Step 1: Slide volume all the way to left - 0 , Muted icon appears on monitor,
Step 2: Slide volume to the right , to increase volume, speaker remains muted until you un mute with monitor buttons.
Expected behavior
After making the volume 0 , if we increase the volume it should start increasing. It should not remain in muted state. Volume slider percentage is increasing but it remains in mute.
Anything else?
No response
Environment Information (please complete the following information)
@waydabber commented on GitHub (Dec 5, 2025):
Hi there,
this is a monitor specific issue.
I recommend looking at this: https://github.com/waydabber/BetterDisplay/issues/1248