Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

rondocap

macrumors 6502a
Original poster
Jun 18, 2011
542
341
So far everything running fine - will do some tests.

I also connected it to an iMac Pro via eGPU, my Vega 56 got a metal scope of 54,353 on Geekbench 5, and the 6800xt got 136,676

So far tested just on the iMac Pro egpu on FCPX, worked fine with no issues, seems really fast. Will test on Mac Pro later as well vs W5700X dual
 
  • Like
Reactions: AlexMaximus

LeonPro

macrumors 6502a
Jul 23, 2002
933
510
Can't wait for the MPX version of the 6900 to replace or add to my Vega II. Hopefully it would be able to decode h.265 4:2:2 10-bit on the fly without proxy editing just like the iPads. lol
 

rondocap

macrumors 6502a
Original poster
Jun 18, 2011
542
341
Can't wait for the MPX version of the 6900 to replace or add to my Vega II. Hopefully it would be able to decode h.265 4:2:2 10-bit on the fly without proxy editing just like the iPads. lol
I think the M1 Macs are the only ones that can do that for now, not even the 6800xt or a 3090 can decode that yet
 
  • Like
Reactions: chfilm

LeonPro

macrumors 6502a
Jul 23, 2002
933
510
I think the M1 Macs are the only ones that can do that for now, not even the 6800xt or a 3090 can decode that yet
Oh, that's strange they haven't built in decoding for these demanding codec in these powerful GPU. Thanks for info.
 

Liber

macrumors newbie
Jan 19, 2021
13
7
Can't wait for the MPX version of the 6900 to replace or add to my Vega II. Hopefully it would be able to decode h.265 4:2:2 10-bit on the fly without proxy editing just like the iPads. lol
h.265 4:2:2 10-but, such as iPhone 12 film in Dolby Vision videos?
I can edit it on the fly without issue.
But I think it maybe consume the CPU power not GPU.

By the way, I have confirmed with AMD, Vega II Duo doesn’t support h.265 decoding. So it is not much faster than I expected. Much slower than M1.

After enabled 6900 XT, the rendering time is same as Vega II.
 

deconstruct60

macrumors G5
Mar 10, 2009
12,493
4,053
Oh, that's strange they haven't built in decoding for these demanding codec in these powerful GPU. Thanks for info.

no all that strange at all.

Costs ( along multiple dimensions )

1. The static, fixed function decoders take up transistors ( space on the die). For a given product die allocation , more codec support means features cores/cache that are contributing to the "powerful" aspect selling the card against.

2. Also competing with other codes. AV1 got added to RDNA2 cards. The number of potential consumers of the codec is also a "cost" factor. More folks who need it pragmatically makes it cheaper to add ( since more folks will buy to get that).

3. H.265 doesn't come free. If 4:2:2 10-bit entangles more patents than 4:2:0 10-bit then it costs more to deploy.

Pile up all three factors and it particularly surprising can loose out to AV1 ( which is "free" , and has more users ).


Nvidia isn't bending over backwards to do 4:2:2 10-bit either. [ So that is kind of a cherry on top factor. Apple does. but Apple also doesn't complete in the "very powerful" GPU space either. ]

If Apple is on tract to always putting theirs ( 4:2:2 10-bit) embedded into every Mac sold ...... probably not going to be major driver for Linux/Windows market.


AMD/Nvidia next generation GPU that get to new process node ( e.g. 6nm-5nm ) then that would be a bigger chance of a "surprise" ( "strange"). More die space (because everything else shrank), looking for new ( because AV1 present already), and looking to keep average selling price at least as high ( more expensive components).


The fact Apple is not looking to do a top end , "most powerful" GPU means they are much more willing to allocate transistor budget to some niche that adds value to their mobile devices (e.g., iPad product line). They spend more on smaller dies on the bleeding edge process (e.g., 5nm for M1 ) and just pass increased component costs to customers with profit pad on top every chance they get.
 

deconstruct60

macrumors G5
Mar 10, 2009
12,493
4,053
No H265 decode, no buy :(

Already does H.265.

https://www.pugetsystems.com/labs/a...e-Decoding-is-Supported-in-Premiere-Pro-2120/


Just not H.265 4:2:2 10-bit. The blocking issue is on chroma sampling; not the overall codec. The vendors are checking the H.265 box. Just not doing all of the profiles and chroma variations (which aren't all required by the spec).



P.S. Plus Apple's willingness to work with/fund the correct driver support. ( Apple is more interested in their hardware decoder implementations than anyone else's )


P.P.S. Divinci Resolve does a bit better than Adobe in interacing with the hardware support. ( but 4:2:2 is still not really in the loop from the big (max implementation size) GPU players . Intel's iGPU in similar trade-off position as Apple's iGPU. )

 
Last edited:
  • Like
Reactions: chfilm
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.