mirror of
https://github.com/MonitorControl/MonitorControl.git
synced 2026-05-15 14:15:55 -06:00
[GH-ISSUE #1667] Monitor speakers sync issue #929
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#929
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 @PoeticMichael on GitHub (Nov 7, 2024).
Original GitHub issue: https://github.com/MonitorControl/MonitorControl/issues/1667
Before opening the issue, have you...?
Is your feature request related to a problem? Please describe
It's not exactly MonitorControl problem, but maybe you can solve it.
The problem happens with two different USB-C-connected monitors - Samsung and LG.
It shows up both with Sonoma running MacBook Pro and Monterey MacBook Pro. M1 and M2.
With MonitorControl and without MonitorControl.
If the laptop reboots while not connected to the monitor, sound through the monitor speakers will be garbled.
Videos that have sound are reproduced in a very jittery way, skipping fragments, scanning back and forth, etc.
If I reboot the laptops with the monitors connected, there is no issue, even if the machine is disconnected and reconnected later.
Describe the solution you'd like
It looks like there is some synchronization with monitors happening at reboot and at reboot only.
Is there a chance MonitorControl could do some sync to avoid this issue?
Describe alternatives you've considered
Reboot while connected to the monitor is the only solution I found.
Anything else?
No response
@waydabber commented on GitHub (Nov 7, 2024):
This seems to be some kind of hardware issue. You can try using BetterDisplay and use Tools/Displays.../Reinitialize External Displays to check whether that helps.