[SCRIPT] Accelerate All Applications On eGPU - macOS 10.13.4+  

Page 3 / 3 Prev
 

nanoBit
(@nanobit)
Trusted Member
Joined:7 months  ago
Posts: 52
July 22, 2018 11:37 am  

Maybe a little but off-topic but has anyone tested the script with FCP? I did...it worked and FCP 10.4.3 used my GTX 1080 on export. But somehow it took exactly as long as exporting without the eGPU and FCP used it just at about 40%. Just wanted to know if anyone has the same issue or an idea how to solve this?

Setup: MacBook Pro 2018 15" 2.6GHz Radeon Pro 560X on macOS 10.14 & Windows 10 (Bootcamp); Sonnet eGFX Breakaway Box 350 with a Zotac GTX1080 AMP! Edition


ReplyQuote
damonhayhow
(@damonhayhow)
Eminent Member
Joined:1 year  ago
Posts: 21
July 22, 2018 1:22 pm  

Yes, I did set for all apps. 

Truly, its a fantastic script. And it certainly shows the fallacy that developers have to pour considerable resources into redeveloping their apps to work with eGPU's.  😉 Especially FCPX. 

I'll update in my signature with my setup. In this case, however, as I said, I have a 2016 13" Touchbar MBP which works great in the same setup. I put my new 15" 2018 MBP into the exact same setup and it failed twice in the exact same way.

It is REALLY bizarre behaviour. But for right now, Im happy with everything to use the egpu on High Sierra. Im not game to try Mojave a third time. 😉

2018 15" Macbook Pro I7 2.6 Ghz / 16Gb / 512 Gb / 560X. 2x LG Ultrafine 4K displays. Razer Core V2 eGPU, Radeon RX580, Sunnix UPD2018 Displayport adapter.


ReplyQuote
Eightarmedpet
(@eightarmedpet)
Prominent Member
Joined:2 years  ago
Posts: 802
July 22, 2018 4:09 pm  
Posted by: damonhayhow

Yes, I did set for all apps. 

Truly, its a fantastic script. And it certainly shows the fallacy that developers have to pour considerable resources into redeveloping their apps to work with eGPU's.  😉 Especially FCPX. 

I'll update in my signature with my setup. In this case, however, as I said, I have a 2016 13" Touchbar MBP which works great in the same setup. I put my new 15" 2018 MBP into the exact same setup and it failed twice in the exact same way.

It is REALLY bizarre behaviour. But for right now, Im happy with everything to use the egpu on High Sierra. Im not game to try Mojave a third time. 😉

I think we need pics of your set up... sounds impressive...

2017 13" MacBook Pro Touchbar + GTX1060@32Gbps-TB3 (AKiTiO Thunder3) + Win10
2017 13" MacBook Pro Touch Bar + GTX1070@32Gbps-TB3 (Sonnet Breakaway Box) + Win10
---
LG 5K Ultrafine flickering issue fix


ReplyQuote
042e
 042e
(@042e)
New Member
Joined:1 month  ago
Posts: 2
July 26, 2018 1:23 pm  

I am finally able to see some results now using the Blackmagic eGPU together with the fit-headless GS adapter, but I do have to use mirroring. Can anyone expand a bit on the setup of using a headless adapter without mirroring?

Some applications will work/benefit from having a headless adapter connected to the eGPU without mirroring - especially OpenCL applications.


ReplyQuote
mac_editor
(@mac_editor)
Noble Member Moderator
Joined:1 year  ago
Posts: 1153
July 26, 2018 4:12 pm  

@042e That is with reference to some games such as F1 2016 which won't launch on internal display if headless adapter is at least not connected. A special case I suppose.

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


ReplyQuote
042e
 042e
(@042e)
New Member
Joined:1 month  ago
Posts: 2
July 26, 2018 4:28 pm  

@mac_editor Ah I see, thank you for the clarification!


mac_editor liked
ReplyQuote
iaomw
(@iaomw)
Active Member
Joined:1 year  ago
Posts: 16
July 26, 2018 7:05 pm  

Thanks, that's so great. But looks like the WebGL content is Chrome\Safari is not using eGPU.

Do I need to do something special for Chrome and Safari?


ReplyQuote
limozeen
(@limozeen)
Active Member
Joined:5 months  ago
Posts: 11
July 30, 2018 8:16 pm  

I'm not sure if this is script-related, as I have surely installed a couple of programs since installing this script four or five days ago, but FCPX has today become unusable ---- only during rendering.

My new MBP, running 10.13.6, all-but-hangs, processing at a snails pace though without extensive resource utilization. Console reveals the following fault, which consistently and repeatedly appears only when FCPX is rendering video. Everything goes back to normal the instant rendering is stopped.

IOAccelFenceMachine::fence_timeout(IOTimerEventSource *): AMDRadeonAccelerator prodding blockFenceInterrupt

That error repeats every three or four seconds, infinitely. Any idea what's going on and if it's related to the script?

Does the script make any changes that are persistent even after using the script to reset eGPU preferences for all applications? How would I uninstall it completely if I want to confirm that the script isn't the issue here?

Unexpectedly, I can't find much else on the internet about that error. Help, please! 🙂 Thanks!

ps - When everything is working, your script rocks!


ReplyQuote
mac_editor
(@mac_editor)
Noble Member Moderator
Joined:1 year  ago
Posts: 1153
July 30, 2018 8:19 pm  

@limozeen Ideally resetting eGPU preferences should revert everything back to how it was before setting any preference. For good measure, reset the specific application as well.

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


ReplyQuote
limozeen
(@limozeen)
Active Member
Joined:5 months  ago
Posts: 11
July 30, 2018 8:22 pm  

Done and done. No dice.

Tried restarting, as well as various configurations of set-eGPU, eGPU plugged in vs. not, dummy head in vs. not, etc.

I'll explore other possible software avenues.


ReplyQuote
mac_editor
(@mac_editor)
Noble Member Moderator
Joined:1 year  ago
Posts: 1153
July 30, 2018 8:25 pm  

@limozeen For FCP, check com.apple.FinalCut.plist file and see if it has GPUSelectionPolicy key. If it doesn't, then the script has reset the preference successfully. If it does, delete it manually and retry. Another way might be to remove that plist file (keep it somewhere else and see what happens).

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


ReplyQuote
mac_editor
(@mac_editor)
Noble Member Moderator
Joined:1 year  ago
Posts: 1153
July 30, 2018 8:38 pm  

Apple has removed the SafeEjectGPU command line options to set/reset eGPU preferences as of macOS Mojave Beta 5. Either it is not possible to use CLI to set preferences in macOS Mojave or it has simply been moved (latter likely I guess). In any case, this setting is now available in UI as of macOS Mojave Beta 5. I haven't tested whether the older defaults technique works or not.

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


theitsage liked
ReplyQuote
limozeen
(@limozeen)
Active Member
Joined:5 months  ago
Posts: 11
July 31, 2018 8:28 am  

Hey mac_editor! Thank you so much for your rapid responses earlier!

As it happens - and as you suspected - it had nothing to do with your script. Bizarrely, the root cause of it all were a couple of older and incompatible FCPX plugins. It's incredible when seemingly insignificant problems end up completely putting the brakes on the usability of even the most powerful computer.

Glad I got it fixed, anyway.

If anyone else has this issue in the future: You may be able to isolate the problem to FCPX plugins or other non-stock elements by launching FCPX from another user account. (The effectiveness of this will depend on whether plugins are shared by all users or not. There is no "safe mode" for FCPX.).

This website along with Apple's FCPX troubleshooting page have good information on what to try once you have isolated the issue to FCPX.  What worked for me was  resetting my FCPX preferences, then backing up your plugins folders (there are three, use Google), and finally renaming/nuking those folders. Restart and see if you are good to go. If yes, rebuild your plugin library one plugin at a time. checking for the fault after each plugin install. It's annoying but it works.

Peace.


mac_editor liked
ReplyQuote
dre
 dre
(@dre)
Active Member
Joined:5 months  ago
Posts: 19
August 6, 2018 11:03 am  

Hey mac_editor, I didn't remove the script before installing the public beta of Mojave, any tips on how to remove the script (now that egpu's are supported with FCPX in mojave?). I looked but couldn't see idiot proof instructions 😉 Thanks x


ReplyQuote
mac_editor
(@mac_editor)
Noble Member Moderator
Joined:1 year  ago
Posts: 1153
August 6, 2018 11:06 am  

@dre Do you wish to completely remove it from the system? If so, just reset all apps (if you had used the script to set some), then remove it from /usr/local/bin.

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


ReplyQuote
dre
 dre
(@dre)
Active Member
Joined:5 months  ago
Posts: 19
August 6, 2018 11:10 am  
Posted by: mac_editor

@dre Do you wish to completely remove it from the system? If so, just reset all apps (if you had used the script to set some), then remove it from /usr/local/bin.

Yes, remove completely, I was only using if for FCPX and now there's official support in mojave it's not required on my machine.


ReplyQuote
mac_editor
(@mac_editor)
Noble Member Moderator
Joined:1 year  ago
Posts: 1153
August 6, 2018 11:16 am  

@dre cool, so just reset preference for Final Cut Pro with the script and remove it as above. That should be sufficient. 👍

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


ReplyQuote
Zaylondon
(@zaylondon)
New Member
Joined:3 days  ago
Posts: 1
August 17, 2018 12:03 am  

Everyone having problems with the apple black magic egpu not working efficiently. I’ve got it working on a 2014 mac thunderbolt 2 ports & working for any software. There has DEFINATELY been a huge difference with this device regarding my graphics. Working with 1080p videos and big improvements on FPS. Mac was throttled at 22 FPS and struggling. I have t done a reading as of yet but I can see from experience it’s got to be way above 50fps easily...


ReplyQuote
Page 3 / 3 Prev