Mac Pro Late 2013 and Samsung 4k monitor problem

I have the new Samsung 28" 4k screen (U28D590D) and it has tearing along the right edge when used with displayport. Any way to fix that? I tried different cables (all DisplayPort 1.2 complient) to be sure and have narrowed the issue to the Mac Pro. The HDMI works fine tho only @30hz so is a bit laggy in normal interaction. There is no way to turn on Multi-stream as indicated and I hope it isnt that this screen will never work.

Mac Pro, OS X Mavericks (10.9.2), Dual Fire Pro D700

Posted on Apr 11, 2014 2:12 PM

Reply
Question marked as Top-ranking reply

Posted on Oct 1, 2014 10:44 PM

Good news! I have this same issue running 10.9.5. But I installed the golden master (build 14A379b) of Yosemite tonight and my Samsung displays perfectly @60hz at all resolutions! FINALLY! Yosemite should be out in just a few more days so rest easy Samsung U28D590D owners! Relief is on the way!

330 replies

Jun 8, 2014 8:28 PM in response to Grant Bennet-Alder

I haven't heard about that problem with the RGB mode.



SwitchResX is only useful for creating/enabling/disabling timings and scaled modes and for viewing the EDID plus some other features (menus, applications, etc). The problem might be fixable by editing the EDID. There may be many color parameters in the EDID that can be changed or added (I don't know which). Maybe this is what the Ruby script is doing? Where is the Ruby script? It would help to know what the fix does...



To create a custom timing or scaled resolution, SwitchResX edits or creates an override file in the /System/Library/Displays/Overrides folder. The override file can also override the EDID of the display. In fact, Apple includes files for some 4K displays that override their EDID. In 10.9.3, the following override files were added or modified:



DisplayVendorID-4d10/DisplayProductID-21dd // PN-K321

DisplayVendorID-4dd9/DisplayProductID-2503 // SONY TV *07

DisplayVendorID-469/DisplayProductID-32a3 // ASUS PQ321

DisplayVendorID-10ac/DisplayProductID-4093 // DELL UP3214Q

DisplayVendorID-10ac/DisplayProductID-409c // DELL UP2414Q



I don't know if SwitchResX shows the EDID of the override file or the original from the monitor. You may want to try removing the override file temporarily to see the original EDID (probably needs a restart for each change). Or maybe the original EDID is stored in the IORegistry? Here's a command to look for EDIDs in the IORegistry:



ioreg -w 0 -l | grep EDID



If all the EDIDs are not the same then you have more than one kind of display, or else one EDID might be the original and the other might be an override.



You need an EDID editor to edit the EDID binary. I think there are EDID editors for Windows that could work or you could edit it directly if you know the format. Then you can use the Property List Editor to paste it into the override file (the "xxd -p" command can be used to convert a binary file into text representation of the hex, and "xxd -p -r" can go from text hex to binary).

Jun 30, 2014 7:48 PM in response to Laseyman

Well, you could try the CVT-RB timing that I gave for 50 or 54 or 55 or 56 or 57 Hz. Just replace the <data> line.


Does the display have onscreen controls that show the vertical and horizontal refresh rate? If so then make sure those values match the timing you're using.


Maybe a higher quality DisplayPort cable would help? Are you using a single cable or an adapter + cable? I don't know what a higher quality cable is but at least you can try a different cable.


You could try running Windows to see if that clears it up. If it does, then you can try to figure out if it's using the same timing on the Mac. Maybe a program like PowerStrip can help figure that out. Or maybe there's a Windows driver info file for the display that can be examined (like the Mac's override file). If the timing is the same then that means there's some other difference in the AMD driver on the Mac side (voltage level? or whatever).

http://msdn.microsoft.com/en-us/library/windows/hardware/ff568432(v=vs.85).aspx

http://msdn.microsoft.com/en-us/library/windows/hardware/jj133967(v=vs.85).aspx

http://www.entechtaiwan.com/util/ps.shtm

Jul 21, 2014 3:57 PM in response to joevt

Hi joevt,


Is it possible to make a data line for the override file that is actually 60 Hz. for the Samsung 4k monitor? I have been using the 50 Hz file for a while and it has been much better than the 56 Hz which causes the picture overlap on the right hand side but still a little lagging. 57 Hz also causes the same overlap but it appears to be thinner to the edge. The monitor seems to be okay going past 57 Hz and so does the nMP (D500 model). I have just switched over to the 54 Hz. now and the picture is getting better all the time.


Thanks,

PB

Jul 25, 2014 9:46 PM in response to Daniel Hartman1

If it was a cable problem, then full resolution would not be usable in Windows 7. Maybe Windows 7 wasn't using 60 Hz? Double check the refresh rate.


Does the iMac have the same 4K 60Hz display ability of the MBP and nMP? I don't think it has Thunderbolt 2 or DisplayPort 1.2 so probably not.


SwitchResX shows the correct vender and product ID's in the upper left part of the Display Information tab of the display. The product ID should be b80. You could post the EDID hex so we can make sure.

Aug 3, 2014 5:08 AM in response to Terscion

I just purchased the Philips "Brilliance 288P6" to my Mac Pro w. D-700's.


It certainly has the same issues top-right. I've played around (inspired by joevt ;-), I've decided to wait for 10.9.5 or 10.10 in the hope that Apple got it fixed.


EDID for Philips 288P6:


"IODisplayEDID" = <00ffffffffffff00410cd7089500000010180104a53e22783a5525a1574fa0280f5054bd4b00d1 c081808140950f9500b30081c0010150d000a0f0703e8030588a006d552100001a023a801871382d 40582c45006d552100001e000000fc005068696c697073203238385036000000fd0017501ea03c01 0a20202020202001b3020323f44b010203040590111213141f23090707830100006a030c00300000 78200000023a80d072382d40102c96806d5521000018023a801871382d40582c96006d5521000018 04740030f2705a80b0588a006d552100001a011d00bc52d01e20b82855406d552100001e00000000 0000000000000000000000000000000080>


Best regards - Kim Bjoern

Oct 30, 2014 7:31 PM in response to digitalcoleman

I got the emails, and saw the posts. Some interesting points were made seminolefans. The only way to get these issues heard though is to call AppleCare, and let them know about these issues. It's the only way to get engineering to hear us, and actually do something about this issue rather then doing nothing. If you call, let them know about this thread, as this is a widespread issue, and this thread shows that.


Again, anyone having this issue, please call AppleCare!

Oct 2, 2015 10:35 PM in response to Markus Gantner

So I was able to solve the right hand tearing on the samsung U32D970q by using SwitchresX and creating a custom profile at 57 hz.... (and using diplayport)... but now there is a subtle thin tearing right down the middle of the screen. Is my only hope on this to upgrade to yosemite? This is such a drag Apple. Its a work computer, I need to be careful about OS upgrades... these kinds of things should be functional. Anyone have any other thoughts to solve the center tearing? Thanks!

Apr 11, 2014 4:01 PM in response to digitalcoleman

When using "Legacy" displays the screen is re-drawn some 30 to 100 times a second even if it does not change a bit. If the re-draws stops, the screen goes blank.



it has tearing along the right edge when used with displayport.


When using DisplayPort, the screen data is sent ONCE, and then if nothing changes, the data link goes quiet. Scrren data re NOT re-drawn if they do not change.


Tearing down one side of a DisplayPort display is an indication that the DISPLAY has an Internal problem.

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

Mac Pro Late 2013 and Samsung 4k monitor problem

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.