[Reed Brown]

Thanks for the links. Will give ’em a try. I found the “round off” in the AE template (amazing what you find when you open your eyes!), and will attempt to insert the comma code into the script. Thanks again.

[Reed Brown]

Hi Liran,
Thanks very much for your reply & instructions. Oddly, I wasn’t able to locate anywhere the “Convert to Bezier Path” on the layer you iindicated and I’m on A/E 14.2 but who knows… Everything works ’till it doesn’t. Anyway, I created the path in the pen tool in a shape, copied the path and all worked great. Copy/pasted groups of keyframes (didn’t know you could copy start frame right on top of end frame for totally smooth movement), did a bit more work on the smaller orbit, changed colors, added text, arrows–and all worked great. Image below is the electron captured between dissolving from the inner orbit to the outer circle; orbits in sync with each other.
Again, thanks so much!
Reed

[Reed Brown]

Wow… not that anyone is still looking at this thread (well, YOU are…), but I’ve been using FCP 7.0.3 on a 2013 MacPro 3.5 GHz 6-Core on OS 10.10.5 with an AMD FirePro D500 and two wide screen monitors AND, drum-role please, had the same issue with the very dark source/record images but after changing System Settings Gamma Correction to Approximate, all screens now look perfect! And shifting brightness going from pause to play as sometimes happened as stopped as well. THANKS for the easy fix!

Also running PPCC on the system and since several Adobe updates a couple years back, no longer have freezes or crashes I had back in 2013. Smooth sailing for at least two and half years. All at peace in the world of non-linear editing. Yeah!

[Reed Brown]

I created a separate boot drive for my new late 2013 MacPro using 10.9.5 and have been successfully running PP CC on that for 3-4 weeks now. 98% stable. FINALLY!!! After this next job finishes, I’ll probably upgrade the internal HD to 10.9.5 and hopefully be done with the freeze, glitch, crash issue. My recommendation–try 10.9.5 on a different boot drive and see how PP runs.

Feedback welcome!

[Reed Brown]

Great to hear. I’ll probably make a disk image of 10.9.3 then, in a few weeks after this project is done, try going 10.9.5. May check in with you to see if things still running smoothly.

All others, please continue to chime in on your experiences! Thanks.

Reed Brown
INNOVATION EDIT

[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

[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

[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

[Reed Brown]

First day of editing back on 10.3.9 and (drum roll please)…. the crashing still persists (cymbal crash now). PP CC seemed to play better for an hour or so, then the crashes started occurring. And for the first time, I also started seeing those pesky line break-ups, in addition to the normal freeze and crash events. I am truly beside myself – as is my client. We are stuck on PP CC for this job, but if this problem isn’t fixed and soon, I will go to FCP X or Avid as soon as possible (or continue using FCP 7 until it’s last dying breath on my old MacPro).

(By the way, my system checked out perfectly at Genius Bar — no bad graphics card VRAM or computer cooling issues — as suspected.)

Ken, what are your system specs? Most importantly, which AMD FirePro series do you use? Did the crash issue go away upon moving from 10.9.4 to 10.9.5? There has to be some difference(s) between your MacPro running smoothly with PP CC and those of us having problems.

As it seems Adobe/ Apple/ AMD are not perusing this tech problem it will be helpful for all of us to use our detective skills to figure out a solution. Obviously, some editors with PP CC on new Mac Pro are NOT having this issue. Why why why? Detective hats on please!

[Reed Brown]

I’ve gone back to OS 10.9.3 and am just starting to put the computer through it’s PP CC editing paces today…will keep you posted if this improves the situation… Hope this works!

Reed Brown
INNOVATION EDIT