FCPX 10.4.7. egpu problem

During import of media and generating optimized & proxy media, only the internal GPU is used ---> that is normal eGPU only generate frames they do not compress this is an OSX limitation unrelated to any version of FCPX or OSX

The speed drop is due to a potential loss of performance of FCPX nothing to do with eGPU regardless of what activity monitor says

Compression in apple devices and encoding is just a CPU job as apple uses quick sync or nothing and that uses the iGPU on the chip

Sorry you seem to not understand how it works let me tell you again

The stopwatch is unrelated to the eGPU is related to the code the software is written

An eGPU renders drawable, it can perform compression in h264 and h265 but not on OSX and ProRes is not supported full stop

Can you stop disseminate incorrect information? Have a trip on eGPU.io where some other people have finally realised that h264 compression and eGPU are unrelated it took them some time but they got there

The only GPUs that can compress real time are Nvida on Linux and Windows there is no OSX support by any program or driver

It is embarrassing how someone who does not know anything can draw conclusion on 3rd hand observations

Ok guys I was sitting in the same eGPU boat as you are. My Radeon VII in combination with the MB Pro late 2016 performed perfectly under 10.04.06 and massively degraded with 10.04.07 and 10.04.08.

Once I received my Mac Pro I decided to conduct a multitude of tests and there's certainly something wrong with FCPX that goes way beyond eGPUs when it comes to rendering and the support of 3rd Party Graphics.

So my Tests were conducted with the same Project Files at the following setups:

I cancelled the Test with both cards installed and the 580X selected, since both cards were used for rendering even tough only connected to the 580X. Funny thing this behaviour doesn't occur with the Radon VII.

One thing in my opinion becomes abundantly clear. Once you are using 3rd Party Graphics there's no reliable Support in FCPX yet. Even worse with the introduction of a second Graphics card FCPX shows weird behaviour especially when the stock card is selected (like in the case with the 580X).

On the other hand with tested cards like the 580X, that rendering Results massively improved. This also shows the massive potential Apple has on their hands if they get the upcoming releases right.

By the way in the German forum there's also somebody with the Blackmagic eGPU complaining about the same things we are.

Apple certainly needs to throw more money at bug fixing and quality control regarding their software in general.

✌️

System Preferences>Accessibility>Display. Make sure reduce transparency and increase contrast are off.

I am using external monitor and still eGPU is useless, 10.4.7 is a disaster AVOID IT, stick to 10.4.6

Did you select the egpu in the preferences?

Is your monitor attached to the egpu?

And then I read this

http://www.fcp.co/forum/4-final-cut-pro-x-fcpx/31583-i-got-an-egpu-and-i-am-ecstatic

They're off by default in a clean install. If you update from Mojave I presume they'll take whatever settings were in the older OS.

Thanks for coming back. I didn't release the problem was in Mojave. I thought it was introduced in Catalina. You're probably right though, that it's related to changes in the application for Metal.

This is a nightmare for me as i went down the mac mini route. the internal eGPU is useless but the radeon 570 was a great combo. Now I can not barley playback proxy when I have added a load of effects. This irresponsible and apple need to get this sorted now. I don't have a copy of the previous fcpx so I'm screwed. Shocking especially as they have been selling these eGPUs in their stores. It seems they only work for rendering and sharing anyway.

Even if monitor is connected and all the boxes are checked, certain tasks of FCPX such as "sharing" in certain format are using only the Built-in card... Ex: Playback is using eGPU and rendering is done on Built-in.

yes same problem here. Updated FCPX on my 2013 MBP and am not able to use the BlackMagic eGPU for playback. (Only rendering) But my work iMac is still on 10.4.6 so I'm going to copy the .app file and try to overwrite the 10.4.7 file on my MBP. Hope this works, or I'm going to loose my **** with Apple.

After talking with support, I'm not much closer to resolving the issue. Even with the setting above, on Catalina using 10.4.7 FCPX my eGPU is not used for H.264 exporting.

Testing on Mojave, still using 10.4.7, I see mixed usage of the CPU and eGPU exporting H.264 on the project I was trying and failing to export using my eGPU on Catalina.

All hope lost until until update I suppose. So glad I just bought the Sonnet eGPU from the Apple Store and now it's worthless.

Same here. The RX 590 in my Razer Core X (with an external display connected) barely works while exporting in h.264.

Thought it’d be a workaround to just export in ProRes and convert the file with Compressor later. But when I do so, the export time feels nothing different from exporting in h.264 with the iGPU of my 2019 13” MacBook Pro, even the eGPU was fired up. I assume the eGPU is busy converting the footages to ProRes to create an “optimized version” first, dunno, just disappointed.

I really don't care where it is connected, my external GPU is about 20 times faster for encoding Videos (at least it was with 10.4.6), now it is not being used unless I change all the cabling. I am doing 4K video encoding and doing it with an Intel GPU is everything but fun. Clearly this new behaviour is a major bug and Apple needs to fix it ASAP. We are not talking about an eGPU to render nice pictures but to deliver power for complex encoding calculations.

By the way it looks like I have the same issue with compressor now.