Skip to content

Instantly share code, notes, and snippets.

@genedeng-ca
genedeng-ca / G95NC-core-lighting-ddc.md
Created September 10, 2026 06:50
Samsung Odyssey Neo G9 57" (G95NC): controlling the rear Core Lighting over DDC/CI - three undocumented VCP codes (0xF8/0xF9/0xFA)

Controlling Samsung Odyssey Neo G9 57" (G95NC) Core Lighting over DDC/CI: the three undocumented VCP codes

TL;DR. The G95NC's rear CoreSync+ lighting is fully readable and mostly writable over plain DDC/CI, through three manufacturer-specific VCP codes that the monitor does not advertise in its capabilities string:

VCP Meaning Range Writable
0xF8 Lighting source max 17 only 0x00 (off) / 0x01 (manual)
0xF9 Lighting effect mode max 5 yes, in manual mode
@genedeng-ca
genedeng-ca / G95NC-macOS-HiDPI.md
Last active September 10, 2026 06:51
Samsung Odyssey G95NC on macOS: unlocking 1920x1620 HiDPI via USB-C dock — the cable matters, not the HDMI port

Samsung Odyssey G95NC on macOS: unlocking 1920×1620 HiDPI via USB-C dock — the cable matters, not the HDMI port

Short version for people who Google'd their way here at 2am: if your Mac shows the G95NC at 2560×2160 native 1:1 (tiny text) and the Scaled menu has no 1920×1620 option, it's not the dock and not the HDMI port — it's the cable. You need a USB-C → HDMI 2.1 active cable (not DP-to-HDMI, not a generic adapter). Both HDMI-1 and HDMI-2 on the monitor work once the cable is right. Scripts + full wiring below.


The problem

You bought a Samsung Odyssey G95NC 57" Dual UHD (7680×2160, 32:9). You dock your Mac (MacBook Pro M-series) through a Thunderbolt 4/5 hub. You run it in PBP 21:9 mode so the right half is 2560×2160.