Custom Resolution Utility (CRU)

[MUC]

(Today 07:32 PM)moecre Wrote:  - The original EDID of the monitor connected via HDMI directly and exported
- The EDID I got from Blustream to make the 5120x1440 resolution work, through the signal processor
- The EDID, with 144 Hz based on the one provided by Blustream.

The monitor's original EDID indicates a maximum bandwidth of 24 Gbps (HDMI 2.1 Fixed Rate Link 3). Consequently, the graphics card must use Display Stream Compression (DSC) to output 5120 x 1440 @ 144 Hz to the monitor.

The other two EDID files are only 256 bytes each. This makes it impossible to advertise the monitor's desired refresh rates via the SM11EARC-8K, as doing so requires an EDID of at least 384 bytes. A DisplayID cannot be defined in the format shown in the two modified EDID files. This results in incompatibility with HDMI 2.1 FRL (DSC). I suspect the SM11EARC-8K is limited to a 256-byte EDID.

However, to solve your problem, it should suffice to connect the device chain as intended and then fully import the monitor's original EDID using CRU. In other words, you apply the original EDID as an override for whatever the graphics card detects when connected to the SM11EARC-8K.

I do, however, doubt whether the SM11EARC-8K can still perform audio (de-)embedding with a DSC signal. What function do you need the device to perform? That should determine how you set the device's DIP switches before applying the EDID override on your PC.

---

(Today 08:22 PM)katates Wrote:  I saw couple mentions that its related with some Nvidia DSC bug. Is there any proper solution that can be achieved with CRU or some other way?

The Samsung monitor expects this:

5120 x 1440 @ 239.76 Hz >>> 1939.49 MHz pixel clock

With Nvidia GeForce RTX 40 series cards, EDID overrides only work successfully if the output signal's pixel clock remains below 1350 MHz. That is the graphics card's single-head limit. It has nothing to do with DSC itself.

I don't think CRU can help in your case.