-
OT: Apple not supporting nVidia graphics in OS X Mojave
-
25 Replies
-
It is really unfortunate if that is absolutely true, and there is no way that in the future an Nvidia card could ever be used with the Mac Pro.
However, seeing the performance on the new Radeon cards with 8K footage and grading, and their apparent matched performance to an nvidia 2080, it might beg the question – so what? If video editors can achieve the same performance with a Radeon card in a Mac, are they really bothered if an Nvidia card won’t work in the new Mac Pro? It’s a big if, and also dependent on seeing how the new drivers for R3D files work with Nvidia and AMD, but it could very well be meaningless if the new Mac Pro is hugely quick with an AMD card inside.
Co-owner at Pollen Studio
http://www.pollenstudio.co.uk -
[Tom Sefton] “it might beg the question – so what?”
The answer if that it locks into an even tighter, proprietary ecosystem – with few, if any, options for upgrades. You simply chuck what you bought and then buy new again. Good for Apple, pretty lousy for the user and the environment.
– Oliver
Oliver Peters – oliverpeters.com
-
I understand that. If the Mac Pro in 2019 is going to be upgradeable/modular, there must be a way to modify parts such as the GPU, RAM, processor, storage etc. But how many people on Mac OS have already bought an Nvidia 2080 or 1080? Which machines are they working stable inside?
Apple and Nvidia have worked together in the past, and may well again in the future. But being locked to GPUs that aren’t Nvidia isn’t really a proprietary ecosystem, it just discounts using one manufacturers products….
Co-owner at Pollen Studio
http://www.pollenstudio.co.uk -
I’m struggling through this right now. The drivers are there from Nvidia. Just can’t use them with Mojave. On any exports longer than 5 or 6 minutes Compressor shuts down. Media Encoder shuts down. FCPX is hurt by this. Premiere is hurt by this. Fortunately, I have Windows workstations as well (with Nvidia cards). Not sure what I’m going to do. This is just stupid.
-
[Tom Sefton] “But being locked to GPUs that aren’t Nvidia isn’t really a proprietary ecosystem”
Yes, in a sense you are. If they take the route that they took with the 2013 Mac Pro, those GPUs use AMD chips, but are not the same as other Radeon/AMD products. Even AMD says we sell Apple the chips, but the configuration and drivers are theirs. So, while not truly proprietary, it might as well be. You can stick an Nvidia or Radeon card in a Sonnet eGPU, but it still has to play nice with macOS.
– Oliver
Oliver Peters – oliverpeters.com
-
[Paul Neumann] “On any exports longer than 5 or 6 minutes Compressor shuts down. Media Encoder shuts down. FCPX is hurt by this. Premiere is hurt by this.”
I have a mid-2014 Retina MBP – the last run with an Nvidia GeForce card. I’m on Mojave and am using the default OS drivers, not the Nvidia-supplied drivers. Renders/exports are just fine – Adobe, Apple, Avid, BMD. Make sure you have set all the settings to OpenCL, Metal or software. Definitely not CUDA. If that doesn’t help, revert the OS back to High Sierra or earlier.
– Oliver
Oliver Peters – oliverpeters.com
-
“being locked to GPUs that aren’t Nvidia isn’t really a proprietary ecosystem, it just discounts using one manufacturers products….”
When it involves the dominant GPU manufacturer that holds nearly 70% market share and who is known as the leader in GPU innovation it becomes a larger issue.
From U.S. News and World Report:
“In the past two years, Advanced Micro Devices (AMD) market share has dropped from 25.1 percent to 13.9 percent. Over the same period, Intel Corp. (INTC) market share has fallen from 17.8 percent to just 9.6 percent.”
Tallmanproductions.net | Windows 10 Pro | i7-5820k CPU | 64 gigs RAM | NvidiaGeForceGTX970 | Blackmagic Decklink 4k Mini Monitor |
Adobe CC 2019 13.0 | Renders/cache: Samsung SSD 950 Pro x2 in Raid 0 | Media: Samsung SSD 960 PRO PCIe NVMe M.2 2280 x 2 | Media: OWC Thunderbay 4 x 2 Raid 0 mirrored with Resilio -
Yeah that’s what I’m running on this particular machine (Late 2013 27″/i7). It seems to get bogged down with any data rates higher than ProRes LT. Everything off an SSD Raid and separate SSD cache. It’s hit and miss, but lately much more miss. The exports are the problem. No problems with playback, transcodes or making proxies. After Effects seems fine, but those are much shorter exports of course. Metal is the most reliable, but only slightly so.
I’ve gone round round on this, and when you keep coming back to, “Man, I never should’ve upgraded…” You lose a little faith, ya know? (please hold any comments about upgrading, I get it all too well) especially when everything was running great on the previous version. This box cost close to $3k and to have it crippled this way is disheartening.
It’s easy enough to build projects on it and move them over to a Windows workstation for export (aside from FCPX projects obviously), but that’s not really the point.
-
[Paul Neumann] “The exports are the problem. No problems with playback, transcodes or making proxies”
A tough one. How about plug-ins? Maybe start a “divide & conquer” approach. Export in-out smaller sections of your sequence until you (hopefully) hit a section that fails. Then see if you can narrow it down to a clip or a plug-in. If you have any Magic Bullet plug-ins, I would disable/remove those first. Also copy your sequence and remove all attributes. Then export and see if it’s successful.
– Oliver
Oliver Peters – oliverpeters.com
-
Nah, I can throw 15 minute clip into a timeline set up for just that format and it will crash before it finishes. Thought for a while it was Lumetri causing the problem, but I can get Compressor to do the same thing from FCPX.
And these are 1080 ProRes clips in ProRes timelines like I said. Not even 4K. But they output just fine on the other machines.
Reply to this Discussion! Login or Sign Up