FCPX 10.4.7. egpu problem

Used time machine. Other ways are there just google it. But once your libraries are updated to 4.7 you can’t use on 4.6 unless you go back using time machine backup. Totally worth it for me

If you have active projects that you have already updated, you can export the xml file and reopen it in 10.4.6 I had to do that to revert a few projects to the old version

I have exactly the same problem (still on Mojave). The egpu is not used for playback. With 10.4.7 you don't have the option for "prefer external EGPU" when right click -> get info. You do have the option in FCPX itself (preferences, playback) and it shows the EGPU and I can select it. But it doesn't use it for playback while with the previous version of FCPX also for playback the EGPU was used.

How did you go back from 10.4.7 to 10.4.6, because currently FCPX is useless to me.

Just want to add that proxy generation does not use the eGPU anymore under 10.4.7 (reverts to built-in). Monitor connected to eGPU or not. Works perfectly in 10.4.6.

If this whole thread of issues is not seen as a bug by Apple, they need to be absolutely clear what exactly is accelerated by the eGPU and for which you need to actually work off of an external monitor as a primary display. But I really hope that's not the case.

Just been on the phone to them and the guy was really helpful. So he asked me to get everyone to ring in and explain the problems they are having. The engineers do not read these forums as said above. He has a couple of people with the same issues but he said he needs much more data to take to the engineers for a fix. He is sending me an email with instructions to get a screen capture and send some logs so they can look into things further. I am still on Mojave and I think a lot of the problems are on Catalina.... could be wrong on that. I am having play back issues and some when exporting. Get on the phone, he said if a lot do it using that link from janne76 then it will get fixed... could not say when.

Titokane is absolutely right here. I have exactly the same behaviour as Titokane does. I have one external monitor connected directly to the eGPU, and the eGPU is connected to my 13" macbook pro. Even when FCPX is running on the external monitor with version higher than 10.4.6 the eGPU is not used and the performance of FCPX is so bad it is useless for me.

With 10.4.6, doesn't matter how I connect (directly or indirectly), if the eGPU is connected, it is used and the performance is as expected.

I hope Interceptor121 is wrong and Apple does do something about this. If it will stay like this, FCPX is useless and I (and many others) would be forced to use something else (like Resolve)

The VEGA 64 in an egpu worked VERY well with h.264 rendering/exporting in 10.4.6 (and 10.4.x before that) in OSX but the bug that the rest of us has experienced is VERY REAL. Continuing to argue your single & isolated position, won't make it true for the rest of us.

Render times on my 13" MBP and 2018 Mac Mini went (in my workflow) from 4-5 mins with the egpu being used on Render to 30+ mins in 10.4.7 and 10.4.8, for the exact same project/export. This bug IS VERY REAL!

Interceptor121, the facts is that 10.4.6 is using the eGPU while you're exporting to H264 a unrendered timeline.

10.4.7 and 10.4.8 don't.

It's a big regression, and for this raison 10.4.7 and 10.4.8 are not usable (for me)

I have this question too.

My environment is MBA 2018（10.15 Catalina）+eGPU(NODE PRO+RADEON Vega 56 @ SAPPHIRE).

I suspected it was 10.15 Catalina.

But that was a mistake. Returning to 10.14 Moyave did not change the results.

So I suspected GPU this time.

Because I found a note that Vega was the cause.

I prepared the RX470 for verification.The result is as shown in the image.

Although the same video is encoded, the usage rate is completely different.

I probably think there is a problem between Vega and FCPX.

The reason is that there are cases where Vega performs processing depending on the operation.

However, other applications may not use Vega, so you may need to suspect the driver.

I want to Apple. To solve this FCPX problem.

In the case of the RX5600, since the inside has changed, I don't think that the same trouble will occur, but I hope that the report will go up.

Sorry for the machine translated English, but thank you for reading to the end.

I long for a solution to the problem.

I have the same issue. The option has been removed not because of Catalina but because of the FCPX update. You can select the eGPU from within the FCPX but it doest seem to work.

If you have a system backup you can reload it from there.

Rhe release notes for 10.4.7 say that you now can select which gpu, internal or external, to use.

I haven’t tried it yet but I take that to mean that there somewhere in the interface where you can make that choice-thus it would make sense to do away with the setting in the Get Info Window.

I think the setting was just removed because a manual setting was no longer needed. FCPX 10.4.7 works perfectly fine with my Vega 56 eGPU on Mohave and now on Catalina. Playback is clearly using the eGPU according to Activity Monitor.

Maybe it is because I have a Mac mini with no dedicated internal GPU but it seems to use my eGPU right out of the box. Perhaps systems with a dedicated internal GPU don't really work with the automatic selection. Apple should probably bring back the optional setting to prefer GPU since a lot of eGPU users are MBP 15" users.

One other issue I did find however is that many of the share formats in FCPX will not use the eGPU. Any of the Apple Devices share options will default to the internal GPU. Selecting Master and ProRes or Master and h.264 as the codec will however use the eGPU I select in the preferences so I know FCPX will work with the eGPU. It just seems to be specific encoders that will not use it.

Guys, sorry but I am trying to help from memory. My eGPU is an Akitio one with NVIDIA cards which Apple killed with High Sierra.

I just remember setting the eGPU prefer in finder and then in system preferences>displays - arrangement tab, I had to drag the white bar onto the eGPU Monitor for FCPX to use the eGPU. See my screen grab. Bottom screen is my laptop and I moved the bar so the system knows to use that GPU.

Try that or has this completely changed?

I currently have: Still on Mojave

rMBP 15.5" 2019 model connected to Akitio Thunder3 Dock Pro via TB3 cable. (BottomDisplay)

Then an Samsung 28 UHD Monitor connected via Display Post on the Dock. Top Left Display)

And Apple 27" Display also connected to the Dock via TB2 cable and Akitio TB3/TB2 adapter.

So when I launch FCPX 10.4.7, I get Full screen Picture on the Samsung. FCPX 2 view over the Laptop screen and Apple Display according to my choice.