-
Notifications
You must be signed in to change notification settings - Fork 43
Samsung
Does not support DDC.
Monitor supports DDC via HDMI and both DisplayPorts. Unfortunately, the protocol doesn't allow you to properly switch between DP1 and DP2 - probably due to custom PIP mechanisms.
Do not implement DDC/CI on DisplayPort inputs, only on HDMI. See webpage Notes on Specific Monitors and this reddit post.
Feature x60 (Input Source) actual values:
| Port | Feature value |
|---|---|
| HDMI | x05 |
| DisplayPort | setvcp requires x06, but getvcp reports x0f |
MCCS (VCP) version reported:
| Source | Version |
|---|---|
| capabilities string | 2.2 |
| feature xdf | 2.2 |
Reported by user @ehdoyle
Manufacture year: 2015
VCP Version: 2.0
Controller manufacturer: Mstar, controller number: mh=x00, ml=x10, sh=x00
Firmware version: 0.1
Capabilites request returns a 0 length string.
Features x0B and X0C are unsupported. Cannot calculate color temperature.
Has no serial number in EDID
Does not support DDC.
VCP version: Unspecified, implies 1.0
Controller manufacturer and model: Unknown (VCP feature code C8 unsupported)
Firmware version: Unknown (VCP feature code C9 unsupported)
The capabilities string spcifies the values for non-continuous features in decimal rather than hexadecimal
VCP feature code
VCP version reported by capabilitise string: 2.0
VCP version reported by feature xdf: 2.1
Controller manufacturer and model: Novatek, model id: mh=xff, ml=0xff, sh=0x00
Firmware version: 0.0
Two users have reported that DDC/CI does not work over DisplayPort. In both cases they were using the amdgpu video driver This was true no matter which DisplayPort version was chosen in the OSD. As of 12/2020, this is not fixed by the most recent monitor firmware update. User razamatan reports that he was told in Samsung's chat support that DDC/CI is not implemented on DisplayPort.
The capabilites string reports an unrecognized command code, x4e
Feature x14 (Color Perset), x06 (Color Temperature Increament) and x06 (Color temperature requrest) appear consistent.
In one report:
VCP code 0x14 (Select color preset ): 7500 K (sl=0x06)
Color temperature increment (x0b) = 50 degrees Kelvin
Color temperature request (x0c) = 90
Requested color temperature = (3000 deg Kelvin) + 90 * (50 degrees Kelvin) = 7500 degrees Kelvin
The monitor has two DisplayPort inputs and one HDMI input. However, the capabilities string reports valid values as being as x01 - VGA and X03 - DVI-1.
The following features are not declared in the capabiliteis string but were found by scanning:
Feature x52 - Active control
Feature xb2 - Flat panel sub-pixel layout
Feature xf4 - Manufacturer Specific
Feature xfe - Manufacturer Specific
VCP version reported by capabilities string: 2.1,
VCP version reported by feature xdf: 2.0
Controller manufacturer and model: Mstar, model id: mh=x00, ml=0x10, sh=0x00
Firmware version: 0.1
This monitor is a MCCS disaster area.
The capabilities string returned by the monitor is malformed. As a result, ddcutil cannot parse the "cmds" field.
Features x0B and X0C are unsupported. Cannot calculate color temperature.
No matter what the color mode (x14 Preset, xDC Display Mode) color settings (x16, x18, x1a) cannot be changed. Brightness (x10) and contrast can be changed only in some modes.
Values in the capabilities string correlate poorly with observed values. For example, according to the capaiblities string, feature x60 (Input source) has values x11, x12, and x0f, which the MCCS spec defines as HDMI-1, HDMI-2 and DisplayPort-1 respectively. However, the observed values are x05, x06, and x0f, which the MCCS spec defines as Composite video 1, Composite video 2, and Displayport respectively.