HT202856: Using 4K displays and Ultra HD TVs with your Mac

Learn about Using 4K displays and Ultra HD TVs with your Mac
digitalcoleman

Q: 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

Close

Q: Mac Pro Late 2013 and Samsung 4k monitor problem

  • All replies
  • Helpful answers

first Previous Page 5 of 23 last Next
  • by joevt,

    joevt joevt Jun 8, 2014 8:28 PM in response to Grant Bennet-Alder
    Level 1 (0 points)
    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).

  • by Laseyman,

    Laseyman Laseyman Jun 10, 2014 3:25 PM in response to joevt
    Level 1 (0 points)
    Jun 10, 2014 3:25 PM in response to joevt

    Anyone tried switchresX on the mac pro 2013 and the samsung 4k? I'm going to give it a go tomorrow.. see if I can get displayport working at 2560x1440 rather than running 30Hz on hdmi. will let you know what happens.

  • by joevt,

    joevt joevt Jun 10, 2014 11:43 PM in response to Laseyman
    Level 1 (0 points)
    Jun 10, 2014 11:43 PM in response to Laseyman

    The EDID of the Samsung monitor was posted on MacRumors. It does mention that it supports a 2560 x 1440 mode with the same parameters I listed. It also has a timing for 1920 x 1080 as well as the native 3840 x 2160.

     

    It also lists frequency ranges which suggests it has a scalar that can support custom resolutions not listed here. In that case, you might try creating different resolutions and/or frequencies to find what limit (resolution or pixel clock or refresh rate) is causing the problem. Maybe it's an HBR2 problem? At what frequency does DisplayPort 1.2 switch from HBR to HBR2?

     

    For resolutions: If 2560 x 1440 at 60 Hz works without problem, then you can try creating larger resolutions at 60Hz by adding multiples of 32 to the horizontal and 18 to the vertical (to keep the 16:9 ratio) up to 3840 x 2160. The reason to use 32:18 is because some drivers don't like odd number of vertical lines. You could try going beyond 3840 x 2160 to test if the monitor scalar can shrink the input. We already know that the graphics card scalar can shrink the output to support larger HiDPI modes.

     

    For frequencies: If 2560 x 1440 at 60 Hz works without problem, then you could add other 2560 x 1440 timings by adding multiples of 5 Hz to the refresh rate up to the point where the pixel clock is 540 MHz or the refresh rate is 75 Hz.

     

     

    Detailed mode: Clock 533.250 MHz, 607 mm x 345 mm

                                     3840 3888 3920 4000 hborder 0

                                     2160 2163 2168 2222 vborder 0

                                     +hsync -vsync

    Detailed mode: Clock 241.500 MHz, 607 mm x 345 mm

                                     2560 2608 2640 2720 hborder 0

                                     1440 1443 1448 1481 vborder 0

                                     +hsync -vsync

    Detailed mode: Clock 148.500 MHz, 607 mm x 345 mm

                                     1920 2008 2052 2200 hborder 0

                                     1080 1084 1089 1125 vborder 0

                                     +hsync +vsync

    Monitor ranges (GTF): 56-75Hz V, 30-134kHz H, max dotclock 540MHz

  • by thehesiod,

    thehesiod thehesiod Jun 11, 2014 11:00 AM in response to digitalcoleman
    Level 1 (0 points)
    Jun 11, 2014 11:00 AM in response to digitalcoleman

    I just got the Seiki SE39UY04 and I would say that through HDMI at least with sharpness down the text isn't very smooth (seems like text smoothing isn't working, with sharpeness up it looks horrid).  I noticed similar with my older monitor that if I used HDMI the text wasn't smooth.  Anyone notice this?  Will using this monitor through an active displayport make a difference like it did on my last monitor?

     

    The other thing I noticed is that playing 4k can be dangerous!  I played a 4k video a few times through quicktime and eventually my machine rebooted itself!  4k through FP is really jerky due to lack of hardware decode, I'll try to if something can be done

  • by Laseyman,

    Laseyman Laseyman Jun 11, 2014 12:58 PM in response to digitalcoleman
    Level 1 (0 points)
    Jun 11, 2014 12:58 PM in response to digitalcoleman

    played about with it tonight using standard resolutions but nothing worked at hig res 60hz.. a couple of smaller res's worked at 75hz, so I think I have to play around more with the specifics and increment up in the custom mode... knowing how to use switchres properly will help so i'll have another go tomorrow and watch a tutorial first. not sure it was 'taking' my custom resolutions at all. so will figure that out and go again tomorrow

  • by joevt,

    joevt joevt Jun 11, 2014 4:19 PM in response to Laseyman
    Level 1 (0 points)
    Jun 11, 2014 4:19 PM in response to Laseyman

    If SwitchResX says "modified" in the bottom right corner or the new timing says "Not saved" then press Command-S to save. Type in your password to save. Then if the new timing says "Needs to reboot" then you need to restart the Mac. After restarting, if the driver accepts the resolution/timing then it will say "Active", otherwise it will say "Not activated - invalid?".

    CustomResolutions.png

    Did the 2560 x 1440 timing not get activated? In the Current Resolutions tab, you can click a radio button for an activated resolution to use it, and you can double click it to see the timing information for it.

  • by Laseyman,

    Laseyman Laseyman Jun 12, 2014 12:32 PM in response to joevt
    Level 1 (0 points)
    Jun 12, 2014 12:32 PM in response to joevt

    Ok, did as above with the settings you did a screenshot of before and got "Not activated - invalid?"... should I decrease the resolution until it accepts it and go from there...? it would be good to get displayport working at some sort of acceptable resolution

  • by joevt,

    joevt joevt Jun 13, 2014 2:31 AM in response to Laseyman
    Level 1 (0 points)
    Jun 13, 2014 2:31 AM in response to Laseyman

    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

  • by Terscion,

    Terscion Terscion Jun 20, 2014 1:29 PM in response to ttppee
    Level 1 (0 points)
    Jun 20, 2014 1:29 PM in response to ttppee

    Hi ttppee, I too had purchased a pair of PB287Qs only to discover the 56Hz and tearing along the right edge problem.  I submitted a bug report to Apple and luckily, they have responded asking me to provide some additional data - hopefully it will lead to a solution!  Unfortunately, I have since returned the monitors so I cannot provide that data.  If you are able to get me these files, I'll gladly submit them and hopefully we can all receive a fix from Apple.  Thanks!

     

    This is a courtesy email regarding Bug ID# 17378711.

     

    Please update your report directly at http://bugreport.apple.com for the fastest response.  Please do not email your updates.

     

    Engineering has requested the following information in order to further investigate this issue:

     

    Please attach the output of 'sysdiagnose' collected while the problem is occurring or if not possible taken after the issue has occurred.  'sysdiagnose' can be triggered by pressing Cmd-Opt-Ctrl-Shift-Period, and it may take a few minutes to complete. When ready, the output will automatically be revealed in a Finder window (or it can be manually retrieved from /var/tmp)

     

    Also, please include a full System Information Report.

     

    To obtain a full System Information Report on OS X:

     

    1. Select "About This Mac" from the Apple Menu

    2. Click the “More Info…” button on the About This Mac window

    3. Click “System Report…” on the next About This Mac window

    4. Select "Save…" from the File menu (cmd-s)

    5. Change the file name and save location as needed

    6. Click the "Save" button

     

    A System Information Report can also be obtained via Terminal using the following command:

     

    /usr/sbin/system_profiler -detailLevel full -xml >mymachine.spx

     

    This command will create a full System Information Report, named "mymachine.spx", which will open in System Profiler on another machine.

     

    Please attach the files to your bug report.

     

     

    Bug reports requiring your attention will appear under ‘My Originated Problems’.  Please review this bug report and provide the requested information via the Apple Bug Reporter.

     

    <http://bugreport.apple.com>

     

    Thank you for your assistance in helping us discover and isolate bugs within our products.

     

    Best Regards,

     

    Apple Developer Support

    Worldwide Developer Relations

  • by ConradWinchester,

    ConradWinchester ConradWinchester Jun 20, 2014 11:27 PM in response to Terscion
    Level 1 (0 points)
    Jun 20, 2014 11:27 PM in response to Terscion

    Then they'll ask you to send them a timing file, and then they won't talk to you any more.

     

    Look at bug report

    16937706

    for the exact same issue.

  • by tommyfromomaha,

    tommyfromomaha tommyfromomaha Jun 21, 2014 9:36 AM in response to Terscion
    Level 1 (0 points)
    Jun 21, 2014 9:36 AM in response to Terscion

    Interesting.  I have a New Mac Pro with D300s (low end), and the PB287Q and don't have this problem.  Everything actually works great on 10.9.3, 4k and 60hz.

     

    The only thing I did was activate display port 1.2 in the monitor settings (otherwise it was stuck at 30hz).

     

    Maybe this is an issue with the D700s?  Someone in a different forum with D700s reported the same problem.

  • by ttppee,

    ttppee ttppee Jun 21, 2014 4:54 PM in response to Terscion
    Level 1 (0 points)
    Jun 21, 2014 4:54 PM in response to Terscion

    Hi Terscion,

    Thanks for your information, I am in a business trip now, I will try as soon as I back to home!

  • by Rave-TZ,

    Rave-TZ Rave-TZ Jun 21, 2014 8:41 PM in response to digitalcoleman
    Level 1 (0 points)
    Jun 21, 2014 8:41 PM in response to digitalcoleman

    I have a the UD590 and a Mac Pro late 2013 with the D700s.  I am seeing this issue as native resolution as well.  It also doesn't turn on after sleep sometimes and I recently caught it blinking in and out like crazy.  The blinking and not waking up requires a power cycle to fix.  Early adopter for life!

     

    That said, there are a number of D700 GPU issues introduced with 10.9.2 and 10.9.3.  There is a new 10.9.4 beta release that clears up the multi monitor issue with the Mac Pro.  Could be worth a shot to try the 13E19 beta.  I don't want to sign up for a $99/year plan just to test it though. 

  • by Daniel Hartman1,

    Daniel Hartman1 Daniel Hartman1 Jun 22, 2014 3:45 PM in response to digitalcoleman
    Level 2 (450 points)
    Jun 22, 2014 3:45 PM in response to digitalcoleman

    I had a similar problem with MacPro4,1 and a AMD7950 on the Samsung 4k.  I did discover that dropping the refresh rate to 50Hz would result in no artifacts.  55Hz still gave some, but less.  My understanding is the nMP is using the same drivers, so the same fix might work if you're willing to live with a slight refresh drop.  I used SwitchResX to make the mode, though I'm sure there's other ways.

     

    My bigger problem was the system would not boot with the monitor attached to the 7950's displayport, so I swapped to a GTX 680 which works fine (as others noted)

  • by Rave-TZ,

    Rave-TZ Rave-TZ Jun 22, 2014 7:00 PM in response to Daniel Hartman1
    Level 1 (0 points)
    Jun 22, 2014 7:00 PM in response to Daniel Hartman1

    Can you share what settings you're using to get 50Hz?

     

    Also, I'm trying 10.9.4 Beta 13E19 and it doesn't fix the Samsung distortions on the right side at 60Hz.  It does fix multi monitor bugs (more than 3 screens at the same time).

first Previous Page 5 of 23 last Next