Premiere Pro CC no longer compatible with New Mac Pro running 10.9.3

[Reed Brown]

I’ve tried as suggested: trashed prefs, created new “custom” sequence, set preview files to QT animation, copied clips into new sequence, PP deletes all old render files and I re-render in in/out sections… and program still crashes, although maybe, maybe just a bit less.

I tried this workflow with a other preview file codec settings (ProRes422, ProRes422LT) but the problem remains the same.

Will keep going with editing over next few days and see how it goes. If problem persists (anyone willing to take bets?), I might go up to 10.9.4 or .5. I noticed that .5 has a thunderbolt update. Another link in the chain that maybe helps fix things?

Like many of you, I wish someone from any of the companies involved would at acknowledge this problem and give an update on their findings/solution.

Reed Brown
INNOVATION EDIT

[Alexander Goff]

Hi Reed

How have you found things working out with 10.9.5? I just updated from 10.9.3 which was having irregular problems when rendering raw S-Log footage, and found this thread which seemed to be touching on some similar issues.

This is just the latest in a long line of issues with the new Mac Pro which I initially thought were down to driver clashes and software glitches – reading this thread has me wondering whether there is a fundamental issue with certain GPUs.

As an aside, in my limited testing so far I have found that when playback/render glitches occur whilst playing back in my timeline, I can switch from GPU rendering to Software Only (throwing out the old renders), and then back again and this seems to have me up and running without issues. But I have yet to test this theory to destruction.

Alexander Goff

[Jimmy Brunger]

Hi all,

Glad I spotted this…just about to order an 8-core MacPro and we rely very heavily on PPro CC2014 (latest .1 release)

Has this issue been resolved?

Also – if anyone has any thoughts or experience on scratch drive set up on the nMP I’d love to hear….I currently have media running on a big RAID via 10GbE and then internal SSD for system, then another internal SSD for scratch…As new MP only supports one internal drive, I’m curious as to whether the new ‘super fast PCIe SSD’ is fast enough to do both?

Thanks,
James

——————————-
Adobe CC 2014
MacPro 3,1 8-core 3.2GHz / 32GB RAM / NVidia Quadro 4000 / OSX 10.8.7
Decklink Extreme+ 3D / 3TB RAID-0 local / 6TB XServe + United Digital RAID on 10GbE

[Brian Cooney]

Well we have 2 new 12 cores and 4 8 cores and the issue seems to be related to the AMD video cards. The only way I’ve found to have some sort of stable performance is to switch from openCL to software rendering. this is a bummer because obviously it’s like owning a BMW S3 and only driving it at 40 miles per hour.

Head of Post Production, Coca-Cola Studios Atlanta, GA. Telly Award Winning Editor and Motion Gfx Artist.

[Jimmy Brunger]

Thanks for the heads up Brian.

Definitely not an option to switch off GPU acceleration!…main reason going for the upgrade! Do you know what the last stable version of mavericks is that will run PPro CC2014?

Also, as a side – i wonder if you could share any thoughts you have on the performance difference in PPro/other adobe video apps between the new 8 & 12core? Trying to decide if worth the extra £££

Thanks,
James

——————————-
Adobe CC 2014
MacPro 3,1 8-core 3.2GHz / 32GB RAM / NVidia Quadro 4000 / OSX 10.8.7
Decklink Extreme+ 3D / 3TB RAID-0 local / 6TB XServe + United Digital RAID on 10GbE

[Reed Brown]

Here’s the latest update: I was able to get Apple to reinstall 10.9.3 and yes, the system is more stable now than running 10.9.4, with fewer freeze and crashes. I’m now rendering everything in ProRes422 which seems to help stabilize things. However, oddly, I’m now getting the video glitches everyone else was seeing, but mostly in render files. I can usually get clean renders by adjusting the opacity on the offending clip(s), resetting back to 100%, re-render, and the new render file is usually OK.

Still a few odd crashes here and there, but to summarize, going back to 10.9.3 has 85% done the trick. I’m very reluctant to go to 10.9.4 again until this issue is finally resolved.

I’m also going to be starting a project using only ProRes422 and so I’ll see (and report back) if that codec is more stable than the couple I’ve been using so far.

Meantime, anyone else made discoveries on this MacPro issue?

Thanks.

Reed Brown
INNOVATION EDIT

[Alexander Goff]

We’ve now gone to 10.9.5 and everything’s running pretty well (admittedly this is short form stuff, but we’re cutting XAVC 2K log footage with LUTs so a reasonable demand on the system). Might be worth atry for those still struggling with 10.9.4

[Reed Brown]

Thanks for the update. As you have the time for updates, that would be terrific.

By the way, are you running two monitors on your system? For me, using 10.9.4 with two monitors was more troublesome than one so I’m wondering if you are using two monitors without problems. Back on 10.9.3, two monitors seem to be stable again.

Thanks.

Reed Brown
INNOVATION EDIT

[Alexander Goff]

Using Tiger shared storage and no Yosemite drivers are available for that yet. I’ll probably wait a version or two before jumping into Yosemite, it’s a significant overhaul.

[Alexander Goff]

Yes, two monitors plus a broadcast monitor via BM Decklink 4K Extreme. All going swimmingly at the moment.