github-starred/MonitorControl

Fork 0

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

[GH-ISSUE #707] Philips 329P9H built-in camera freezing while on video calls #467

New issue

Closed

opened 2026-05-05 06:04:12 -06:00 by gitea-mirror · 5 comments

gitea-mirror commented

2026-05-05 06:04:12 -06:00

Owner

Originally created by @acousticbiker on GitHub (Oct 12, 2021).
Original GitHub issue: https://github.com/MonitorControl/MonitorControl/issues/707

Before opening the issue, have you...?

Searched for existing issues
Looked through the wiki
Updated MonitorControl to the latest version (if applicable)

Describe the bug

Since using M1 builds (version 3 onward), when on a video call (e.g., Teams, Zoom) the built-in camera on my Philips 329P9H monitor freezes intermittently. The only way to unfreeze is to disable video in the app, re-insert camera into monitor (it retracts), re-deploy camera, and re-enable video in app.

I don't know enough technically to determine whether MonitorControl could cause this but I can't think of any other change/cause and the behavior aligns with the timing of the change to the M1-compatible MonitorControl.

Steps to reproduce

Engage in video call using Teams or Zoom while MonitorControl running

Expected behavior

No freezing during video calls (which was the case pre-M1 compatibility)

Anything else?

No response

Environment Information (please complete the following information)

- macOS version: 11.6
- Mac model: M1 MacBook Air
- MonitorControl version: 4.0
- Monitor(s): Philips 329P9H
- Apple Silicon/M1 (yes or no): yes

Originally created by @acousticbiker on GitHub (Oct 12, 2021). Original GitHub issue: https://github.com/MonitorControl/MonitorControl/issues/707 ### Before opening the issue, have you...? - [X] Searched for existing issues - [X] Looked through [the wiki](https://github.com/MonitorControl/MonitorControl/wiki) - [X] Updated MonitorControl to the latest version (if applicable) ### Describe the bug Since using M1 builds (version 3 onward), when on a video call (e.g., Teams, Zoom) the built-in camera on my Philips 329P9H monitor freezes intermittently. The only way to unfreeze is to disable video in the app, re-insert camera into monitor (it retracts), re-deploy camera, and re-enable video in app. I don't know enough technically to determine whether MonitorControl could cause this but I can't think of any other change/cause and the behavior aligns with the timing of the change to the M1-compatible MonitorControl. ### Steps to reproduce Engage in video call using Teams or Zoom while MonitorControl running ### Expected behavior No freezing during video calls (which was the case pre-M1 compatibility) ### Anything else? _No response_ ### Environment Information (please complete the following information) ```markdown - macOS version: 11.6 - Mac model: M1 MacBook Air - MonitorControl version: 4.0 - Monitor(s): Philips 329P9H - Apple Silicon/M1 (yes or no): yes ```

gitea-mirror

2026-05-05 06:04:12 -06:00

closed this issue
added the
monitor Issue
label

gitea-mirror commented

2026-05-05 06:04:18 -06:00

Author

Owner

@JoniVR commented on GitHub (Oct 12, 2021):

Hi,

When it was working "pre-M1 compatibility", I'm assuming this was also using an Intel machine then?

@JoniVR commented on GitHub (Oct 12, 2021): Hi, When it was working "pre-M1 compatibility", I'm assuming this was also using an Intel machine then?

gitea-mirror commented

2026-05-05 06:04:21 -06:00

Author

Owner

@acousticbiker commented on GitHub (Oct 12, 2021):

Correct. And, in case helpful, I used Lunar for a period of time when they added M1 compatibility and before MonitorControl did and don't remember the freezing being an issue then.

@acousticbiker commented on GitHub (Oct 12, 2021): Correct. And, in case helpful, I used Lunar for a period of time when they added M1 compatibility and before MonitorControl did and don't remember the freezing being an issue then.

gitea-mirror commented

2026-05-05 06:04:23 -06:00

Author

Owner

@waydabber commented on GitHub (Oct 12, 2021):

Hi @acousticbiker - for a while you should try not using MonitorControl (you can try Lunar again) and see if the issue persists. I can't think of any reason why this should happen as the built-in webcam most probably uses USB data while DDC control uses I2C embedded in the DisplayPort communication which happens on separate lanes via USB-C. But the internal workings of the display is an unknown, it might be that somehow DDC commands causes problems internally. Lunar and MonitorControl uses the same commands and basic control method on M1.

@waydabber commented on GitHub (Oct 12, 2021): Hi @acousticbiker - for a while you should try not using MonitorControl (you can try Lunar again) and see if the issue persists. I can't think of any reason why this should happen as the built-in webcam most probably uses USB data while DDC control uses I2C embedded in the DisplayPort communication which happens on separate lanes via USB-C. But the internal workings of the display is an unknown, it might be that somehow DDC commands causes problems internally. Lunar and MonitorControl uses the same commands and basic control method on M1.

gitea-mirror commented

2026-05-05 06:04:27 -06:00

Author

Owner

@acousticbiker commented on GitHub (Oct 12, 2021):

I did try not using MC and that seemed to fix it

@acousticbiker commented on GitHub (Oct 12, 2021): I did try not using MC and that seemed to fix it

gitea-mirror commented

2026-05-05 06:04:30 -06:00

Author

Owner

@waydabber commented on GitHub (Oct 13, 2021):

This probably means that the MC is incompatible with the display. You might want to try Lunar and see if it causes the same problem or not. If not, then I advise you to stick with it, if it is, then it is probably best not to use apps that control the display via DDC if you wish to frequently use the built in webcam. An other option might be to seek Philips about this problem or check if there is a firmware update for the display that fixes the issue.

I'll convert this issue to a discussion, maybe other Philips users will add their experiences.

@waydabber commented on GitHub (Oct 13, 2021): This probably means that the MC is incompatible with the display. You might want to try Lunar and see if it causes the same problem or not. If not, then I advise you to stick with it, if it is, then it is probably best not to use apps that control the display via DDC if you wish to frequently use the built in webcam. An other option might be to seek Philips about this problem or check if there is a firmware update for the display that fixes the issue. I'll convert this issue to a discussion, maybe other Philips users will add their experiences.