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.
MP All Models SOLVED: 8k Displays Running on Mac Pro? Any? What Video cards would work that support 8k HDMI 2.1/Displayport 1.4/2.0 displays on Mac Pro? YES you can
- Thread starter ZombiePhysicist
- Start date
- Sort by reaction score
I'd give my left...you know what...to have a 32" 8k monitor running at 4k Retina on an Apple Silicon based Mac
Sounds like the 32" DP Dell 8k monitor would work for you.
The display cannot be running at 8K60 without a proper two cable connection. RDM and web-based tools and macOS report only the framebuffer size - not the output resolution.
Use SwitchResX to view the current resolution timing info (double click the current resolution in the Current Resolutions tab of SwitchResX for the display) and check the active pixels.
Or run the latest version of AllRez. https://forums.macrumors.com/threads/mac-mini-4k-120hz.2267035/post-31199747
I imagine it would be a doable thing with the Mac's display engine, to write a screen filter that applies a concave distortion to the display, creating a virtual curved display, so the edges / periphery are displayed larger, with a keystoning to correct for perceived perspective.
That's why I was confused. I figured it must be some kind of reporting error. I did run AllRez but I don't really understand the output.
@Pressure gave it a go on his Mac Studio but no luck last I heard.
I have it working but it’s recognized as two separate monitors (3840x4320 side-by-side) on the latest macOS 12.4.
That gives me 1920x2160 HiDPI on both connections.
Can you get it working like a big single screen at 30hz as well? I think for some, that might be preferable depending on their type of work.
zip the result and post it here and I can tell you what's going on.
The first thing to look at is the current mode:
Code:
current mode by CGSGetCurrentDisplayMode (private) = 13 = { 13: id:0x8000.016 1920x1080@144.000Hz 144Hz (dens=2.0) pixels:3840x2160 resolution:163x161 32bpp 10bpc 3cpp rowbytes:15360 IOFlags:(Valid,Safe,Television,) flags:(Valid,Television,) depthFormat:8 encoding:--RRRRRRRRRRGGGGGGGGGGBBBBBBBBBB refreshRate.unk0.unk1:00900001.0000.00000001 }Then you search for the timing info for that mode using the mode id.
Code:
{ DetailedTimingInformation = { V2 id:0x8000.016 3840x2160@143.999Hz 318.957kHz 1275.830MHz (errMHz 0,0) h(48 32 80 +) v(3 5 47 -) border(h0:0 v0:0) active:3840x2160 (not scaled) inset:0x0 flags(0°,) signal() levels:0700_0300 links:2 vbext:0 vbstretch:0 vbshrink:0 encodings(420,) bpc(10,) colorimetry(BT709,) dynamicrange(TraditionalGammaSDR,) dsc(0x0 0bpp) }; DisplayModeInformation = { 3840x2160@143.999Hz maxdepth:2 flags:Valid,Safe,Television, imagesize:600x340mm }; ID = 0x8000.016; },Another thing to look for is the DisplayPort connection link rate and link lanes
Code:
00100h LINK_BW_SET: HBR3
00101h LANE_COUNT_SET: 4The included AGDCDiagnose may have additional useful info. For example an 8K dual tile display should have two connections at 3840x4320. While a single tile display should have a single 7680x4320 connection.
I could on my Intel based Mac Pro but Apple Silicon doesn't support an 8K resolution.
Applications can still be stretched over both "screens" if you disable "Displays have separate Spaces" under System Preferences -> Mission Control but the Menu Bar will not stretch over both. That's a compromise I'm willing to take to get 48Hz and 60Hz.
that's alright. I'm quite certain it's 4k@60Hz over 1 DP, but just "artificially" (?) increasing the resolution to 8K. Kind of like digitally stretching it out?
Ventura has support for Dell UP3218K 8K60,48,30,24.
https://github.com/waydabber/BetterDisplay/discussions/199#discussioncomment-3111040
But Apple made it available only to MacPro7,1 and maybe not in all cases (I'm not sure what the second check related to MacPro7,1 is for - the value being checked needs to be > 0x211). I made a WhateverGreen patch in my GitHub fork to remove those checks (boot-arg
dpd=2). It's a user patch which requires my fork of Lilu. That means you need to recompile any other Lilu dependent kexts against that version of Lilu. The patch was successful with one hackintosh so far. There may be a kernel panic in my Lilu but sometimes it works fine - not sure what's going on there (some weird C++ thingy that I had nothing to do with)...Apple limited the Dell UP3218K to 8bpc for all modes in Ventura even for modes that could support 10bpc (such as 48Hz and 24Hz). Use AllRez to get the bpc for each display mode. The 8bpc limit is in the override file for the Dell UP3218K as a EDID patch. To remove that EDID patch, you can combine the dpd patch with another patch (use
dpd=3 instead of 2) that loads override files from /Library/... instead of /System/Library/... Copy the override files to /Library/... and edit. I don't know what the result will be. Is 10bpc important? 10bpc cannot be supported at 8K60 but should work at 8K48.It's just baffling that their own display engine for the M1 Pro / Max / Ultra isn't getting support. I know it's a niche product but there must be a handful of macOS users who have it.
I was really looking forward to the single cable TB ViewSonic VP3286-8K for a possible upgrade but it has failed to materialise so far.
I mean it kinda makes sense. Originally developed for iPhone/iPad screens, there was just never a need to support anything greater until the M1 came along, and even then they only added support up to the requirements of Apple's own products, e.g. 6k. I'm sure it's possible given how capable the Apple Silicon GPU's are with editing 8K streams, it's just we probably won't see it until Apple releases their own 8K display.
I kind of disagree. Apple regularly touts 8k work flows. It should be beyond embarrassment for apple that they basically don't support 8k output to actually see the results of that work flow.
It can drive both halves of the screen at the correct resolution (3840x4320 pixels) but treats it as two separate displays on the M1 Pro / Max / Ultra.
It already works because the monitor takes two DP connections.
Oh I don't agree with it by any means, but it's totally up Apple's alley to do something like that. They either won't have proper first class support for it until they launch their own competing product or until they become commonplace enough that Apple doesn't have a choice.
That was fast! The UP3218K was released only five years ago.
I have a 2019 Mac Pro with the Radeon Pro 580X. I have a Dell UP3218K as well as 2 Cable Matters USB-C to DP the latest version 8k. Running Monterey latest update. The computer sees the monitor as 2 separate monitors 4K. Is it possible to get this monitor working 8K60 with this configuration? I saw a post about Overrides ? Can somebody explain to me exactly what I need to do to make this work. I sincerely appreciate it.
Bass
Bass
Do you have SwitchResX and/or are you familiar with Terminal commands?
If not you can always install the public beta of Ventura. That should enable 8K60 for you.
I do not have SwitchResX and I never used the Terminal on Mac, I am a Windows guy by trade .net developer but I also use Mac Pro for ProTools rig for our studio, its very sensitive to os versions and would like to stick to Monterey because of drivers ect with Avid Hardware. I am really great with instructions, would you be willing to list for me the steps I need to take to get it to work with Monterey? I would greatly appreciate it.
Bass
Sure thing, have in mind though that full support for the Dell UP3218K seems to be coming in macOS Ventura.
Right now in macOS Monterey each half of the monitor will be recognised as independent 3840x4320 pixel displays (or 1920x2160 HiDPI).
First we need to add the 3840x4320 resolution. The easiest solution is to install SwitchResX and use the 10-day trial (although seeing as you run Avid hardware and software you or the company should be able to cover the €14 license).
1. Download SwitchResX
2. Install it
3. Navigate to -> System Preferences
4. In System Preferences you should now have an SwitchResX panel
5. Open it and click on the first monitor (DELL UP3218K), then click on Custom Resolutions and lastly the + sign.
6. Add the 3840x4320 resolution (the HiDPI option will be added automatically) and reboot. SwitchResX ask if you want to save the changes, say yes.
7. After reboot go to -> System Preferences and open SwitchResX preferences
8. Launch SwitchResX Daemon (it should appear in the menu bar) and select either the full resolution (3840x4320@60Hz) or the HiDPI resolution (1920x2160@60Hz) for both monitors
The only caveat as mentioned up top is that it is recognised as two separate displays, so the menu bar will only be on one side of the screen.
To stretch applications over both "screens" you need to go to System Preferences -> Mission Control and deselect the option "Displays have separate Spaces". If you full screen an application it will only cover one side of the screen.
This should be the most straightforward way to obtain 8K60 but if this doesn't work I have two other things we can try.
Last edited:
And FYI for folks lining up your two halves of the screen with SwitchResX, be aware you can use AppleScript with SRX to get, and set the position coordinates of the displays to the precise pixel, which the monitors prefpane doesn’t allow.
Could you give an example of that?
As far as I am aware isn't that basically what you tell the OS in the com.apple.windowserver.displays.plist file found under /Library/Preferences?
Example:
Code:
<key>Configs</key>
<array>
<array>
<dict>
<key>CurrentInfo</key>
<dict>
<key>Depth</key>
<integer>10</integer>
<key>High</key>
<real>2160</real>
<key>Hz</key>
<real>48</real>
<key>IsLink</key>
<true/>
<key>OriginX</key>
<real>0.0</real>
<key>OriginY</key>
<real>0.0</real>
<key>Rotation</key>
<integer>0</integer>
<key>Scale</key>
<real>2</real>
<key>Wide</key>
<real>1920</real>
</dict>
<key>LinkDescription</key>
<dict>
<key>BitDepth</key>
<integer>10</integer>
<key>EOTF</key>
<integer>0</integer>
<key>PixelEncoding</key>
<integer>0</integer>
<key>Range</key>
<integer>1</integer>
</dict>
<key>Rotation</key>
<real>0.0</real>
</dict>
<dict>
<key>CurrentInfo</key>
<dict>
<key>Depth</key>
<integer>10</integer>
<key>High</key>
<real>2160</real>
<key>Hz</key>
<real>48</real>
<key>IsLink</key>
<true/>
<key>OriginX</key>
<real>1920</real>
<key>OriginY</key>
<real>0.0</real>
<key>Rotation</key>
<integer>0</integer>
<key>Scale</key>
<real>2</real>
<key>Wide</key>
<real>1920</real>
</dict>
<key>LinkDescription</key>
<dict>
<key>BitDepth</key>
<integer>10</integer>
<key>EOTF</key>
<integer>0</integer>
<key>PixelEncoding</key>
<integer>0</integer>
<key>Range</key>
<integer>1</integer>
</dict>
<key>Rotation</key>
<real>0.0</real>
</dict>
</array>
</array>Could you give an example of that?
I’m not at my Mac, but from an email a while back, you can run these in script editor:
Code:
tell application "SwitchResX Daemon" to get position of display 2Where display 2 is the second display, you’ll receive a return of the top left coordinates to check if the snapping in displays prepare is pixel accurate. The Y / vertical value is most likely the one that’s out.
Code:
tell application "SwitchResX Daemon" to set position of display 2 to {3840, 0}Will set the second display to have its top left corner matched to the top right corner of display 1 - the x offset is from the top left origin of display 1. That’s presuming you don’t need to use halved values for hi-dpi.