10.9.3 newMacPro GPU broken

[Ben Silberfarb]

Hi Kevin,

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.

[Walter Biscardi]

[Esben Holm] ” Both Aple, AMD and Adobe has a responsibility here. Get your smartest heads together and bring us down in one piece.
“

This is all on Apple. They develop and release the OS regardless of anyone else’s needs. Main reason I moved away from an all Apple ecosystem.

Walter Biscardi, Jr.
Editor, Colorist, Director, Writer, Consultant, Author, Chef.
HD Post and Production
Biscardi Creative Media

Craft and Career Advice & Training from real Working Creative Professionals

Blog Twitter Facebook

[Alain Maiki]

Not to mention that not even exporting premiere cc timeline to Davinci works well…U can do the xml transfer perfectly, but then davinci crashes while color grading…

It’s a very frustrating situation for all of us MAC PRO Owners

[Robin Erard]

Hello,

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.

Robin

réalisateur, scénariste, monteur, étalonneur
http://www.robinerard.ch

[Danny Phillips]

Hi Kevin,

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..!

Specs –
Mac Model: MacPro 6,1
Memory: 16 GB
GPU: D700
Premiere Pro version: CC 7.2.2
Storage – local vs network: Areca 8052TB2
3rd party IO?: BMD Monitor Mini
Dual monitor GPU?: Yes
3rd party plug-ins loaded?: Red Giant
Type of footage?: ProRes 422HQ

Where a-bouts would I find the crash log?

Cheers,
danny Phillips
Melbourne, Aus.

[Slobodan Milivojevic]

Hi guys,

I can’t describe how much I feel like a donkey now.

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!

Director/Editor/Postproduction manager
@ Talking Pictures productions Bahrain
http://www.vimeo.com/channels/bobansky

[David Brumbley]

Also make sure “render at Maximum Depth” and “Use Maximum Render Quality” are unchecked.

This made premiere work for me without error.

Hope it helps you too

[Danny Phillips]

Hi David,

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

[David Brumbley]

Hi 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.

My system seems to be stable now. Slow, but stable, without glitches.

[Christoph Heimer]

[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.