on May 22, 2014 at 2:58:41 pmLast Edited By EricBowen on May 22, 2014 at 3:01:01 pm

Open CL is standardized. Either Nvidia or ATI can update the standards used with their drivers. It is not specific to either AMD or Nvidia. That means Nvidia's driver can update the Open CL used by OSX the same as AMD's.

on May 22, 2014 at 11:20:44 pmLast Edited By EricBowen on May 22, 2014 at 11:23:28 pm

Kevin someone brought up a point I didn't think about before in the Red Forums. Does the Open CL in Premiere reference the Cuda Player at all in Adobe? If so that may be why those who have tried the OSX Cuda update are able to export via GPU acceleration on.

In export settings if "render at Maximum Depth" and "Use Maximum Render Quality" is off. Everything exports fine for me. If they are on the export freezes. I haven't tried Media Encoder, but I'll give it a shot.

Attached is a screen shot typical of the type of crash you get with AMD FirePro cards on the new Mac Pro with 10.9.3. Having spent many hours on the phone with both Apple and Adobe I can confirm that it is an acknowledge bug that will only be fixable upon the next update by Apple and/or Adobe. A lot of editors are in a world of hurt right now.

Hey guys, had the same problem exporting a ProRes 422 HQ . The file length was 75 minutes. I started happening after the first 6 minutes. The settings for the MacPro are all the same, and I bought the computer when it first came out.

If you read the rest of the thread, AMD says its nothing to do with the Graphics Cards! It has to do with Mavericks and Premiere's OPEN CL 2.0 update.

Just installed 10.9.4 beta = will respond when installed and we render out again.

There appears to be rumors that the beta release 10.9.4 will solve the Open CL incapabilities that are causing multiple crashes with Premiere and the New Mac Pro. Unfortunately THIS IS NOT THE CASE. I have loaded 10.9.4 and sadly the same problems/crashes persist.

We rendered out again, mind you 6- 7 hours later without maximum bit depth and without the maximum render quality ticked which don't really do much but give you a better color space, I still got errors.

The funny thing is that if you render out , say in my case 10 minutes of the 75, you get no errors. ( Did this to test different scenarios, toggling on off max render quality and bit depth to see if those where giving me errors, without having to spend the full render time )

So it has to do with rendering a certain file size or length. In my case I went from a 2k timeline 2:1 Aspect to codec ProRes 422 HQ 1920 x 1080 while using the mac pro specs, and the newest AMD Firepro drivers with the newest OS iteration. Tried both 10.9.3 and 10.9.4 beta. I have yet to time machine back to older Mavericks , but why bother.

Adobe needs to look into this. Apple needs to look into this. AMD , wasnt expecting much from the card anyways, but I don't think its the card, but rather compatibility.

I am transferring my project to avid media composer. Should have used this to begin with.

I am aware of the issues with Resolve and believe they are related. It seems that Apple has effectively made their flagship computer unusable for video production (at least for those not using FCP). I am quite concerned that Adobe is on the cusp of loosing all they gained from those who switch from FCP7. This is quite serious for pro video production. I hope that the Adobe engineers at the current Apple WWDC are all over this.

I'm not a Adobe User, I'm colorist on DaVinci. This problem existed on 10.9.2. Apple changed my two D700 one month ago... but today (and I'm still on 10.9.2)... the problem occurred again (color lines on GUI and on Render). Then maybe it's really an OpenCL problem.

I don't currently have a crash log and I turned off GPU rendering. Since turning it off, the machine no longer crashes but it runs slow for exports and the audio playback through the IOXT cuts in and out. Very disappointed in apple right now.

Far up in the north of Norway I'm in the same shit. Bought this fantastic machine with the ultimate specs to finish a major 4k project with multiple fileformats, and what happens? It works even worse than my 3 year old PC.

Aple support in Norway didn't know shit and I found out about the problems with the OS X update on the net myself. I have a customer, I have a deadline and I have a mortgage. AND I have spent all my money on this f.... machine.

Went back to 10.9.2 by Time Machine and I am now able to work, but it is still not up to hardcore 4k and grading as Aple proclaim. Both Aple, AMD and Adobe has a responsibility here. Get your smartest heads together and bring us down in one piece.

I've got these issues as well - Very frustrating... Premiere keeps locking up and/or "Serious Error" shutdown along with the digital pink/green visual tearing/distortion. have not exported yet, only in playback so far. Third the way through 10 episode series for broadcast... Hoping help is on the way..!

After decades working on PC, I've decided to try MAC, so recently I bought a new Mac Pro 6 core, with D500.

FCP 7 is out of question now (its old, slow and outdated), FCP X is s**t), so I decided to go with Adobe CC/Resolve combination.

BUT

After few days, I've realized that 16 GB is not enough, and that MAC OS is much worse in Memory management than Windows 7/8, so I have to order expensive 32 Gb in order to avoid OUT OF MEMORY errors (haven't seen in in Windows since 2000!!!) I was trying to use MULTIPROCESSING on Aftereffects, and it turn out to be slower in render than my 3 years old MSI notebook.

After unpacking machine, I've updated to 10.9.3, and since first project I have big problems with Premiere and Resolve.

I am getting weird lines during playback of RED or SONY f5 files, Premiere is hanging on GPU exports, Resolve is damn slow and just quits randomly....

Ist this THE MAC I was listening about for years....All these people nagging how Mac is cool, superior, this , that....???? OS that breaks GPU support for Adobe and Resolve??? WTF????

I feel like throwing this ugly trashcan trough the window, really....^$^^#^#!!##@@#

I am seriously thinking to install WIN 8 on trashcan... I guess It will work much better!

That might be an idea for export but I'm having issues in editorial. I've disengaged 'GPU' mercury playback in favour of 'software' and that seems to have helped quite a bit. I wonder, is it just these D-series GPUs in the new Mac Pro that are causing problems? ...i.e. just driver support in 10.9.3?
Cheers,
danny

From what I've read it's the D500's and D700's. It seems to have started after people upgraded to 10.9.3, including my self.

I've turned off preference syncing in premiere (That crashed my system as soon as I turned it on).
repaired permissions
Threw away my premiere preferences
Cleared my media cache in premiere preference pain.
Threw away ALL render files.
Turned off GPU Mercury play back.
and I have a 1080 timeline playing back at half res.
I work with R3D's and 5d footage.

[Esben Holm]"Went back to 10.9.2 by Time Machine and I am now able to work, but it is still not up to hardcore 4k and grading as Aple proclaim. Both Aple, AMD and Adobe has a responsibility here. Get your smartest heads together and bring us down in one piece."

I'm having the same issues... It's incredible, I feel like they designed this monster machine, put it out in the wild and now abandoned it.
I have barely been able to use the GPU for anything, since almost no software is able to properly tap those cards.

The latest frustrating experience was regarding FCPx: I purchased a license of neat video for fcp x (even thoug I already had one for after effects, but I thought it would properly utilize the GPUs in fcp).
Turns out - yes it does use the gpus, but is then slower than without them, and overall neat video in fcp x is not able to use even halve of the CPU horsepower in this machine. CPUs are at 25% and the whole cleaning process took like three times as long as in after effects.

Frustrating! Get on this apple, and adobe, please fix this glitch. I'll open up a ticket now.

I am having many issues with the newMacPro and Premiere/AE. Currently I can cause it to crash just by playing back a rendered file. Tried to change my render location, delete render files before I render etc. Does not seem to help. I have not used the Nvidia update as I am using the D700. I have brought my Mac to Apple and am currently waiting on a new graphics card as they have found this one to be faulty. I have had many other strange issues relating to crashes and glitches that have not been solved, could be related to the card or something else.

I am suffering similar problems with my Mac Pro (D700) since updating to 10.9.3. Adobe Support is a nightmare and impossible to find someone to discuss this issue with! Can you let me know if you have found any solutions?

The problems are:-

1. Premiere Pro (PP) runs very slowly and freezes
2. When rendering it freezes
3. Exporting to Media Encoder causes it to freeze as well
4. Extra frames appear randomly within the sequences - these are frames from other sequences that appear.
5. When Force Quit is used for PP the whole machine freezes, the mouse arrow still moves but will not activate any functions. To shut down the computer I have to pull out the plug.
6. On Restart I get a grey screen. Nothing happens
7. I have to Restart using cmd R and the go for the Restart option from there.
8. I have used Disk Utility and done Repair Permissions and Repair Disk but no faults found.
9. On one Restart on Saturday the internal speakers vanished and none of the USB ports were active. Thunderbolt was active.
10. Auto save on PP also did not work - it told me it was auto saving but it never actually did - lost 3 hours editing when the machine crashed.
Kind regards
Simon

After lengthy discussions with Apple Senior Support they admit there is a problem and they are trying to resolve it. Hopefully in 10.9.4.
In the last year Apple have become appalling, we have had major issues with our Mac OS X server as well and nothing works properly anymore. After ten years loyalty to Apple I am seriously thinking of moving to PC. Anyone want a new full spec Mac Pro?

Sorry for the late reply... I have found that just turning of Mercury GPU playback in favour of software has helped, mostly clearing up my issues. However, it would be lovely to get back openCL boost from these dual D700 cards in Adobe suite.

I didn't find that I needed to wipe prefs or trash anything, just turned off Mercury.

So this is still not fixed in Yosemite or answered else. I can say it's open cl /amd /Mac os as the same machine in boot camp doesn't have the issue with Resolve. This sucks. Glad I didn't spend $10k on NMP
Mac Pro 2012 12 core
4 r9 280x 6g in Cubix

Still having this issue on Mavericks on the 2013 Mac Pro with D700's, software fully up to date. Also having a similar issue on Yosemite on a 2011 Macbook Pro, software also up to date. Feature updates are great, but I literally can't render out footage in one, or get timeline GPU playback on the other. Any help Adobe?