[GH-ISSUE #44] After the PC is started, MonitorControl is always at 0 #42

New issue

Closed

opened 2026-05-05 04:49:58 -06:00 by gitea-mirror · 2 comments

gitea-mirror commented

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

Owner

Originally created by @kocinko on GitHub (Aug 3, 2018).
Original GitHub issue: https://github.com/MonitorControl/MonitorControl/issues/44

Hello,
Please help, how to set MonitorControl to volume level ?
After the PC is started, MonitorControl is always at 0

Thanks

PS: EFI/CLOVER/drivers64UEFI - is OK

Originally created by @kocinko on GitHub (Aug 3, 2018). Original GitHub issue: https://github.com/MonitorControl/MonitorControl/issues/44 Hello, Please help, how to set MonitorControl to volume level ? After the PC is started, MonitorControl is always at 0 Thanks PS: EFI/CLOVER/drivers64UEFI - is OK

gitea-mirror closed this issue

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

gitea-mirror commented

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

Author

Owner

@vogtmh commented on GitHub (Sep 15, 2018):

I've experienced the same issue. I guess it's because MonitorControl doesn't read the values on startup. However, it was just a display bug for me, sound worked fine (no muting). Pressing Volume Up / Down got the correct value displayed for me.

@vogtmh commented on GitHub (Sep 15, 2018): I've experienced the same issue. I guess it's because MonitorControl doesn't read the values on startup. However, it was just a display bug for me, sound worked fine (no muting). Pressing Volume Up / Down got the correct value displayed for me.

gitea-mirror commented

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

Author

Owner

@reitermarkus commented on GitHub (May 17, 2019):

It should restore the last saved values now.

@reitermarkus commented on GitHub (May 17, 2019): It should restore the last saved values now.