Hi there,

• Does brightness control work or only the bottom 50% of the scale does anything (if so then that is only software adjustment, not DDC control).
• Can you control the display using m1ddc or the latest beta of BetterDummy? If not then there might be some kind of display. incompatibility.

Hi,
thanks a lot for this quick feedback.
-unfortunately, brightness control works only for the bottom 50%
-just tried betterdummy latest beta : same issue , no control of the volume; only bottom 50% for brightness + screen resolution do work well.
I'll contact Samsung too, to know if there is a way to activate DDC on this display, if this is the issue. it's curious for a display that is really targetting Macbook & Mac studio users, including for Camera & Audio. they should keep a way to control it, but ...

You might want to check for a DDC/CI toggle in the monitor OSD (but I don't think Samsungs have one). I don't have any other idea. You can try m1ddc and see if it gives an actual error or not. If you have a Windows PC around, you can also try some apps like Monitorian and see if that works.

Any update @Phryxos? I'm having the same issue, and I'm trying to decide whether to return the monitor or not.

Same issue on the predecessor of the m8, the samsung m7 monitor. I'm connecting via USB-C (DisplayPort).

Any update @Phryxos? I'm having the same issue, and I'm trying to decide whether to return the monitor or not.

Hi,
I've tried several tools, as various parameters on the display... still doesn't work. Looks silly, but it actually seems that Samsung is blocking the DDC/CI protocol on smart monitors, with no way to activate it... I've contacted Samsung yesterday to know about possible software update on their side. Expecting their reply ..

Let us know if there is any response from them! I'll convert this one into a discussion as this comes up from time-to-time and might be a good place to collect info about these displays.

https://github.com/Toxblh/samsung-tv-control

Guys this works perfectly for samsung smart monitor. I tested in samsung M5 monitor for sound control only. We need to develop electron app and wrap this nodejs framework inside ui.

Do we have any update on this issue here?

Hi,
I don't know if there are a latest version of Betterdummy that fixes the issue, butI'm still using sound control which works well.

Is there further fix to enable DDC for M8 for Mac ?

Hi maintainers,

I investigated a software-volume fallback for my Samsung Smart M80F, whose DisplayPort audio output has no native CoreAudio volume control. MonitorControl's volume indicator changed, but the actual sound level did not. Brightness already worked and did not need a new implementation.

A local proof of concept based on MonitorControl 4.4.0 successfully attenuates the audio inside the app using a CoreAudio process tap and a private aggregate device, excluding the app's own output. This changes the audio signal, not the monitor's internal volume, and does not fix DDC. No separate driver, companion app or network connection is required. Audio is processed in memory, without recording or transmission. The prototype uses MIT-licensed CoreAudioTapKit with attribution preserved.

The proposed addition is an optional software-volume fallback for the selected output, sharing one state between the slider, volume keys and mute, while retaining MonitorControl's existing brightness behavior and classic OSD. The local test confirmed volume up/down and mute/unmute using normal multimedia events, without an additional Logitech HID reader or changes to Fn/key assignments.

One useful finding: in this setup, each multimedia key press produced two notifications approximately 2–4 ms apart. Mute therefore toggled twice and appeared ineffective; volume also advanced twice. Filtering duplicate notifications within 20 ms fixed this locally. Volume-key repeat is preserved; mute auto-repeat is ignored. The source of the duplicate notifications has not been established.

Gain uses a cubic curve with a 15 ms ramp. A playback watchdog should distinguish idle audio from a stalled stream, rather than exhausting recovery attempts before playback starts. The solution is now fully functional in my tested Samsung Smart M80F setup: volume up/down, mute/unmute and the existing brightness controls all work. I also signed out of macOS and signed back in; MonitorControl started again and everything continued working, with audio processing active and no recoveries observed. This confirms the functionality on my own setup, rather than claiming validation across all hardware or audio formats. Sleep/wake, hotplug and output switching have not been separately tested.

Would you consider this opt-in fallback for a future release? I would be happy to test an implementation on this monitor.

The earlier reference package below documents the initial prototype and does not include the latest multimedia-event filtering or classic-OSD refinements:
Initial reference proposal and patch

Implementation proposed for review: #1929 . The PR contains the focused software-volume change, compatibility guards, licensing and automated tests.

Update: PR #1929 now also uses cgSessionEventTap for the dedicated volume interceptor. In my local Samsung setup, this restored Spotify previous/next/play-pause keys while keeping software volume working; all were physically confirmed together. Playback keys pass through unchanged, without Spotify-specific handling or Logitech remapping. The PR was rebuilt and the software-audio tests passed.