Mac Pro Late 2013 and Samsung 4k monitor problem

I noticed your screen shot isn't using the CVT-RB calculation. It's using the vertical blanking values of the 60 Hz timing. That made me realize that I forgot to update the Blanking value in the overrides that I gave. Here's some updated EDIDs with the correct blanking values to conform to SwitchResX's CVT-RB calculation:

50 Hz (442.00 MHz):

<data>AP///////wBMLYALAAAAADQXAQS1PSN4Ol+xoldPoigPUFS/74BxT4EAgcCBgKnAswCVANEAqKwAoPBwM4AwIDUAX1khAAAaVl4AoKCgKVAwIDUAX1khAAAaAAAA/QAySx6GNgAKICAgICAgAAAA/ABVMjhENTkwCiAgICAgAXkCAwzwIwkHB4MBAAACOoAYcTgtQFgsRQBfWSEAAB4AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAlw==</data>

54 Hz (478.50 MHz):

<data>AP///////wBMLYALAAAAADQXAQS1PSN4Ol+xoldPoigPUFS/74BxT4EAgcCBgKnAswCVANEA6roAoPBwOIAwIDUAX1khAAAaVl4AoKCgKVAwIDUAX1khAAAaAAAA/QAySx6GNgAKICAgICAgAAAA/ABVMjhENTkwCiAgICAgASQCAwzwIwkHB4MBAAACOoAYcTgtQFgsRQBfWSEAAB4AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAlw==</data>

55 Hz (487.50 MHz):

<data>AP///////wBMLYALAAAAADQXAQS1PSN4Ol+xoldPoigPUFS/74BxT4EAgcCBgKnAswCVANEAbr4AoPBwOYAwIDUAX1khAAAaVl4AoKCgKVAwIDUAX1khAAAaAAAA/QAySx6GNgAKICAgICAgAAAA/ABVMjhENTkwCiAgICAgAZsCAwzwIwkHB4MBAAACOoAYcTgtQFgsRQBfWSEAAB4AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAlw==</data>

56 Hz (496.75 MHz):

<data>AP///////wBMLYALAAAAADQXAQS1PSN4Ol+xoldPoigPUFS/74BxT4EAgcCBgKnAswCVANEAC8IAoPBwOoAwIDUAX1khAAAaVl4AoKCgKVAwIDUAX1khAAAaAAAA/QAySx6GNgAKICAgICAgAAAA/ABVMjhENTkwCiAgICAgAfkCAwzwIwkHB4MBAAACOoAYcTgtQFgsRQBfWSEAAB4AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAlw==</data>

57 Hz (505.75 MHz):

<data>AP///////wBMLYALAAAAADQXAQS1PSN4Ol+xoldPoigPUFS/74BxT4EAgcCBgKnAswCVANEAj8UAoPBwO4AwIDUAX1khAAAaVl4AoKCgKVAwIDUAX1khAAAaAAAA/QAySx6GNgAKICAgICAgAAAA/ABVMjhENTkwCiAgICAgAXECAwzwIwkHB4MBAAACOoAYcTgtQFgsRQBfWSEAAB4AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAlw==</data>

Just got back to follow the progress of this thread.

Good news people! Will try this out this evening if I can get my head round it myself.

from what I gather from poydas success, the process is to

1. restore switch res to factory settings

2. Create an override using the code that joevt has written above for one of the timings in

/System/Library/Displays/Overrides/DisplayVendorID-4c2d/DisplayProductID-b80

(what should the file extension be?)

3. switchres should then allow selectable resolutions at the timings which work for our display ports and we can finally use them with a respectable result.

Please correct me if I'm wrong or if there are any pitfalls you can foresee for me or others, be good to get it working tonight 🙂

L

Are you positive your cable is Displayport 1.2 compliant? This is the description for the one I have: "The 20-pin Mini-DisplayPort is DisplayPort 1.2 compliant / HDCP 1.3 and 21.6 Gbps of bandwidth. The maximum resolution supported is 4096 x 2160 @ 60Hz."

Specially, I think the bandwidth is of great importance.

I bring that up because @Laseyman reported horizontal artifacts on his Samsung as you did, and that seems to be the only difference between our setups by now. I´ve been using graphics software and playing videos flawlessly with the Lenovo cable for 2 days now, no artifacts at all...

Aha, yes, must be the problem: I bought the StarTech.com Mini DisplayPort to DisplayPort Adapter Cable - M/M - DisplayPort cable - 2 m, only supports data-transfer rates of up to 8.64Gbps, having a look at a few 1.2 compliant and even some don't have the top bandwidth of the ones you have listed, so I'll definitely get one that does at a later date.

Cheers.

Last week I bought the "cheap" Mac Pro with the two AMD D300 graphic cards. I Connected it yesterday to my Samsung U28D590D with a standard Cable Displayport mini>Displayport of Delock with a length of 1 meter (Art #82698 spec: max res wqxga 2560x1600, qxga 2048x1536, connector gold plated).

I didn't change any settings to the monitor or the Mac. It run plug and play immediately 60hz 4k resolution of 3840 x 2160. No artifacts. I ran View and Nikon Capture NX2 on my Mac, very nice crispy "Retina" feeling. I am very happy with my setup.

Hi Toni,

This seems to be consistent with other D300 owners. My problems didn't go away until I installed OS X 10.10 beta and I have the D500's.

Are you running OS X 10.9.4 or OS X 10.10 beta?

I read on the Displayport.org site that it doesn't matter which cable you use DP 1.1 or DP 1.2 as they are designed with the same standard. However, that doesn't mean that you can get a poorly manufactured one and have problems.

From what I see, 4k SST support will be widespread very shortly.

Trace-

I have the EA244UHD and am having the same problems (D700 cards as well). Have you contacted apple? is there an official response?

------

I purchased a NEC Multisync EA244UHD IPS display and having the distortion issues with the right side of the screen with Display Port 1.2 at 60hz at any resolution however no issue with Display Port 1.1 at 30hz. I took my mac pro 10.9.4 with dual D700's into the Apple store and my NEC monitor and they hooked up the monitor to a MacPro with D300's and it worked fine with Display Port 1.2 and 60Hz at any resolution. The monitor also woke up fine with shutting down or sleeping which is the other problem I have. I have to jump through hoops to get the MacPro to wake up the NEC monitor even running Display Port 1.1. It seems that the issue is with my D700's.

I had same problem too, The samsung monitor can't adjust the stream so it's reffresh reate it's locked at 56HZ, NOT 60Hz, may be this is the reason caused the "tearing" problem, I was call samsung service department, thsy told me they know nothing about it, and this monitor is design for Windows not fro Mac...............

And there is another problem, when you use displayport connect to Mac Pro, when Mac Pro went to sleep you can't wake up monitor by using keyboard, it will stay dark unless you push the monitor switch again, but if you choose by using HDMI 30Hz mode it will be work fine.....

ttppee, you are absolutely right up till OS X 10.9.2 but 10.9.3 beta has already enabled support of 4k/60Hz using display port on macbook pro late 2013. Yet my concern is whehther the Samsung 4K monitor will have the similar problem as Mac pro. I guess one difference on Samsung is that this is the first monitor not requires MultiStream Transport (MST) as this monitor can support Single Stream 60Hz 4k which is pretty amazing.

Check the EDID of the monitor to make sure it supports a 2560x1440 timing mode, then use SwitchResX to create that timing mode (you'll have to figure out if the mode is GTF or CVT or CVT-RB). This should override the scaled mode that is automatically created by the Mac graphics driver.

I do this on my Apple 30" Cinema HD Display to enable the non-scaled 1280 x 800 mode that it supports (native resolution is 2560 x 1600).

Sure, try starting from 1920 x 1080 @ 60 Hz. Try CVT-RB and GTF. Enter a bunch of sizes or refresh rates, then restart to see which if any get activated. If nothing works, then maybe you can try overriding the EDID to remove the 3840 x 2160 descriptor and/or make the 2560 x1440 @ 60 Hz descriptor the first one.

I wonder how digitalcoleman got 2560 x 1440 to work. Are you sure there's no 2560 x 1440 @ 60 Hz mode already (non-scaled)? Maybe digitalcoleman used an HDMI cable for that since it only requires 241.5 MHz.

Anyway, send a screen shot of the Current Resolutions and Custom Resolutions tabs of SwitchResX to show us what you've tried. Post the EDID info if it doesn't match the info posted in the MacRumors forums.

http://forums.macrumors.com/showthread.php?t=1668673&page=4

I sent the developer of SwitchResX an email asking if it was possible, here is the reply:

You cannot define which resolution is used as a basis for the scaled resolutions. Scaled resolutions are all "children" of a master resolution, which is always the same, and which is chosen by MacOS X - this is not a choice that can be influenced by SRX

Moreover, as far as I know, Apple has decided that AMD display drivers cannot use scaled resolutions apart those that are stored in a hardcoded list in their display driver. I may be wrong, but this simply means that you cannot get any HiDPI resolution that is not "apple-approved" on a MacPro.

regards

Stephane

That's very unfortunate news for me, because I find the interface to be way too small to use at the native resolution of 3840x2160. At least we have made some progress. Let's hope Apple and AMD hurry up and fix this problem soon.

Thanks,

Poyda

Poyda said he got 54 Hz working (though maybe with a slightly off blanking interval). You should try 55 Hz then go to 54 if that doesn't work or 56 if it does. Takes only a couple restarts to find out.

Did you consider the ASUS PB287Q monitor? Same panel, better stand, more features, VESA compatible mount.

Of course, you would need to override the EDID to fix the same problem if you're using an affected graphics card/driver. I guess the Samsung override file would work, but you would need to change the vendor and product ID in the file and in the file path/name to match the ASUS values. The ASUS monitor would then appear as a Samsung monitor.

I got the EDID for the Samsung from a hex dump from SwitchResX posted at MacRumors, used "echo 'paste hex here' | xxd -p -r > U28D590.bin" to convert to binary, then I used a utility called Lightware Matrix Controller v 3.4.6 (free) in Windows to edit the bin file, changed the primary timing to match SwitchResX's CVT-RB calculations for the desired timing. Then "xxd -p < U28D590.bin" to get the hex dump and pasted that into the override file using Property List Editor.app.

I think it would be cool if SwitchResX had an EDID editor like Lightware Matrix Controller or Phoenix EDID Designer 1.3 (I haven't tried the latter).

I described the method I used to edid the EDID on page 7 (Jun 25, 2014 9:02 PM).

Lazlo, you have a PB287 model 28a2. The override file should be at /System/Library/Displays/Overrides/DisplayVendorID-469/DisplayProductID-28a2

The contents of an override file for product 28a2 that uses 3840 x 2160 50 Hz CVT-RB for the preferred timing mode should look like this:

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
  <key>DisplayProductID</key>
  <integer>10402</integer>
  <key>DisplayVendorID</key>
  <integer>1129</integer>
  <key>IODisplayEDID</key>
  <data>AP///////wAEaaIoAAAAABAYAQSlPiJ4Ohy1o1dPoCcNUFSjCADRwIFAgYCVALMAgcABAQEBqKwAoPBwM4AwIDUAbVUhAAAaBHQAMPJwWoCwWIoAbVUhAAAaAAAA/QAeUBigPAQRAPD4OPA8AAAA/ABBU1VTIFBCMjg3CiAgATwCAydxTwECAxESEwQUBR+QDg8dHiMJFweDAQAAagMMABAAAHggAACMCtCKIOAtEBA+lgBtVSEAABgBHQByUdAeIG4oVQBtVSEAAB4BHQC8UtAeILgoVUBtVSEAAB6MCtCQIEAxIAxAVQBtVSEAABgAAAAAAAAAAAAAAAAAAAAA6w==</data>
</dict>
</plist>

For the PB287Q model 28a3, the override file should be at /System/Library/Displays/Overrides/DisplayVendorID-469/DisplayProductID-28a3

The contents of an override file for product 28a3 that uses 3840 x 2160 50 Hz CVT-RB for the preferred timing mode should look like this:

<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
  <key>DisplayProductID</key>
  <integer>10403</integer>
  <key>DisplayVendorID</key>
  <integer>1129</integer>
  <key>IODisplayEDID</key>
  <data>AP///////wAEaaMoAAAAABQYAQSlPiJ4Ohy1o1dPoCcNUFS/7wDRwIFAgYCVALMAcU+BwAEBqKwAoPBwM4AwIDUAbVUhAAAaBHQAMPJwWoCwWIoAbVUhAAAaAAAA/QAeUBigPAQRAPD4OPA8AAAA/ABBU1VTIFBCMjg3UQogAUUCAydxTwECAxESEwQUBR+QDg8dHiMJFweDAQAAagMMABAAAHggAACMCtCKIOAtEBA+lgBtVSEAABgBHQByUdAeIG4oVQBtVSEAAB4BHQC8UtAeILgoVUBtVSEAAB6MCtCQIEAxIAxAVQBtVSEAABgAAAAAAAAAAAAAAAAAAAAA6w==</data>
</dict>
</plist>

I removed the serial numbers from the EDIDs.

Make sure the spaces or tabs are normal and not non-breaking spaces. Use plutil to make sure the files are valid. Make sure the vendor and product ids match your display.

I made a shell script to output the text of an override file given the path of an already edited EDID binary file:

#!/bin/bash
#
# Output the text for an override file
# $1: name of EDID file (128 or 256 bytes)
vendorid=$((0x$(dd if="$1" bs=2 skip=4 count=1 2> /dev/null | xxd -p)))
productid=$((0x$(dd if="$1" bs=2 skip=5 count=1 conv=swab 2> /dev/null | xxd -p)))
echo "Path: /System/Library/Displays/Overrides/DisplayVendorID-$(printf '%x' $vendorid)/DisplayProductID-$(printf '%x' $productid)"
echo '<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
  <key>DisplayProductID</key>
  <integer>'$productid'</integer>
  <key>DisplayVendorID</key>
  <integer>'$vendorid'</integer>
  <key>IODisplayEDID</key>
  <data>'$(base64 < "$1")'</data>
</dict>
</plist>'