In Mac OS X, the screen should be set to display millions of colors (I think this means RGB 8 bits per pixel but I’m not sure it couldn’t also mean one of the YCbCr formats). In that case, you’ll want to check the EDID which can be overridden in Mac OS X. There may be other issues affecting this though (not likely) such as color space and pixel depth/format (RGB, YCbCr 4:4:4/4:2:2/4:2:0, 8/10/12 bits per component). The patch should eliminate that incorrect logic. Maybe Apple’s driver is getting some information from the adapter or the 4K HDMI display that makes it choose to only allow 30 Hz.
It also means that that MacBook Pro should be able to give the mdp-hdmi adapter a SST 4K 60 Hz signal. If the U28D590D works with your MacBook Pro (Retina, 15-inch, Late 2013) at 4K 60 Hz, then it means that that MacBook Pro supports SST 4K 60 Hz and Apple’s HT206587 document is wrong. I also found this next link which emphasizes the single screen (not using MST) feature: I would like to know why a port that can do 60 Hz via MST can’t do the same using SST? Also, how difficult would it be to make an HDM 2.0 adapter that can take as input a DisplayPort MST signal?įound this link which says the U28D590D is SST: I guess the mdp-hdmi adapter requires SST? Are the DP monitors you’ve tried set to MST? The Apple document at says that the MacBook Pro (Retina, 15-inch, Late 2013) is supposed to be able to do 4K at 60 Hz using MST.
The 15 inch MacBook Pro Late 2013 has Thunderbolt 2 ports which are supposed to support DisplayPort 1.2. Maybe the patch can fix this case, or maybe a different patch could be made… 4K at 60 Hz requires 533 MHz which may be beyond the capabilities of the port. The patch I linked was originally for removing a 165 MHz pixel clock limit for HDMI to allow resolutions higher than 2K at 60 Hz. It could be that the Windows graphics driver has the same incorrect limitation as the Mac graphics driver or maybe the port just doesn’t support 4K at 60 Hz.
0 kommentar(er)
