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.
iMac Pro not compatible with Pro Display XDR?
- Thread starter OCDMacGeek
- Start date
- Sort by reaction score
Yeah, I'm going to do my best to get some answers from support. If its truly impossible to get 6k enabled through the Blackmagic Pro eGPU, then I could just return the Blackmagic Pro eGPU. My iMac Pro is running the Pro Display XDR in 5k (and my 4k Dell display) just fine without the Blackmagic Pro eGPU.
I'd love to hear from any other user who has an unsupported Mac with TB3, as to whether a Blackmagic eGPU gets them 6k. I just tested on my MacBook Pro 15 inch (2016) with Radeon Pro 455 2 GB graphics. When I connect the Blackmagic Pro eGPU, I also only get 5k from the Pro Display XDR.
With Blackmagic themselves unable to stand behind this, and two machines not working, this could mean the support document is wrong. Maybe they meant that anyone can get 5k from the Pro Display XDR with a Blackmagic, but not 6k (even though it explicitly says the opposite).
I'd love to hear from any other user who has an unsupported Mac with TB3, as to whether a Blackmagic eGPU gets them 6k. I just tested on my MacBook Pro 15 inch (2016) with Radeon Pro 455 2 GB graphics. When I connect the Blackmagic Pro eGPU, I also only get 5k from the Pro Display XDR.
With Blackmagic themselves unable to stand behind this, and two machines not working, this could mean the support document is wrong. Maybe they meant that anyone can get 5k from the Pro Display XDR with a Blackmagic, but not 6k (even though it explicitly says the opposite).
We need AGDCDiagnose from someone getting 6K on an XDR (with or without Blackmagic eGPU) to show how it's supposed to work.
I guess we need evidence that the Blackmagic eGPU can support DisplayPort 1.4, so AGDCDiagnose output from someone with a DisplayPort 1.4 display that is not the XDR would help.
Maybe AGDCDiagnose with the XDR connected directly to the computer instead of the Blackmagic eGPU would show something different that can explain the problem with the Blackmagic eGPU.
I guess we need evidence that the Blackmagic eGPU can support DisplayPort 1.4, so AGDCDiagnose output from someone with a DisplayPort 1.4 display that is not the XDR would help.
Maybe AGDCDiagnose with the XDR connected directly to the computer instead of the Blackmagic eGPU would show something different that can explain the problem with the Blackmagic eGPU.
Maybe. I wonder if there is a difference between Blackmagic eGPU and Blackmagic eGPU Pro, besides the GPU?
Can you post results of the following commands:
This one gets EDIDs from ioreg, just in case they are different or missing from the AGDCDiagnose output.
Code:
ioreg -lw0 | perl -e '
$thepath=""; while (<>) {
if ( /^([ |]*)\+\-o (.+) </ ) { $indent = (length $1) / 2; $name = $2; $thepath =~ s|^((/[^/]*){$indent}).*|$1/$name| }
if ( /^[ |]*"([^"]*edid[^"]*)" = <(00ffffffffffff.*)>/i ) { print $thepath . "/" . $1 . " = <" . $2 . ">\n" }
}
'This command gets info about the Thunderbolt devices so we can make sure they are all Titan Ridge:
Code:
ioreg -lriw0 -k "PCI-Thunderbolt" > ioregthunderbolt.txtAlso, please run the AGDCDiagnose command with the display connected directly to the iMac Pro.
Code:
/System/Library/Extensions/AppleGraphicsControl.kext/Contents/MacOS/AGDCDiagnose -a > AGDCDiagnose_XDRConnectedToiMacPro.txt 2>&1
Last edited:
I got a call back from Apple Support. They read back a message from some senior advisor who said that Blackmagic will have a firmware update of some kind coming out soon. Blackmagic themselves didn’t confirm this yet.
Is it some kind of bug where the Titan Ridge in the Blackmagic limits DisplayPort to HBR2 when the upstream is connected to an Alpine Ridge? That would be strange.
You mention the MacBook Pro 15 inch 2016 with Radeon Pro 455. do you have any problems connecting that device without eGPU to the Pro Display? I have a 2016 model with Radeon Pro 460 and wasn’t sure if that display works...Can you confirm that without Blackmagic you can still use this 2016 MacBook Pro with this Display?
There should be according to the documentation.
This is what I was wondering - Apple probably had access to said firmware during testing and expected Blackmagic to have it released by the time the XDR hit the market.
The difference I was asking about is the behavior when connected to an XDR display. What does the documentation say is different about that? And can you give a pointer to that documentation?
Basic tech specs are at: https://www.blackmagicdesign.com/products/blackmagicegpu/
Reviews noting it uses a Titan Ridge TB3 controller: https://appleinsider.com/articles/1...olt-3-displays-but-also-for-any-usb-c-monitor and https://egpu.io/forums/thunderbolt-enclosures/blackmagic-egpu-review-apples-ultrafine-curse/
Apple support article on using the XDR with Blackmagic family eGPUs: https://support.apple.com/en-us/HT210437
Reviews noting it uses a Titan Ridge TB3 controller: https://appleinsider.com/articles/1...olt-3-displays-but-also-for-any-usb-c-monitor and https://egpu.io/forums/thunderbolt-enclosures/blackmagic-egpu-review-apples-ultrafine-curse/
Apple support article on using the XDR with Blackmagic family eGPUs: https://support.apple.com/en-us/HT210437
I just tested this for you with the MacBook Pro 15 inch 2016 with Radeon Pro 455. It works with the Pro Display XDR in 5k (without any Blackmagic eGPU), and it looks great. I think yours will work.
I've read all those. Can you point out the difference between the Blackmagic eGPU and the Blackmagic eGPU Pro that affects the Apple Pro Display XDR? You said there's a difference but I can't find it.
There should not be a difference. Best I understand it, they are the same enclosure, just the GPU card inside differs (580 vs. Vega).
Thank you so much for testing this! Hope you will get yours to work as well! Merry Christmas!
For anyone with a Mac without built in Titan Ridge, don’t be expecting your Blackmagic eGPU to be getting you 6k anytime soon. I’ll live with the 5k o am getting and return the Blackmagic since it offers me nothing extra. Here is their best info right now:
“We have inquired with the head of hardware for the product line, but it is unlikely we will hear anything back until the end of the winter break, so most likely not until early January.
At this time I am not aware of any "firmware" updates. As you know there were no separate downloads for drivers or firmware for this device and the support for eGPU/eGPU pro was normally automatic through OS up to this point.”
“We have inquired with the head of hardware for the product line, but it is unlikely we will hear anything back until the end of the winter break, so most likely not until early January.
At this time I am not aware of any "firmware" updates. As you know there were no separate downloads for drivers or firmware for this device and the support for eGPU/eGPU pro was normally automatic through OS up to this point.”
You'd like to think Apple would have tested the BlackMagic eGPUs before saying they could drive an XDR at 6K, but then they never noticed the original LG Ultrafine blocked Wi-Fi signals, either. 
Seriously, I expect the configuration was tested, but I wonder if that functionality somehow was removed from macOS (perhaps as part of a bug-related regression) and they expected it to be added back with 10.15.2 (which I believe is the minimum version required for the XDR).
Seriously, I expect the configuration was tested, but I wonder if that functionality somehow was removed from macOS (perhaps as part of a bug-related regression) and they expected it to be added back with 10.15.2 (which I believe is the minimum version required for the XDR).
You'd like to think Apple would have tested the BlackMagic eGPUs before saying they could drive an XDR at 6K, but then they never noticed the original LG Ultrafine blocked Wi-Fi signals, either.
Seriously, I expect the configuration was tested, but I wonder if that functionality somehow was removed from macOS (perhaps as part of a bug-related regression) and they expected it to be added back with 10.15.2 (which I believe is the minimum version required for the XDR).
The latest beta didn’t help either, FYI. I gave that a shot to see if the fix was included in that.
Still need
1) an AGDCDiagnose output for a normal DisplayPort 1.4 display connected to the Blackmagic eGPU Pro to prove it can connect with HBR3.
2) an AGDCDiagnose output for a XDR display that works at 6K to prove that it uses HBR3 to support 6K.
Possible workaround: if the Blackmagic eGPU won't output dual HBR3, then maybe a Titan Ridge dock connected to the Blackmagic eGPU will? But that is unlikely because the DisplayPort signals are still Thunderbolt until it gets to the XDR's Thunderbolt controller. Adding another Thunderbolt controller would probably not change anything.
1) an AGDCDiagnose output for a normal DisplayPort 1.4 display connected to the Blackmagic eGPU Pro to prove it can connect with HBR3.
2) an AGDCDiagnose output for a XDR display that works at 6K to prove that it uses HBR3 to support 6K.
Possible workaround: if the Blackmagic eGPU won't output dual HBR3, then maybe a Titan Ridge dock connected to the Blackmagic eGPU will? But that is unlikely because the DisplayPort signals are still Thunderbolt until it gets to the XDR's Thunderbolt controller. Adding another Thunderbolt controller would probably not change anything.
Apple should really be updating their XDR Display Tech Specs / Compatibility section. It still states:
Grossly misleading, given Blackmagic GPU adds nothing here.
Grossly misleading, given Blackmagic GPU adds nothing here.
Are you going to keep it and use it in 5k, like I settled on? It is disappointing, but it looks great and I definitely don’t want to send it back (or switch machines). I am conflicted on keeping the Blackmagic and hoping for a macOS update (Blackmagic tech support seems to think they don’t do firmware updates, and they only provide built in drivers for macOS), or just returning it.
It’s so weird, that phrasing actually has changed now. It no longer specifically says it will work in 6k for devices in that list. It used to, for certain. Now it only says it will be compatible but no reference to the resolution. Maybe this means they botched it and know the Blackmagic won’t do 6k.
“Compatibility
Pro Display XDR is compatible with the following Mac models running macOS Catalina 10.15.2 or later:
Mac Pro (2019) with MPX Module GPUs
15-inch MacBook Pro (2018 or later)
16-inch MacBook Pro (2019)
21.5-inch iMac (2019)
27-inch iMac (2019)
Any Mac model with Thunderbolt 3 ports paired with Blackmagic eGPU or Blackmagic eGPU Pro”
Edit, nevermind, it’s this one that says so specifically: https://support.apple.com/en-us/HT210437
“Compatible Mac models
Pro Display XDR supports a resolution of 6016 x 3384 with 10bpc on these Mac models:
Mac Pro introduced in 2019
16-inch MacBook Pro introduced in 2019
15-inch MacBook Pro introduced in 2018 or later
iMac introduced in 2019
Mac computers with Thunderbolt 3 ports connected to Blackmagic eGPU or Blackmagic eGPU Pro”
Last edited:
Ohh I'm definitely keeping the display. This is replacing a Thunderbolt Display that was starting to go on the fritz - and 5k is still far better than before.
I still have some hope that Apple will get the 6K situation figured out...
Nick
The firmware update is available at https://www.blackmagicdesign.com/uk/support/
Does it work?
Does AGDCDiagnose show HBR3 connection after applying the firmware update?
Does it work?
Does AGDCDiagnose show HBR3 connection after applying the firmware update?
It works! it took two reboots (one after unpacking the .pkg, and another after a toast popped up saying firmware had been updated please reboot). I'm now running as 32-inch (6016 x 3384)
Nick
[automerge]1577690472[/automerge]
And AGDCDiagnose shows the following as connectivity to the eGPU
* 2: [DP 1.4 4 x HBR2] Status: [4 x HBR2 7777] caps [features 0x101001b, p_encoding 0xd] Sink OUI:000-016-250 D1baba [068-049-098-097-098-097] HW Version: 17 FW Version: 6.55
* 3: [DP 1.4 4 x HBR3] Status: [4 x HBR2 7777] caps [features 0x101001b, p_encoding 0xd] Sink OUI:000-016-250 D1baba [068-049-098-097-098-097] HW Version: 17 FW Version: 6.55
Nick
[automerge]1577690472[/automerge]
And AGDCDiagnose shows the following as connectivity to the eGPU
* 2: [DP 1.4 4 x HBR2] Status: [4 x HBR2 7777] caps [features 0x101001b, p_encoding 0xd] Sink OUI:000-016-250 D1baba [068-049-098-097-098-097] HW Version: 17 FW Version: 6.55
* 3: [DP 1.4 4 x HBR3] Status: [4 x HBR2 7777] caps [features 0x101001b, p_encoding 0xd] Sink OUI:000-016-250 D1baba [068-049-098-097-098-097] HW Version: 17 FW Version: 6.55
Last edited: