new FCPX 10.4 and eGPU  

Page 3 / 4 Prev Next
 
Jared
(@jared_busch)
Eminent Member

@mac_editor You know what, as stupid as this sounds, I never thought about the difference in how FCPX plays between AMD vs Nvidia! Which you'd think I would've thought of considering the current compatibility. But now that you've brought it up, when I think about it, I've never read anyone claiming and confirming any sort of playback with an Nvidia card. Only seen folks talk about the playback with AMD cards.

Well shit...Now I'm gonna have to start looking for an AMD replacement! 

Well, I appreciate your time bud. It's helped me sort of narrow down what my issue is.

Cheers

ReplyQuote
Posted : April 17, 2018 7:36 pm
mac_editor
(@mac_editor)
Noble Member Moderator

@jared_busch finding an AMD replacement might just be expensive ;).. I'd still suggest trying macOS Sierra once. Perhaps there won't be a difference, but who knows..

purge-wrangler.shpurge-nvda.shset-eGPU.sh
----
Troubleshooting eGPUs on macOS
Command Line Swiss Knife
----
3 Build Guides

ReplyQuote
Posted : April 17, 2018 7:41 pm
Jared
(@jared_busch)
Eminent Member

@mac_editor Yea it'll be expensive, but I can offset that by selling my 1080. At the moment, I'm not really interested in testing out Sierra for a couple reasons.

1- I don't have the time to backup, downgrade, setup, test and then upgrade to HS again. I rely on my mac to earn a living. So when it's down, so is my income.
2- Even if it does make a difference, I still wouldn't stay on Sierra. It's an older OS and I HATE running on older OS's, even though I'm still on 10.13.2.

There are several online stores selling Vega 56 cards for under $1000. I should be able to sell my 1080 for $800 - $900 😉

ReplyQuote
Posted : April 17, 2018 8:12 pm
mac_editor
(@mac_editor)
Noble Member Moderator

@jared_busch It's always your call 🙂

purge-wrangler.shpurge-nvda.shset-eGPU.sh
----
Troubleshooting eGPUs on macOS
Command Line Swiss Knife
----
3 Build Guides

ReplyQuote
Posted : April 17, 2018 8:19 pm
Chippy McChipset
(@chippy-mcchipset)
Reputable Member

I don't think there's ever a reason to use NVIDIA cards with Apple's apps. Apple does not CUDA-accelerate anything which means the only reason to try is if someone has seen evidence that NVIDIA's OpenCL / Metal performance is better than AMD's in a given scenario, which I doubt. Particularly the former.

ReplyQuote
Posted : April 17, 2018 9:53 pm
Jared
(@jared_busch)
Eminent Member

Ya fair enough and I agree. I guess while shopping, my mind just kind of justified Nvidia. I shoulda just went AMD and gone hassle free (for the most part, lol)

ReplyQuote
Posted : April 18, 2018 12:23 am
ikir
 ikir
(@ikir)
Honorable Member

A new update has been released but the eGPU a is used only for some task, anyway it is is faster with eGPU anyway! Let’s hope Apple will fix this.

eGPU.it | LG 34" 4K 34UC88 curved ultrawide display
MacBook Pro 2018 Touch Bar i7 quad-core 2.7Ghz - 16GB RAM - 512GB PCIe SSD --> my Mantiz Venus extreme mod with Sapphire Nitro+ RX Vega 64

ReplyQuote
Posted : May 3, 2018 11:05 pm
dre
 dre
(@dre)
Active Member
Posted by: ikir

A new update has been released but the eGPU a is used only for some task, anyway it is is faster with eGPU anyway! Let’s hope Apple will fix this.

faster than 10.4.1? Is the gpu used for exporting at all?? I'm back on 10.3 and don't want to risk loading 10.4 till its resolved

ReplyQuote
Posted : May 3, 2018 11:22 pm
eAlchemist
(@ealchemist)
Active Member

Hey Everyone

I'm using an eGPU (Readeon 7970) successfully with FCP 10.4.2 and HS 10.13.4

I'm mostly working with 8/10bit GH5 4k footage, heavy & long timelines.
Playback / timeline eGPU acceleration working great when having the viewer-window on the monitor connected to the eGPU.
Tho, I'm actually using an LG 5K Monitor at my editing workplace. As soon as I change to a screen other then the eGPU one, the load moves to the dGPU.

There is no way of connecting the LG 5K (TB3) Monitor to an eGPU for now. The only way is using a monitor connected to the eGPU as the "Viewer".
Any workflow advice on this?

I wish to see a FCP Update which enables eGPU rendering and screen-independent eGPU acceleration / utilisation soon.
Similar to Davinci, This would improve workflows for a lot of users I believe, also for users who are working on the internal display.
This should be technically possible as far as sending data back via TB3.

Wherever this is a marketing conspiracy or not - I'd guess Apple is interested in making FCPX as attractive as possible and will give these demands priority.

Great to have a community here which keeps it rollin.

ReplyQuote
Posted : May 5, 2018 9:55 pm
ikir
 ikir
(@ikir)
Honorable Member

Last eat FinalCut Pro still doesn’t use eGPU for everything. Finger crossed for next release.

eGPU.it | LG 34" 4K 34UC88 curved ultrawide display
MacBook Pro 2018 Touch Bar i7 quad-core 2.7Ghz - 16GB RAM - 512GB PCIe SSD --> my Mantiz Venus extreme mod with Sapphire Nitro+ RX Vega 64

ReplyQuote
Posted : May 10, 2018 8:50 pm
(@nariman_gafurov)
New Member

Hello everybody. I have maccopo 2013 and egpu akitio node thinderbolt 3 with an adapter. Advise me what card to take? I choose between rx580 and vega 64

Mac Pro (2013), 12Core Xeon, 32 GB, 256gb SSD, 2xD500, AKiTiO Node
Macbook Pro 15, 2017 touch bar

ReplyQuote
Posted : May 18, 2018 5:25 pm
eAlchemist
(@ealchemist)
Active Member
Posted by: Nariman Gafurov

Hello everybody. I have maccopo 2013 and egpu akitio node thinderbolt 3 with an adapter. Advise me what card to take? I choose between rx580 and vega 64

This seems to be very off-topic? Please keep this thread about eGPU & FCPX Support.

If you ask this in the context of FCP performacne: Go for the best AMD / ATI Card that your budget will allow for. The RX580 is very good, the Vega64 surely more future-proofed.

Nothing changed so far on FCP eGPU. Still looking for a release from apple..

ReplyQuote
Posted : May 19, 2018 12:42 pm
(@nariman_gafurov)
New Member

Thank you! Yes, the speed of work, the effect filters are important for FCPX. I know that it is better to radeon, but who would advise which card which will be more powerful than d500

Mac Pro (2013), 12Core Xeon, 32 GB, 256gb SSD, 2xD500, AKiTiO Node
Macbook Pro 15, 2017 touch bar

ReplyQuote
Posted : May 20, 2018 12:26 pm
theitsage
(@itsage)
Famed Member Admin

@nariman_gafurov In OpenCL tasks, the performance level from highest to lowest is RX Vega > Dual D500s > RX 580 > Single D500. I'd say go for the RX Vega 56. It has a more reasonable power requirement and performs very close to the Vega 64 in macOS.

Best ultrabooks for eGPU use

eGPU enclosure buying guide

66 external GPU build guides

ReplyQuote
Posted : May 20, 2018 1:46 pm Username liked
dre
 dre
(@dre)
Active Member
Posted by: eAlchemist

Hey Everyone

I'm using an eGPU (Readeon 7970) successfully with FCP 10.4.2 and HS 10.13.4

I'm mostly working with 8/10bit GH5 4k footage, heavy & long timelines.
Playback / timeline eGPU acceleration working great when having the viewer-window on the monitor connected to the eGPU.
Tho, I'm actually using an LG 5K Monitor at my editing workplace. As soon as I change to a screen other then the eGPU one, the load moves to the dGPU.

There is no way of connecting the LG 5K (TB3) Monitor to an eGPU for now. The only way is using a monitor connected to the eGPU as the "Viewer".
Any workflow advice on this?

I wish to see a FCP Update which enables eGPU rendering and screen-independent eGPU acceleration / utilisation soon.
Similar to Davinci, This would improve workflows for a lot of users I believe, also for users who are working on the internal display.
This should be technically possible as far as sending data back via TB3.

Wherever this is a marketing conspiracy or not - I'd guess Apple is interested in making FCPX as attractive as possible and will give these demands priority.

Great to have a community here which keeps it rollin.

My LG tb2 monitor connects directly to my egpu using a tb2/3 dongle. 

There is a version of FCPX that renders fully using an egpu, it’s 10.3?

Not it sure how you’d describe removing this functionality but (they’ve done it with tb2 Mac users and egpu’s too). We’re a long way into 10.4 (update wise) and it looks like Apple have deliberately removed egpu render support and it looks unlikely to return in the short to medium term.

ReplyQuote
Posted : May 20, 2018 4:32 pm
(@nariman_gafurov)
New Member

Thank you! I'll probably buy vega56 ... and will there be a big loss when using the th3-th2 adapter?

Mac Pro (2013), 12Core Xeon, 32 GB, 256gb SSD, 2xD500, AKiTiO Node
Macbook Pro 15, 2017 touch bar

ReplyQuote
Posted : May 20, 2018 6:17 pm
eAlchemist
(@ealchemist)
Active Member
Posted by: dre
Posted by: eAlchemist

Hey Everyone

I'm using an eGPU (Readeon 7970) successfully with FCP 10.4.2 and HS 10.13.4

I'm mostly working with 8/10bit GH5 4k footage, heavy & long timelines.
Playback / timeline eGPU acceleration working great when having the viewer-window on the monitor connected to the eGPU.
Tho, I'm actually using an LG 5K Monitor at my editing workplace. As soon as I change to a screen other then the eGPU one, the load moves to the dGPU.

There is no way of connecting the LG 5K (TB3) Monitor to an eGPU for now. The only way is using a monitor connected to the eGPU as the "Viewer".
Any workflow advice on this?

I wish to see a FCP Update which enables eGPU rendering and screen-independent eGPU acceleration / utilisation soon.
Similar to Davinci, This would improve workflows for a lot of users I believe, also for users who are working on the internal display.
This should be technically possible as far as sending data back via TB3.

Wherever this is a marketing conspiracy or not - I'd guess Apple is interested in making FCPX as attractive as possible and will give these demands priority.

Great to have a community here which keeps it rollin.

My LG tb2 monitor connects directly to my egpu using a tb2/3 dongle. 

There is a version of FCPX that renders fully using an egpu, it’s 10.3?

Not it sure how you’d describe removing this functionality but (they’ve done it with tb2 Mac users and egpu’s too). We’re a long way into 10.4 (update wise) and it looks like Apple have deliberately removed egpu render support and it looks unlikely to return in the short to medium term.

Hey there.

Thanks for your reply. I doubt there is any GPU with TB3 nor any Thunderbolt support. What you are probably doing is using the DisplayPort signal over a thunderbolt / mDP adapter.

The LG5k Monitor is using a real Thunderbolt3 connection (with actually two DP lanes). Connected via a dongle / DP you'd only get a maximum 4k signal.

Even with the old FCP version you wouldn't get eGPU timeline accelerated on the LG5k as there is no GPU out there yet to connect it to. Davinci Resolve as an example uses a way to utilise GPUs independently of connected monitors. Therefore giving you acceleration even on an internal MacBook Monitor.

This method is much more advanced and I'd suggest apple is highly aware of their shortcomings on this side in FCP. Updates should certainly come in the future to keep the product competitive.

We'll see what time brings ;-).. 

ReplyQuote
Posted : May 22, 2018 9:17 am
mac_editor
(@mac_editor)
Noble Member Moderator

To my report regarding eGPU support for FCP, Apple Dev Relations had the following to say  -> "It's not been determined how and when the issue will be resolved." SAD. It's their typical generic response to minor bugs plaguing older hardware - but didn't expect to see it for this one.

purge-wrangler.shpurge-nvda.shset-eGPU.sh
----
Troubleshooting eGPUs on macOS
Command Line Swiss Knife
----
3 Build Guides

ReplyQuote
Posted : May 25, 2018 4:04 am Chippy McChipset and Username liked
Chippy McChipset
(@chippy-mcchipset)
Reputable Member
Posted by: mac_editor

To my report regarding eGPU support for FCP, Apple Dev Relations had the following to say  -> "It's not been determined how and when the issue will be resolved." SAD. It's their typical generic response to minor bugs plaguing older hardware - but didn't expect to see it for this one.

I think as time goes on it's their response to almost any software issue out there. Probably written by their legal team and enforced as a policy unless they have a specific fix and imminent release of said fix planned. But frustrating either way.

ReplyQuote
Posted : May 25, 2018 8:24 pm
Username
(@username)
Estimable Member

I believe this have more to do with their future business model then fixing bugs.
For the last 10 years they have changed strategic focus faster then patches have been released. And just as their pretty damn good software gain a steady growing user base they kill it and move on because it does not support their current software, hardware or service strategy.
It's as annoying as it is sad.

2012 Mac Mini + GTX1070@10Gbps-TB1 (AKiTiO Thunder3 via TB3->TB2 adapter) + macOS

ReplyQuote
Posted : May 25, 2018 8:32 pm theitsage liked
charleszhao
(@charleszhao)
Active Member

have anyone tested the newest fcpx 10.4.3? have some improvement on egpu rending?

ReplyQuote
Posted : June 22, 2018 10:24 am
Antoine
(@antoine)
Trusted Member

from what I've tested anything has changed.

2017 15" MBP 3.1 MHz RP560 + AMD Vega FE LC@32Gbps-TB3 (Breakaway 350 + SF600) + macOS 10.13.4

ReplyQuote
Posted : June 22, 2018 3:14 pm
dre
 dre
(@dre)
Active Member

anything or nothing? Hopefully not nothing 🙁

ReplyQuote
Posted : June 22, 2018 3:18 pm
Jared
(@jared_busch)
Eminent Member

Well for me, since switching from a GTX1080 to a Vega 56, I've noticed that my eGPU memory and processor spikes when I'm either playing back, transcoding or exporting. Essentially I believe FCPX is actually using my eGPU for several tasks.

Obviously the eGPU isn't being fully utilized by FCP but I've noticed that my AMD card vs my Nvidia card, seems to improve my editing flow considerably!

ReplyQuote
Posted : June 22, 2018 6:29 pm theitsage liked
dre
 dre
(@dre)
Active Member

You’re on 10.4.3 and your egpu is working/helping with some of your exporting/rendering?  

ReplyQuote
Posted : June 22, 2018 6:58 pm
Jared
(@jared_busch)
Eminent Member

My apologies, I'm currently on 10.4.2.

I use iStat in my menu bar to monitor everything. So when I'm exporting, or after I've applied an effect or when playing back, I look in iStat and it shows my Vega56 spiking.

ReplyQuote
Posted : June 22, 2018 7:01 pm dre liked
Antoine
(@antoine)
Trusted Member
Posted by: dre

anything or nothing? Hopefully not nothing 🙁

sorry for the misunderstanding, nothing changed.

2017 15" MBP 3.1 MHz RP560 + AMD Vega FE LC@32Gbps-TB3 (Breakaway 350 + SF600) + macOS 10.13.4

ReplyQuote
Posted : June 23, 2018 12:21 pm
Antoine
(@antoine)
Trusted Member
Posted by: Jared

Well for me, since switching from a GTX1080 to a Vega 56, I've noticed that my eGPU memory and processor spikes when I'm either playing back, transcoding or exporting. Essentially I believe FCPX is actually using my eGPU for several tasks.

Obviously the eGPU isn't being fully utilized by FCP but I've noticed that my AMD card vs my Nvidia card, seems to improve my editing flow considerably!

well, actually FCPX in previous version than 10.4.0 was able to use eGPU for playback/rendering but after 10.3.4 (from 10.4.0) Apple decided to block rendering, so essentially only playback was enabled.
Anyway, there are some third party plug-ins that can use eGPU whatever version of FCPX in use and that's why you can see some activity on eGPU. A proper test to see if FCPX itself could benefit from eGPU is to run BruceX benchmark and compare duration on rendering/export a part from see iStat activity on eGPU.

p.s. sorry for my bad english but it's not my mother tongue language.:-)

2017 15" MBP 3.1 MHz RP560 + AMD Vega FE LC@32Gbps-TB3 (Breakaway 350 + SF600) + macOS 10.13.4

ReplyQuote
Posted : June 23, 2018 12:52 pm
eAlchemist
(@ealchemist)
Active Member

Wake me up if I'm dreaming, but there finally seems to be a way to get full FCP 10.4.3 acceleration with eGPUs!

Posted by: detunedradios

Fantastic news for FCPX users - I can confirm this enables rendering and exporting using your eGPU on the latest FCPX release (10.4.3) - confirmed with GPU usage in Activity Monitor. BruceX exported to 5K ProRes 422 in 38 seconds on my Radeon Pro 460 but in only 19 using my RX 580.

No more having to stick to 10.3!

Thread and Script:  https://egpu.io/forums/mac-setup/potentially-accelerate-all-applications-on-egpu-macos-10-13-4

I will test this with a MacBook Pro 2017 and LG Ultrafine 5k. This would be so great =)!

ReplyQuote
Posted : July 1, 2018 2:29 pm
charleszhao
(@charleszhao)
Active Member
Posted by: eAlchemist

Wake me up if I'm dreaming, but there finally seems to be a way to get full FCP 10.4.3 acceleration with eGPUs!

Posted by: detunedradios

Fantastic news for FCPX users - I can confirm this enables rendering and exporting using your eGPU on the latest FCPX release (10.4.3) - confirmed with GPU usage in Activity Monitor. BruceX exported to 5K ProRes 422 in 38 seconds on my Radeon Pro 460 but in only 19 using my RX 580.

No more having to stick to 10.3!

Thread and Script:  https://egpu.io/forums/mac-setup/potentially-accelerate-all-applications-on-egpu-macos-10-13-4

I will test this with a MacBook Pro 2017 and LG Ultrafine 5k. This would be so great =)!

i've tested the script and it does works with my fcpx 10.4.2 and rendering with egpu

ReplyQuote
Posted : July 1, 2018 9:12 pm
dre
 dre
(@dre)
Active Member

WORKS here on 104.3 🙂 Not as fast as 10.3.4 but a big improvement never the less.....

Now I need to see if it is still works if I have an external monitor attached to the eGpu too....

ReplyQuote
Posted : July 2, 2018 7:57 am
eAlchemist
(@ealchemist)
Active Member

Experience using an LG 5k on a MacBook 15" 2017 (Monitor connected to dGPU 560 via TB3):

Good News: FCPX 10.4.3 (with the script activated) is utilising the eGPU for timeline and export, when working on the LG 5k.
Bad News: Performance is worse then just using the dGPU. Very low FPS, not smooth.

This is with 4k footage. I guess the bad performance is caused by a signal overhead, getting the render data to the egpu and simultaneously transfer it back to the MacBook and then to the LG 5k.

Though for exporting, this seems to be useful.
But even here my 7970 (eGPU) has very similar results then exporting via the dGPU: Around 44 Seconds for BruceX.
Having the Radeon in a Hackintosh I get around half the time.

Timeline Performance:
FPS are measured over the iStat FPS Parameter

eGPU:
Internal: ~10FPS
LG 5k: ~6FPS
Ext. Monitor via eGPU: ~55FPS

dGPU:
~55FPS in every scenario

What the Bottleneck

I'm not sure if even a Vega64 would be a fluid solution here, as the loss in performance is so major.
The only usable solution with FCP still seems to be connecting a monitor directly to the eGPU to get usable performance.
Which excludes the internal monitor and the LG 5k.

The only other solution (for internal Monitor and TB3 Displays) would be, that FCP changes the way it utilises eGPUs, as i.e. Davinci Resolve does.
Right?

ReplyQuote
Posted : July 2, 2018 10:05 am
artik
(@artik)
Active Member
Posted by: eAlchemist
Bad News: Performance is worse then just using the dGPU. Very low FPS, not smooth.

This is with 4k footage. I guess the bad performance is caused by a signal overhead, getting the render data to the egpu and simultaneously transfer it back to the MacBook and then to the LG 5k.

 

Unfortunately I get similar slow performance on my Mac Pro 2013 (TB2) and Vega64

Mac Pro 2013, 10 core, Sonnet eGFX 550, Vega 64

ReplyQuote
Posted : July 2, 2018 12:37 pm eAlchemist liked
dre
 dre
(@dre)
Active Member

It's better than nothing I suppose 😉 I'm not getting full the VEGA64 warp speed but I'm not getting iGPU speeds either. 

A video in 10.3.4 that took 2:30 to render, takes about 10.00 in 10.4.3 with the script but using iGPU alone it's 30.00 mins. 

I'm only seeing 75% egpu usage in the resource monitor so maybe there's some more juice to be extracted from the VEGA??

ReplyQuote
Posted : July 2, 2018 12:56 pm eAlchemist liked
eAlchemist
(@ealchemist)
Active Member

Yes. Would have been to good =)..

So we find that with the script, there is still a large gap in export-speeds.
Timeline performance is unusable (with internal or TB3 Display), even on a Vega64 (but may be better if you only have iGPU).

Still, there is lots of room for effective utilisation. FCP and eGPU, please make peace again =).
Native support via a serious update seems the way to go (hope).

ReplyQuote
Posted : July 2, 2018 2:06 pm dre liked
Antoine
(@antoine)
Trusted Member

for sure this new script is very welcome but in the meantime I invested some time digging into Davinci Resolve and I think I will switch from FCPX. Resolve use GPU and eGPU more than FCPX, nearly all the fx are optimised for GPU whatever you use monitor attached to dGPU or eGPU. Of course connecting the monitor to eGPU will be a little bit better in term of performance. Also, all the third party plugins I use in FCPX are included in Resolve and they are GPU optimised.

2017 15" MBP 3.1 MHz RP560 + AMD Vega FE LC@32Gbps-TB3 (Breakaway 350 + SF600) + macOS 10.13.4

ReplyQuote
Posted : July 2, 2018 8:11 pm artik liked
Page 3 / 4 Prev Next