Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
LG 31MU97 4k Display
- Thread starter Zorn
- Start date
- Sort by reaction score
No Support?
Did you get anything useful out of Apple /LG Support? - Before returning your new MBPr(11,5).
Did you get anything useful out of Apple /LG Support? - Before returning your new MBPr(11,5).
In case it helps anyone, I originally purchased an early 2015 13" MacBook Pro in late March to use with the LG 31MU97-B at its full native resolution of 4096x2160 @ 60 Hz refresh. As we now know, the monitor will support only 3840x2160 @ 60 Hz, without the option of choosing a lower refresh rate to increase the resolution. Additionally, the monitor will not support any 17:9 resolution below 4096x2160—only 16:9 resolutions are supported.
Fast forward to today... the monitor works at its full native resolution, 4096x2160 @ 60 Hz, with a mid-2015 15" MacBook Pro with AMD Radeon R9 M370X graphics. And yes, it is a beautiful thing. I haven't had any signal dropouts, flickering, or other issues previously discussed when using either the included LG DisplayPort cable or the StarTech 3 ft. HBR2 DisplayPort cable (http://www.amazon.com/gp/product/B003TSTDI0).
I had a support incident open with Apple the entire time, and they tried to help get this monitor work at its native resolution with the 13" MacBook Pro, but nothing we tried (we read every post in this blog, and reached out to Stephane from SwitchResX) could get it working past 3840x2160.
So in summary, it sounds like for now this monitor requires a Mac with a discrete GPU to function at full spec. It's possible that a future OS X update may address this limitation for non-discrete GPU Macs, as even with my current 15" MacBook Pro, System Information shows that the integrated Intel Iris Pro is driving the pixels, so clearly the integrated GPU can handle it. However, note that the 13" MacBook Pro Intel Iris 6100 GPU may be weaker, may overheat, or may have some other issue that is affecting Apple's decision to ultimately support it at the full DCI 4k spec.
Happy to answer any other questions about my experience.
Fast forward to today... the monitor works at its full native resolution, 4096x2160 @ 60 Hz, with a mid-2015 15" MacBook Pro with AMD Radeon R9 M370X graphics. And yes, it is a beautiful thing. I haven't had any signal dropouts, flickering, or other issues previously discussed when using either the included LG DisplayPort cable or the StarTech 3 ft. HBR2 DisplayPort cable (http://www.amazon.com/gp/product/B003TSTDI0).
I had a support incident open with Apple the entire time, and they tried to help get this monitor work at its native resolution with the 13" MacBook Pro, but nothing we tried (we read every post in this blog, and reached out to Stephane from SwitchResX) could get it working past 3840x2160.
So in summary, it sounds like for now this monitor requires a Mac with a discrete GPU to function at full spec. It's possible that a future OS X update may address this limitation for non-discrete GPU Macs, as even with my current 15" MacBook Pro, System Information shows that the integrated Intel Iris Pro is driving the pixels, so clearly the integrated GPU can handle it. However, note that the 13" MacBook Pro Intel Iris 6100 GPU may be weaker, may overheat, or may have some other issue that is affecting Apple's decision to ultimately support it at the full DCI 4k spec.
Happy to answer any other questions about my experience.
As an Amazon Associate, MacRumors earns a commission from qualifying purchases made through links in this post.
send a screen shot of it with final cut x opened to me.
As an Amazon Associate, MacRumors earns a commission from qualifying purchases made through links in this post.
Huh... It must be my monitor then, I had constant (every 20-40 seconds) full screen flickers with the supplied cable. Didn't try it with another cable and didn't involve support as it worked fine with my Late 2013 rMBP.
As an Amazon Associate, MacRumors earns a commission from qualifying purchases made through links in this post.
Sorry, I don't have Final Cut X. I use it mostly for business and web. Tried some YouTube 4k videos, and they looked good—no image tearing during motion. It's not as nice as a high end plasma or LCD TV for watching videos, but it displays a very sharp, paper-like image for business and web apps.
I guess we need to wait for the LG-31MU97-Z thunderbolt/2 version of the monitor. Maybe that will be filcker-free running full 4k(4096x2160)@60Hz.
I picked up one of these displays tonight. Long story short- it will be going back first thing in the morning.
I've read a bit about the monitor on these forums, as well as Amazon reviews so I was already prepared with multiple cables in case I had issues (all DP 1.2 rated, and both mini->mini DP, as well as regular->mini DP connectors). Right from the start the screen went blank for several seconds every 10-20 seconds or so. Absolutely unusable.
Toggling the Display Port 1.2 setting within the settings menu seemed to not go blank, but then again I did not test this for very long because at DP1.1 it was miserable to use at the much lower refresh rate. Tried every cable I had, and no change in the behavior. Back in the box it went.
This was tested with my week old 2015 Macbook Pro Retina (with GPU).
Oh god. Not what I wanted to read. I thought this version was thunderbolt 2. It was when I searched for it on amazon.
Yeah, I was hopeful seeing the above post by JesseRPI. Microcenter had it for $1199 which seems to be a good price for the display.
But, it was simply not usable in any way that I'm willing to put up with. Reading the reviews on Amazon and on here, way too many similiar instances or chasing down this or that "magic cable," usually followed up shortly after with "had to return it".
I'll wait for a proper solution, until then back to the "old" Thunderbolt Cinema display that just works.
But, it was simply not usable in any way that I'm willing to put up with. Reading the reviews on Amazon and on here, way too many similiar instances or chasing down this or that "magic cable," usually followed up shortly after with "had to return it".
I'll wait for a proper solution, until then back to the "old" Thunderbolt Cinema display that just works.
Maybe I got lucky with mine and there are just a lot of defective units coming from the factory. But thus far, knock on wood, everything is working fine. I also have DP 1.2 enabled in the LCD menu settings. Mine came from Amazon via BeachCamera. I think their return policy is 45 days.
has anyone tried a apple thunderbolt cord. I feel like that mite the be the answer to this.
Did you get the old (DisplayPort) LG-31MU97 version, or the new (Thunderbolt-2) LG-31MU97-Z version? And if so, then where did you find it? Did not know the "Z" monitor had been released. (And don't see it listed via the big retailers yet).
LG-31MU97Z - Announcement NAB (15th April 2015).
http://4k.com/news/lg-31mu97z-offers-thunderbolt-2-support-true-4k-resolution-6856/
Last edited:
You're right - my apologies. The LG-31MU97-B (DisplayPort) monitor is the Current version of course. There has been no indication of a release date (or list price) for the proposed LG-31MU97-Z (Thunderbolt-2) edition. Thou when it does eventually arrive, the "Z" really should play well with Mac devices. Or else, why bother making/marketing it? And the sibling 34UC97-B (released at about the same time last year) has always been a T2 monitor, so this upgrade should not be too much of a leap for LG.
Last edited:
hey all!
haven't checked in for a while. still having the same problems with the LGs. i just live with it now.
these new "z" versions have some promise... maybe, i guess. i'm entirely leery of LG as a company now, which is a shame as i was pretty excited about their OLED TVs up until this happened.
in any event, i have recieved a couple of vague and even angry comments to my youtube video detailing this problem. both comments indicated that this is an apple / mac pro / AMD problem, and nothing to do with the monitors.
again, i'd probably believe that... the way apple changed their officially supported list to suddenly exclude specifics left a very bad taste in my mouth.
and rdav... LG would market a TB-based 4K display that doesn't work with mac just as well as they did an HDMI / Displayport 1.2 monitor that doesn't work with a mac, i'd guess.
cheers,
c
haven't checked in for a while. still having the same problems with the LGs. i just live with it now.
these new "z" versions have some promise... maybe, i guess. i'm entirely leery of LG as a company now, which is a shame as i was pretty excited about their OLED TVs up until this happened.
in any event, i have recieved a couple of vague and even angry comments to my youtube video detailing this problem. both comments indicated that this is an apple / mac pro / AMD problem, and nothing to do with the monitors.
again, i'd probably believe that... the way apple changed their officially supported list to suddenly exclude specifics left a very bad taste in my mouth.
and rdav... LG would market a TB-based 4K display that doesn't work with mac just as well as they did an HDMI / Displayport 1.2 monitor that doesn't work with a mac, i'd guess.
cheers,
c
So,
Has anyone tried two of these monitors connected up to 1 2015 15" Macbook Pro with the M370X?
I can't get a straight answer out of Apple, I'm trying to get something Apple to drive these two monitors, was considering a Mac Pro, but if I can do it with a 2015 Macbook Pro, I'd rather get something portable and more up to date.
Previously was running them at 3072x1620 at 50Hz (both) from my Mid-2012 rMBP and they worked fine.
Thinking of going and getting the MBP From Best Buy to Test, but would be good if anyone has tried it already.
Thanx
Has anyone tried two of these monitors connected up to 1 2015 15" Macbook Pro with the M370X?
I can't get a straight answer out of Apple, I'm trying to get something Apple to drive these two monitors, was considering a Mac Pro, but if I can do it with a 2015 Macbook Pro, I'd rather get something portable and more up to date.
Previously was running them at 3072x1620 at 50Hz (both) from my Mid-2012 rMBP and they worked fine.
Thinking of going and getting the MBP From Best Buy to Test, but would be good if anyone has tried it already.
Thanx
I, I just got one of the screens. My mac pro is currently being shipped with a new 680, so I'm trying it on my mit 2014 13" retina macbook pro.
I'm using the supplied mini DisplayPort cable, but the maximum resolution I can get it into is 3840x2160@30hz.
Does that have something to do with the EDIT issue mentioned earlier in this thread? Didn't apple fix that with 10.10.3 *which i'm running?
What's the maximum resolution I should technically be able to get out of the 13"? Shouldn't it be able to do 4k?
If it's still that EDID issue: can someone please post this solution file? I've read almost the whole thread once, but I can't find it anymore *without reading everyhting again).
edit:
ah ok. well, looks like I'm going to have to wait for my mac pro then. Thanks
Another thing:
did anyone notice a loud "click" sound coming from the monitor whenever you change the resolution via HDMI to 2560x1440? o__º I have this every time, and it's only that resolution so far.
EDIT 2:
I think I sort of got it to work at 4096x2160@60hz on my mid 2014 retina mbp, but I think you are so going to facepalm
I think this video explains everything:
I used the Display's side-by-side mode to display two 2048x2160@60hz signals (one HDMI, oneDisplayPort). The resolutions were created with SwitchResX.
Needless to say, it's ultra-hacky. The colors are slightly different, and OS X thinks it's two screen, so windows will only be on either side. You can't even get a wallpaper to stretch across two screens.
But at least I can use the native resolution for now
I'm using the supplied mini DisplayPort cable, but the maximum resolution I can get it into is 3840x2160@30hz.
Does that have something to do with the EDIT issue mentioned earlier in this thread? Didn't apple fix that with 10.10.3 *which i'm running?
What's the maximum resolution I should technically be able to get out of the 13"? Shouldn't it be able to do 4k?
If it's still that EDID issue: can someone please post this solution file? I've read almost the whole thread once, but I can't find it anymore *without reading everyhting again).
edit:
ah ok. well, looks like I'm going to have to wait for my mac pro then. Thanks
Another thing:
did anyone notice a loud "click" sound coming from the monitor whenever you change the resolution via HDMI to 2560x1440? o__º I have this every time, and it's only that resolution so far.
EDIT 2:
I think I sort of got it to work at 4096x2160@60hz on my mid 2014 retina mbp, but I think you are so going to facepalm
I think this video explains everything:
I used the Display's side-by-side mode to display two 2048x2160@60hz signals (one HDMI, oneDisplayPort). The resolutions were created with SwitchResX.
Needless to say, it's ultra-hacky. The colors are slightly different, and OS X thinks it's two screen, so windows will only be on either side. You can't even get a wallpaper to stretch across two screens.
But at least I can use the native resolution for now
Last edited:
I've got exactly the same problem. From my mid 2014 15" macbook pro (integrated graphics), maxed out at 3840x2160 @60Hz, (display port, hdmi, switchresx, edid files, every possible way). The only exception was with a clean bootcamp windows 10 install, 4096*2160 @30Hz through HDMI (mini display port still stuck with 3840 x 2160).
So far everyone get a mbp outputing native 4096*2160 got discrete graphics. It must be a driver related issue with the intel integrated graphics chip. Apple support claim there shouldn't be such a difference between IGP and DGP, and they simply don't have a clue why this is happening.
So far everyone get a mbp outputing native 4096*2160 got discrete graphics. It must be a driver related issue with the intel integrated graphics chip. Apple support claim there shouldn't be such a difference between IGP and DGP, and they simply don't have a clue why this is happening.
Looks like OS-X 10.11 may be more accommodating to "true 4k" screens. And that the iMac(21.5)Retina will sport a 4096x2304 [16:9] panel. Which matches the 218dpi for the current iMac(27.0)Retina. Viz:
http://arstechnica.co.uk/apple/2015...ces-possible-4k-mac-with-quad-core-broadwell/
http://arstechnica.co.uk/apple/2015...ces-possible-4k-mac-with-quad-core-broadwell/
guys get the s version. Zero lag, just got it and use it with my fully loaded 2015 as my daily driver.
