Final Cut Pro X Roundup/Update?
 

Final Cut Pro X Roundup/Update?  

  RSS
MattRobertson
(@mattrobertson)
New Member

So I've got a host of questions, all which have not been answered by showering the forums and reading up on every topic I could find on here regarding FCP X and also 2013 Mac Pro's.

Do we have a most current Final Cut Update? I know that a while ago there were issues with people in 10.4 (FCP) with the eGPU only being used for playback and not rendering and exporting which is crucial to it's use. Do we have an update on the status of that?

Something that I can't seem to get a clear answer on is does Final Cut use all available GPU's as well as the external when playing back, rendering, and exporting? I have a 2013 Mac Pro d500 and would like to see if I can add a Vega (obviously using an adapter to TB2 and the script) and if Final Cut will indeed use all 3 and at which percentages of usage.

I'm struggling to find real data and input on how the performance increase is with FCP X, and unfortunately what used to be a good text, Bruce X, really isn't a great test any more, and I've only seen a couple Bruce X tests posted anyways.

If you are using a Vega card with final cut, how is it going? I'm especially interested if I can find any Mac Pro users to chime in, only found a couple that were using a 2013 and had a non-nvidia card.

Thanks!

Pending: Add my system information and expected eGPU configuration to my signature to give context to my posts

ReplyQuote
Posted : Feb 6, 2019 2:32 am
mac_editor
(@mac_editor)
Noble Member Moderator

App developers need to specifically code in multiple GPU support. At best we can force eGPU (single typically) use on FCP for both timeline and exporting using set-eGPU, or setting the appropriate preference (macOS Mojave or later).

I use FCP with a Vega 64 (on 2018 15" MBP) and it's been awesome so far. I just wish Apple would update the app to use all available GPUs so that my internal GPUs do something as well.

This post was modified 4 months ago

purge-wrangler.shpurge-nvda.shset-eGPU.shautomate-eGPU EFI Installer
----
Troubleshooting eGPUs on macOS
Command Line Swiss Knife
eGPU Hardware Chart
Multiple Build Guides
----
Current: MacBook Pro RP560X + 480/R9 Fury/Vega 64 | GTX 780/1070
Previous: 2014 MacBook Pro 750M + 480/R9 Fury | GTX 780/980 Ti/1070

ReplyQuote
Posted : Feb 6, 2019 4:51 am
paulspain liked
FCPXUserGermany
(@fcpxusergermany)
Active Member
Posted by: MattRobertson

...

I'm struggling to find real data and input on how the performance increase is with FCP X, and unfortunately what used to be a good text, Bruce X, really isn't a great test any more, and I've only seen a couple Bruce X tests posted anyways.

If you are using a Vega card with final cut, how is it going?

 

here is some of the testing I did with the Vega64 and RX580:

and here is a option so FCPX (and other apps) is "forced" to Prefer External GPU:

MacBook Pro with Touch Bar (15-inch, 2016) , AMD Radeon Pro 450 2GB, MacOS 10.14.2, Razer Core X + ASUS Radeon Vega64 8GB, FCPX 10.4.5

ReplyQuote
Posted : Feb 9, 2019 1:57 am
Seotheneo
(@seotheneo)
Active Member

This looks great!

Pending: Add my system information and expected eGPU configuration to my signature to give context to my posts

ReplyQuote
Posted : Feb 9, 2019 4:27 am
limozeen
(@limozeen)
Active Member

I find that it makes playback and editing of 4K 60 fps footage like butter. Which is pretty amazing on its own, actually. The impact on render / export times varies dramatically, from no change to dramatic improvement. I'm happy, and this has so much room to mature, too.

Pending: Add my system information and expected eGPU configuration to my signature to give context to my posts

ReplyQuote
Posted : Mar 8, 2019 9:48 pm
theitsage liked
Robin_Martin
(@robin_martin)
Eminent Member

I just built a Radeon VII Razer Core X setup for FCPX on my 2018 MBP. Looking forward to putting it through its paces once Apple adds support in Mojave.

I've dabbled a bit in the 10.14.4 beta build and it looks encouraging!

2018 MBP i9, 32GB, Vega 20; Razer Core X, Radeon VII

ReplyQuote
Posted : Mar 11, 2019 5:25 pm
paulspain
(@paulspain)
New Member
Posted by: mac_editor

App developers need to specifically code in multiple GPU support. At best we can force eGPU (single typically) use on FCP for both timeline and exporting using set-eGPU, or setting the appropriate preference (macOS Mojave or later).

I use FCP with a Vega 64 (on 2018 15" MBP) and it's been awesome so far. I just wish Apple would update the app to use all available GPUs so that my internal GPUs do something as well.

Excuse me, what did you do to make Vega 64 work with FCP? I also own a Vega 64 and my FCP takes HOURS to export a 30sec video (with multiple effects, yeah, but I think it's too much time anyway). Playback and editing is fine, but when it comes to rendering it doesn't work at all for me, although System Monitor says the Vega 64 is working. I'm desperate 😥

Pending: Add my system information and expected eGPU configuration to my signature to give context to my posts

ReplyQuote
Posted : Apr 17, 2019 10:35 pm
mac_editor
(@mac_editor)
Noble Member Moderator

@paulspain it’s written in the message you quoted, but for reference: https://support.apple.com/en-us/HT209134

Set that option. That’s the best FCP can do at this time.

purge-wrangler.shpurge-nvda.shset-eGPU.shautomate-eGPU EFI Installer
----
Troubleshooting eGPUs on macOS
Command Line Swiss Knife
eGPU Hardware Chart
Multiple Build Guides
----
Current: MacBook Pro RP560X + 480/R9 Fury/Vega 64 | GTX 780/1070
Previous: 2014 MacBook Pro 750M + 480/R9 Fury | GTX 780/980 Ti/1070

ReplyQuote
Posted : Apr 18, 2019 6:10 am