High Sierra - RX Vega & Final Cut h.264 fix

[pulpinex]

Same problem (H264 fcp exporting) with XFX RX 480 8GB.
I've to try tonight this tips (SMB_BIOS_VERSION "IM191.88Z.0058.B00.1705091711"
SMB_PRODUCT_NAME "iMac19,1"
SMB_BOARD_PRODUCT "Mac-CF21D135A7D34AA6"

Tonight I'll update my post and I'll inform you.
bye

 

[pulpinex]

Your solution worked also for my Hackintosh.
Same as your problem, but with RX 480 (XFX) 8Gb RAM.
See this post.
Thx.

 

[Robvas]

I was wondering if someone has Vega cards recognized in High Sierra. This is what I have, see attached

 

[vinste]

I was wondering if someone has Vega cards recognized in High Sierra. This is what I have, see attached

You would have a nice "AMD Radeon Vega 64" with Whatevergreen, but it does not seem to bring any functional or performance gain.

 

[kukkis]

With Vega performace seems to depend on what you use it for.

On BruceX test it flies in 11,36s compared to 980Ti’s 31,72s.

With OpenCL it’s not bad.
Geekbench OpenCL:
Vega64: 169650
980 Ti: -

Luxmark:
Vega64: 21667
980Ti: 22361

With OpenGL drivers needs improvement
CinebenchR15:
Vega64:130,34 fps
980Ti: 173,34 fps

Still can’t complain as it works well at the moment and is silent with Eiswolf 240mm AIO. If only it would be possible to undervolt and overclock Vega 64 in macOS like in Windows, it would get a major boost in performance.

 

[pioneerbb]

+1
working for me too
MSI 470 Gaming X 4Gb

 

[pulpinex]

Hi all,
Someone have issue with power management when setting iMac 19.1?
My Intelspeedstep dont like the 19.1 setting, and pstate are Lower than expected.
Do someone tested this aspect?
H264 export ok... but with speedstep?
Thx for sharing

 

[vinste]

Hi all,
Someone have issue with power management when setting iMac 19.1?
My Intelspeedstep dont like the 19.1 setting, and pstate are Lower than expected.
Do someone tested this aspect?
H264 export ok... but with speedstep?
Thx for sharing

Unfortunately, beginning with 10.13.1 beta 5, I get the forbidden sign with 19,1. It seems you will need to find another fix.
Concerning h264 export, can you please tell if you get h264 encoding hardware acceleration through your RX 480, or is it pure CPU (what are your CPU and GPU usage while exporting a fully pre-rendered project at timeline resolution?)

 

[pulpinex]

Unfortunately, beginning with 10.13.1 beta 5, I get the forbidden sign with 19,1. It seems you will need to find another fix.
Concerning h264 export, can you please tell if you get h264 encoding hardware acceleration through your RX 480, or is it pure CPU (what are your CPU and GPU usage while exporting a fully pre-rendered project at timeline resolution?)

Hi Vinste,
I upgraded to 10.13.1 beta 5 and the fix is still working.

I think that I've full GPU acceleration. I've 16-17sec with BruceX test (but not export in H264) and about 16.000 on luxmark (don't remember the exact score but more or less more than 16.000).

 

[vinste]

Hi Vinste,
I upgraded to 10.13.1 beta 5 and the fix is still working.

I think that I've full GPU acceleration. I've 16-17sec with BruceX test (but not export in H264) and about 16.000 on luxmark (don't remember the exact score but more or less more than 16.000).

I am quite interested in the influence of your fix on the encoding perfomance.
From my understanding, h264 export acceleration in FCPX is only possible with Intel Quicksync, and not with AMD nor NVidia cards. I really wonder whether your fix and configuration proves otherwise.
If you need some reference material, you could use big_buck_bunny_720p_h264.mov for instance, just drop it in a new library/new event, and from the imported media (not even dropped in a new project, to avoid rendering), share it as master h264 file.
On my consumer-grade system, it uses Intel Quicksync, together with 100-110% of CPU (out of 800%), and finishes the export in 1min25s.