Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
There is no risk involved. This is legit, apple supported behaviour for applying custom resolutions. ;) - In case it does not work, you’d just have to delete the file and folders created, and if it does work feel free to use it or revert if you like.
The custom display files does not work on an M1 mac mini. i tested this and it is ignored. i have the exact same monitor and a an m1 mini with the latest beta 6 of the upcoming release running
 
The custom display files does not work on an M1 mac mini. i tested this and it is ignored. i have the exact same monitor and a an m1 mini with the latest beta 6 of the upcoming release running
Thank you very much for reporting back! Does it “only” not show up in the system preferences or not even with additional tools like RDM?

If not at all it is good to know that apple actually is falsely advertising the M1 Macs, as being 6K capable, while apparently they are not.
The Apple XDR Display is as much true 6K as UHD is 4K. This is especially sad, as all available 5K displays are true 5K, and Apple 4K displays (iMacs) feature true 4K resolution (unlike TVs).

  • XDR: 6016x3384 (HiDPI 3008x1692)
  • 6K: 6144x3456 (HiDPI 3072x1728)
  • UHD: 3840x2160 (HiDPI 1920x1080)
  • 4K: 4096x2304 (HiDPI 2048x1152)
 
Thank you very much for reporting back! Does it “only” not show up in the system preferences or not even with additional tools like RDM?

If not at all it is good to know that apple actually is falsely advertising the M1 Macs, as being 6K capable, while apparently they are not.
The Apple XDR Display is as much true 6K as UHD is 4K. This is especially sad, as all available 5K displays are true 5K, and Apple 4K displays (iMacs) feature true 4K resolution (unlike TVs).

  • XDR: 6016x3384 (HiDPI 3008x1692)
  • 6K: 6144x3456 (HiDPI 3072x1728)
  • UHD: 3840x2160 (HiDPI 1920x1080)
  • 4K: 4096x2304 (HiDPI 2048x1152)

It does give you an HiDPI resolution but its at 3008x1269 but not at 3360x1417 which is the ideal resolution for this monitor. 3360x1417 used to be available with the custom file on intel macs. 3008x1269 HiDPI isn't bad and would probably be great for 90% of the use cases but I use development tools and prefer the bigger space I used to get.

The problem with the custom files are that they used to work on the PCI bus and the new apple m1 display hardware configuration doesnt list it as apple internal under the pci bus any more.

there was a point where apple said they would fix the resolution issues on the m1 macs but i dont know if this would include custom resolution configurations like we could do in the past.
 
  • Like
Reactions: itsphilgeorge
It does give you an HiDPI resolution but its at 3008x1269 but not at 3360x1417 which is the ideal resolution for this monitor. 3360x1417 used to be available with the custom file on intel macs. 3008x1269 HiDPI isn't bad and would probably be great for 90% of the use cases but I use development tools and prefer the bigger space I used to get.

The problem with the custom files are that they used to work on the PCI bus and the new apple m1 display hardware configuration doesnt list it as apple internal under the pci bus any more.

there was a point where apple said they would fix the resolution issues on the m1 macs but i dont know if this would include custom resolution configurations like we could do in the past.
Override files have nothing to do with PCI bus.
Override files work on M1 Macs - but only to change the display name (maybe some other stuff we don't know about?)
 
Problem likely fixed with 11.3...it did for me. I had kernel panic upon waking from sleep when connecting to an LG ultra wide via Thunderbolt. Now resolved.
 
  • Like
Reactions: osplo
OK so it looks 11.3 did the trick. To soon to be 100% but I was able to set DP to 1.4 and now the MacBook wakes up literally every time. I did not test close lid mode just yet.

I'll reserve judgement until a few days later. But so far so good here too, with DP 1.4 and HDR turned on.
 
So the DP 1.4 is fixed with no issues whatsoever but close lid mode does not work :-/ The monitor does not wake only the backlight goes on. I kinda got used to having a laptop open so not a big deal.

I wonder how it works for you. Did anyone manage to work with a closed lid on MacBook Pro 13" and LG 34WK95U?
 
Just 2 days ago, out of the blue, DP 1.4 stops working again. (It sometimes fall back to lower res on wake from sleep.)

Not sure if it's related to 11.3.1
 
Apple have said this is likely fixed in 11.5:
1627458518350.png
 
Unfortunately no idea. All I have is the slight cryptic: "Potential fix identified...". Best bet is to open a radar ticket via the feedback tool, and keep pinging it every time you see the issue with console logs etc.
 
Just found this thread...Anyone got the issue fixed? It seems OP and I are facing a very similar issue though I am with a U2720Q instead of LG. Other than sleep-wake problem, HDR is also an issue for me...

My M1 MBA is connected to U2720Q with a single USB-C to USB-C cable (coming from the box). DisplayHDR is set and HDR is turned on in MacOS (problem exists with both Monterey & Big Sur). HDR content displays properly when the Macbook’s lid is open.

The issue starts to happen when I wake up the MacBook in clamshell mode by pressing any key on external keyboard/mouse. The U2720Q, after scanning signal, wakes up from energy-saving mode and displays in an apparently different colour visuals. The colours now look much more saturated, but HDR content and P3 colour are no longer visible. At this moment if I open MacBook’s lid, the U2720Q will go black for a second then resume normal. However, if I close the lid again (re-entering clamshell mode):

  • with MacOS Monterey: the U2720Q will go back to the colour mode (or “profile”?) in which HDR content and P3 colours can’t be displayed properly
  • with MacOS Big Sur: the U2720Q will stay normal. HDR content and P3 colours are properly displayed
This issue frustrates me a lot because I can’t flawlessly use the Macbook in clamshell mode with consistent colour profile/setting. It seems there are some sort of bug that prevents colour/HDR setting from being consistent after waking up MacOS or U2720Q.
 
I was not able to get Macbook Pro 13 M1 (Monterey 12.1) working in clamshell mode with LG 34WK95U (DP 1.4) using a single thunderbolt cable until I did the following:

1. Install teamviewer on the macbook and on another computer or mobile phone.
2. Open display settings on the macbook
3. Open teamviewer on the macbook and connect the macbook to the monitor in clamshell mode
4. Press 'space' a single time to wake the computer
5. Immediately connect to the computer via teamviewer
6. Set resolution to scaled and then back to default for display
 
I still don't understand the point of HDR, the brightness becomes so dark/faint upon turning it on that it feels pointless to use.
 
this monitor is a real pain in the ass and LG just dumped it right away after release with only coming up with one single firmware update fixing some issues. The sleep/wake issue exists for me from the very beginning after the initial release of the monitor. The so much advertised HDR didnt work for long time and after it started working, mac os looks just washed out as it is showing SDR colors in HDR mode. There is not a single alternative to this monitor (size -> resolution) It is so pitty that neither apple nor LG want to fix any of these annoying issues. Their support looks at these issues reported by nearly all customers of this model as this only happens for 0,00001% of the customers.

Sleep / wake and Bluetooth are the most common problems I have with so many MacBooks. Its crazy
 
I was not able to get Macbook Pro 13 M1 (Monterey 12.1) working in clamshell mode with LG 34WK95U (DP 1.4) using a single thunderbolt cable until I did the following:

1. Install teamviewer on the macbook and on another computer or mobile phone.
2. Open display settings on the macbook
3. Open teamviewer on the macbook and connect the macbook to the monitor in clamshell mode
4. Press 'space' a single time to wake the computer
5. Immediately connect to the computer via teamviewer
6. Set resolution to scaled and then back to default for display
Did you have any issues with resolution like people were having before? Were you able to get 5120 x 2160? Some people complained text was too small and icons too big in Final Cut Pro. Do you do any video editing or image content creation?
I'm between this (LG 34WK95U-W 34") and the LG UltraFine 27MD5KL-B 27" 16:9 5K IPS Monitor that Apple recommends for my upcoming 16" Macbook Pro M1 MAX
I'll appreciate very much your thoughts on this.
Thank you.
 
I've had this LG for several years now and have had an annoying issue when I go to wake it up, the Mac is waking up but the monitor is not. And to be clear I have 3 inputs connected. HDMI 1 from a 2014 Mac Mini. HDMI 2 from my work Surface Pro 7. Thunderbolt from 2018 MacBook Pro (which got replaced 2 weeks ago with a M1 Max Mac Studio).

What I have had for quite a while is that I have to press the button underneath 5-15 times to get the thing to finally wake up. The Mac is waiting but the screen is not coming on, not even the backlight. As of the last month or so, that behavior has changed and now no amount of pushing the power button works and I have to pull the power cord from the back and plug it back in and it comes up right away after turning back on.

So annoying. No resolution issues. The resolution is always correct. It just doesn't want to turn on.
 
I've had this LG for several years now and have had an annoying issue when I go to wake it up, the Mac is waking up but the monitor is not. And to be clear I have 3 inputs connected. HDMI 1 from a 2014 Mac Mini. HDMI 2 from my work Surface Pro 7. Thunderbolt from 2018 MacBook Pro (which got replaced 2 weeks ago with a M1 Max Mac Studio).

What I have had for quite a while is that I have to press the button underneath 5-15 times to get the thing to finally wake up. The Mac is waiting but the screen is not coming on, not even the backlight. As of the last month or so, that behavior has changed and now no amount of pushing the power button works and I have to pull the power cord from the back and plug it back in and it comes up right away after turning back on.

So annoying. No resolution issues. The resolution is always correct. It just doesn't want to turn on.
Try this next time:

When you’re sure the machine is awake and the monitor is still asleep, press Cmd-Ctrl-Q. Then press Cmd-. That’s ”Cmd” + “.”.

That combination, put the computer to sleep with the keyboard, then waking it, has been awakening my LG monitor.
 
On my Intel Mac I use a resolution of 3072*1296 for the LG 34WK95U, as it scales better to the physical pixels (5120/5*3=3072), so that within every 3 physical pixels 5 pixels are rendered. An even better physical scaling is archived with a scaled resolution of 3820*1620, as it renders 4 scaled pixels to 3 physical ones, though this is too small for my taste.
As this resolution is not available on M1 anyhow, I wondered wether my custom 3072*1296 HiDPI resolution still could be applied on the M1 Macs, as it is only slightly larger than the current maximum of 3008*1269, and actually resembles true 6K (1024*6=6144 - HiDPI for 3072), which the M1s, according to apple, are capable off. If someone could try my custom override and report back, I would be glad as it would ease my thought on wether to buy an M1 Mac.

Unzip the attached file and move it to:
Code:
/Library/Displays/Contents/Resources/Overrides/DisplayVendorID-9e6d/
Create the path, if it does not exist (might require admin permissions). After a reboot the resolution should be available as a scaled resolution in the system's display preferences.

I realize this is a super old thread, but you're on to something here. I've been struggling for years to get HiDPI working on anything other than what comes with my monitor.

On my M3 MacBook Pro with LG 34" Ultrawide (34WK95U), I get a max HiDPI resolution of 3008x1270. However when I use your file to override, I get up to 3072x1296. Not a huge difference, but it's progress.

I do see other options introduced by your override for 4096x1728, but it's LoDPI.

What are you using to make the override and is there any way to push HiDPI higher? 3840x1620 would be ideal.
 

Attachments

  • Screenshot 2024-11-22 at 7.13.48 PM.png
    Screenshot 2024-11-22 at 7.13.48 PM.png
    454 KB · Views: 27
I realize this is a super old thread, but you're on to something here. I've been struggling for years to get HiDPI working on anything other than what comes with my monitor.

On my M3 MacBook Pro with LG 34" Ultrawide (34WK95U), I get a max HiDPI resolution of 3008x1270. However when I use your file to override, I get up to 3072x1296. Not a huge difference, but it's progress.

I do see other options introduced by your override for 4096x1728, but it's LoDPI.

What are you using to make the override and is there any way to push HiDPI higher? 3840x1620 would be ideal.
Apple Silicon Macs and Intel Macs use the override files differently. What works on Intel Macs will not work on Apple Silicon Macs.

In the override file, you can see that it patches byte 146 of the EDID. If you get a copy of the EDID then you can compare it with the patched version to see what it is changing. This patch is part of the default override file from Apple.
I think the patch just removes SMPTE ST2084 from the EDID but that's only in the mtdd overlay EDID, not in the tile 1 or tile 2 EDID where the patch would make them invalid. I don't know why the overlay would be patched - it could have included that change. Because of these circumstances, I can't say for sure what it does.

In the override file, you can see there are two scaled resolutions but they're actually the same (6144 x 2592). One of them has additional flags.

SwitchResX and BetterDisplay should be able to create similar scaled resolutions (without flag changes though). However, I think Apple Silicon Macs are limited to 6144 width (this is the width of the Dell 6K display) unless the EDID has a higher width added but if you add a higher width, you can't force an Apple Silicon Mac to use a lower base resolution for scaled resolutions like you can on Intel Macs?

Code:
base64 -d <<< AAAYAAAACiA= | xxd
00000000: 0000 1800 0000 0a20                      ....... 

base64 -d <<< AAAYAAAACiAAAAAJACAAAA== | xxd
00000000: 0000 1800 0000 0a20 0000 0009 0020 0000  ....... ..... ..

printf "%d %d\n" 0x1800 0x0a20
6144 2592

echo $((6144/2)) $((2592/2))
3072 1296
 
Apple Silicon Macs and Intel Macs use the override files differently. What works on Intel Macs will not work on Apple Silicon Macs.

In the override file, you can see that it patches byte 146 of the EDID. If you get a copy of the EDID then you can compare it with the patched version to see what it is changing. This patch is part of the default override file from Apple.
I think the patch just removes SMPTE ST2084 from the EDID but that's only in the mtdd overlay EDID, not in the tile 1 or tile 2 EDID where the patch would make them invalid. I don't know why the overlay would be patched - it could have included that change. Because of these circumstances, I can't say for sure what it does.

In the override file, you can see there are two scaled resolutions but they're actually the same (6144 x 2592). One of them has additional flags.

SwitchResX and BetterDisplay should be able to create similar scaled resolutions (without flag changes though). However, I think Apple Silicon Macs are limited to 6144 width (this is the width of the Dell 6K display) unless the EDID has a higher width added but if you add a higher width, you can't force an Apple Silicon Mac to use a lower base resolution for scaled resolutions like you can on Intel Macs?

Code:
base64 -d <<< AAAYAAAACiA= | xxd
00000000: 0000 1800 0000 0a20                      .......

base64 -d <<< AAAYAAAACiAAAAAJACAAAA== | xxd
00000000: 0000 1800 0000 0a20 0000 0009 0020 0000  ....... ..... ..

printf "%d %d\n" 0x1800 0x0a20
6144 2592

echo $((6144/2)) $((2592/2))
3072 1296
Thanks for the reply and information, although I don't fully understand it. I've tried using BetterDisplay on both my M1 MacBook Pro and M3 MacBook Pro, but both are limited to 3008x1270 even with BetterDisplay setup. The BetterDisplay dev said the "non-Pro/Ultra" chips are limited, where as the Pro/Ultra chips can go a bit higher.

What gave me a bit of hope is this override was able to boost it up a little bit.

As of right now I'm still using BetterDisplay, but their mirrored virtual display solution. Which provides a great, sharp HiDPI display at any resolution. However, I find the slight lag annoying and would rather have a native solution.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.