HT202856: Using 4K displays and Ultra HD TVs with your Mac
Learn about Using 4K displays and Ultra HD TVs with your Mac
-
All replies
-
Helpful answers
-
Jul 21, 2014 5:40 PM in response to PB_NBby joevt,PB_NB wrote:
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
There's no way to know unless you find a mode that works or you find that all possible (at least reasonable) modes don't work. You can use SwitchResX to try different modes. I guess you would want to play with the horizontal blanking values. The horizontal blanking period consists of 3 parts: the front porch, the sync pulse, and the back porch. For CVT-RB timings, it looks like this (16 pixels per character):
–––__––––– (48 front porch, 32 sync width, 80 back porch)
You can move the sync pulse left or right (make a change in the front porch and the opposite change in the back porch) which would have the affect of moving the display left or right on a CRT (not sure what the result would be on an LCD).
You can change the width of the sync pulse (make a change in the sync pulse and the opposite change in the front or back porch).
You can make the total blanking period shorter or longer, but then you would need to adjust the pixel clock to keep the vertical refresh rate at 60 Hz (which means a line will take the same amount of time, but the blanking will be a different fraction of the time).
If the display works in Boot Camp on the same Mac, then you could get the data line from that and use it in Mac OS X. If the data line is the same then it means the Mac OS X driver has some other problem.
-
Jul 21, 2014 9:19 PM in response to joevtby PB_NB,Hi joevt,
I messed with SwitchResX for a while and discovered that this setup (nMP, OSX and SST 4k) is just not ready to go past 54 hz. at full resolution without the picture overlap. I expect that we will see some improvements in SST 4k drivers and support in the near future. For now I will work with 54 hz. using the override file that you supplied.
The problem appears to be limited to the D500 and D700 which are based on the Tahiti AMD GPU engine where the D300 (appears to be working fine) is based on the Pitcairn AMD GPU engine, maybe this is a coincidence or a helpful hint to a solution. Also, the monitor suppliers need to work closely with Apple and AMD to get this fixed to better support SST technology as it appears to be here to stay.
I may be putting Windows on the Mac Pro but I was holding off, trying to migrate all my work under OSX. At least for now, a 90% solution is here thanks to you.
-
Jul 22, 2014 2:48 AM in response to chriskutaby ToniMaccaroni,Hello Chriskuta, what Mac Book Pro are you using? The 15" with Nvidia graphics?
-
Jul 22, 2014 3:14 AM in response to ToniMaccaroniby chriskuta,ToniMaccaroni wrote
Hello Chriskuta, what Mac Book Pro are you using? The 15" with Nvidia graphics?
Retina, 15-inch, Late 2013 with NVIDIA GeForce GT 750M
-
Jul 24, 2014 11:32 AM in response to chriskutaby ToniMaccaroni,ok,thanks. Sorry to ask again. Two questions:
1. What Brand is your "old" DP-2-MiniDP cable that you are using?
2. The MP with D400 is only €500 more than the MBP with nvidia graphics though. So what would you advice, an MBP or a MP?
-
Jul 25, 2014 4:47 PM in response to digitalcolemanby scott265,Howdy all, I'm having a bear of a time trying to get this optimized. I've been able to get only 40Hz max with the
Samsung U28D590D on a late 2013 27" iMac via a mini displayport to displayport cable.
I've followed the steps outline in many of the posts about reseting SwitchResX, adding the new EDID and then
creating the custom resolution. I've been modifying the files in DisplayVendorID-4c2d, and there are currently
two files in that directory (DisplayProductID-4255 DisplayProductID-b80) and I've tried to apply the EDID to both,
together and individually.
I'm wondering if this might be a cable issue? I got the cable from Monoprice (via Amazon) and I can't find
anywhere that it specifies DP 1.2 compliant.
I can get full resolution under windows 7.
Any ideas of things to try?
Thanks,
Scott
-
Jul 25, 2014 5:17 PM in response to scott265by Daniel Hartman1,That sounds like a cable problem to me. Accel makes a good cable: Accell B143B-007J - I've used one with my AMD 7950, and get 60hz without any problems under windows. Under OSX I get the driver problem this thread talks about.
Amazon has them but ship time is pretty large (says 2-4 months, but I think it was about 2-3 weeks for me)
Not affiliated with Accell other than being a happy customer of the above and their mDP -> HDMI 1.4 active adapters.
-
Jul 25, 2014 9:46 PM in response to Daniel Hartman1by joevt,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.
-
Jul 25, 2014 10:04 PM in response to joevtby scott265,Thanks for the replies, Daniel and joevt. I think I was a little misleading in my info about it working in windows. I can definitely get full resolution in Windows, but not in bootcamp on the iMac. Full res was on a non Apple hardware hackintosh/windows combo. Sorry about that.
I just booted into Windows on the iMac and can only see the same resolution of the cinema display (2560x1440). Samsung does have some "driver" on their website for this monitor, but I don't see that it actually does anything.
Is this enough of the EDID info?
-----------------------------------------------------
------------------- RAW DATA ------------------------
-----------------------------------------------------
0 1 2 3 4 5 6 7 8 9 A B C D E F
-----------------------------------------------------
0 | 00 FF FF FF FF FF FF 00 4C 2D 80 0B 00 00 00 00
1 | 34 17 01 04 B5 3D 23 78 3A 5F B1 A2 57 4F A2 28
2 | 0F 50 54 BF EF 80 71 4F 81 00 81 C0 81 80 A9 C0
3 | B3 00 95 00 D1 00 4D D0 00 A0 F0 70 3E 80 30 20
4 | 35 00 5F 59 21 00 00 1A 56 5E 00 A0 A0 A0 29 50
5 | 30 20 35 00 5F 59 21 00 00 1A 00 00 00 FD 00 38
6 | 4B 1E 86 36 00 0A 20 20 20 20 20 20 00 00 00 FC
7 | 00 55 32 38 44 35 39 30 0A 20 20 20 20 20 01 9F
-----------------------------------------------------
0 1 2 3 4 5 6 7 8 9 A B C D E F
-----------------------------------------------------
0 | 02 03 0C F0 23 09 07 07 83 01 00 00 02 3A 80 18
1 | 71 38 2D 40 58 2C 45 00 5F 59 21 00 00 1E 00 00
2 | 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
3 | 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
4 | 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
5 | 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
6 | 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
7 | 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 97
-----------------------------------------------------
< 00FFFFFF FFFFFF00 4C2D800B 00000000 34170104 B53D2378 3A5FB1A2 574FA228 0F5054BF EF80714F 810081C0 8180A9C0 B3009500 D1004DD0 00A0F070 3E803020 35005F59 2100001A 565E00A0 A0A02950 30203500 5F592100 001A0000 00FD0038 4B1E8636 000A2020 20202020 000000FC 00553238 44353930 0A202020 2020019F 02030CF0 23090707 83010000 023A8018 71382D40 582C4500 5F592100 001E0000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000097 >
-----------------------------------------------------
{ 0x00, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0x00, 0x4C, 0x2D, 0x80, 0x0B, 0x00, 0x00, 0x00, 0x00, 0x34, 0x17, 0x01, 0x04, 0xB5, 0x3D, 0x23, 0x78, 0x3A, 0x5F, 0xB1, 0xA2, 0x57, 0x4F, 0xA2, 0x28, 0x0F, 0x50, 0x54, 0xBF, 0xEF, 0x80, 0x71, 0x4F, 0x81, 0x00, 0x81, 0xC0, 0x81, 0x80, 0xA9, 0xC0, 0xB3, 0x00, 0x95, 0x00, 0xD1, 0x00, 0x4D, 0xD0, 0x00, 0xA0, 0xF0, 0x70, 0x3E, 0x80, 0x30, 0x20, 0x35, 0x00, 0x5F, 0x59, 0x21, 0x00, 0x00, 0x1A, 0x56, 0x5E, 0x00, 0xA0, 0xA0, 0xA0, 0x29, 0x50, 0x30, 0x20, 0x35, 0x00, 0x5F, 0x59, 0x21, 0x00, 0x00, 0x1A, 0x00, 0x00, 0x00, 0xFD, 0x00, 0x38, 0x4B, 0x1E, 0x86, 0x36, 0x00, 0x0A, 0x20, 0x20, 0x20, 0x20, 0x20, 0x20, 0x00, 0x00, 0x00, 0xFC, 0x00, 0x55, 0x32, 0x38, 0x44, 0x35, 0x39, 0x30, 0x0A, 0x20, 0x20, 0x20, 0x20, 0x20, 0x01, 0x9F 0x02, 0x03, 0x0C, 0xF0, 0x23, 0x09, 0x07, 0x07, 0x83, 0x01, 0x00, 0x00, 0x02, 0x3A, 0x80, 0x18, 0x71, 0x38, 0x2D, 0x40, 0x58, 0x2C, 0x45, 0x00, 0x5F, 0x59, 0x21, 0x00, 0x00, 0x1E, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x97 }
Also, interesting tidbit, I did an original EDID dump before I started messing with all this. I just did another one to get the info above. A diff shows that they do have differences. I would imagine some of the resolutions, etc, but it seemed that the hex data was different too. Is that normal?
To your other point about Thunderbolt 2 or DisplayPort 1.2, I just checked the specs. It looks like it definitely doesn't have Thunderbolt 2 or DisplayPort 1.2 capabilities. Does that mean I can never expect > 40Hz?
Thanks again.
-
Jul 26, 2014 2:37 AM in response to scott265by joevt,You pasted 3 copies of the EDID info. They are all the same as other people's EDID. The hex data shouldn't be different unless the serial numbers in the EDID are different but I think all the Samsung monitors don't have a serial number in the EDID.
For Boot Camp, you may need to download the latest NVIDIA graphics driver from NVIDIA to get 4K @ 30 Hz.
Anyway, you won't be able to get 4K 60 Hz on your iMac unless you buy an expensive ($1000?) thunderbolt to PCI express chassis with a video card.
http://www.journaldulapin.com/2013/08/24/a-thunderbolt-gpu-on-a-mac-how-to/
-
-
Jul 26, 2014 6:00 AM in response to scott265by Daniel Hartman1,scott,
Sorry for my misread. It looks like the iMac doesn't have thunderbolt 2 yet, so you're restricted to displayport 1.1 unfortunately. You could do 60Hz with picture-by-picture mode using DP + a mDP->HDMI adapter (or two mDP->HDMI adapters), though the computer will see as two displays, and it uses both your thunderbolt ports (though you could put accessiories that have a thunderbolt passthrough inbetween)
My 2012 rMBP has the same limitation unfortunately, and while I was hoping that a DP connection with no thunderbolt would allow it to use all the datalanes, it looks like the thunderbolt 1 setup doesn't allow that.
Glad 10.10 finally has the fixed drivers!
-
Jul 26, 2014 12:11 PM in response to bingsuby PB_NB,Well I just installed the Yosemite public beta and I am getting 3840x2160 at 60hz as soon as it booted to the desktop and the picture overlap is gone for me as well. The resolution and frequency are confirmed by the monitor information section of the monitor menu.
I have the Samsung U28D590D monitor with and dual D500's nMP.
Looks like progress!
-
Jul 28, 2014 10:48 AM in response to PB_NBby ConradWinchester,Yay, with the latest yosemite I have a PB287Q running in 4K at 60Hz.
Awesome - just how I wanted it.
-
Jul 28, 2014 12:04 PM in response to bingsuby Terscion,It's definitely progress as I can also confirm that 10.10 fixes the tearing issue. However, I was wondering if anyone else is experiencing the issue of the monitor not receiving a signal when you first turn on the Mac Pro. It's remedied by unplugging the monitor and then plugging it back in, but it's not an ideal solution.