-
Premiere Pro CC Continues To Crash Continuously
I am running Premiere Pro CC 2014, the latest version, on a Mac Pro running the latest version of Yosemite.
PP crashes all the time. When I move a clip; when I try to quit; when move a title from the bin to the timeline. It crashes about 5 times an hour, no matter
what kind of project I’m on, using whatever kind of footage.I’ve already made sure my permissions are ok for Premiere Pro CC to write to all the appropriate folders in preferences, etc. I thought this would fix the issue, and things appeared to be marginally better for about a week.
But the problem persists.
Any ideas? I’ve loved Adobe Premiere Pro, but if this is not solved, I need to move on. My business simply demands it.
This is the first time I’ve genuinely felt that Adobe is dropping the ball.
Note to my friends at Adobe. STABILITY is the most important thing. Not features. STABILITY. I sincerely hope you are not following Apple’s lead in delivering software and at ever-increasing rate with shittier and shittier quality.
Thanks.
david
-
17 Replies
-
Carlos, Sorry to hear about your crashing troubles. A question for you…
Did you happen to migrate an older computers files over to your new MacPro using migration assistant?
I know that Apple says this is ok, but it is not a good idea in general and Yosemite seems to be more sensitive to this migration. -
No, I did no migration. Everything has been the same on my computer, except for updating to Adobe Premiere Pro CC.
-
The same thing happens to me and it’s geting quite annoying.
-
So, all of you seem to be having these issues since switching to Yosemite, what is so important to you in Yosemite that you can’t simply go back to Mavericks?
David Roth Weiss
Director/Editor/Colorist
David Weiss ProductionsDavid is a Creative COW contributing editor and a forum host of the Apple Final Cut Pro forum.
-
For one, the problem is not limited to Yosemite. As I have investigated this online, a number of Windows users have had a similar issue.
But even, for the sake of argument, if it was limited to Yosemite, the burden should not be upon us. If Premiere Pro CC 2014 is incompatible with Yosemite, the burden is on Adobe to inform us not to update.
But they have not.
Yosemite was released in Beta to developers last June and has been out since October 17. Perhaps Adobe’s engineers do not have the competence to create software that is compatible. Fair enough. But they should simply let us know before an important OS upgrade is released.
-
Hi Carlos/David:
First off you say “no matter what kind of project I’m on, using whatever kind of footage. ”
It would actually be helpful to troubleshoot the cause of this issue if you can give examples of the type of footage you’re editing — what camera was the footage shot from? Is it raw footage? What codec is the footage you’re editing? Are these mixed codec sequences? What is your GPU(s)? Do you have any AV I/O card installed in your system (AJA/BlackMagic) and is Mercury Transmit enabled, outputting the video to a reference monitor/plasma/second monitor/etc?Premier is a pro editing solution that does all things for all people so it helps to keep that in mind when asking for help.
You didn’t mention anything about your sequence settings – here’s what I’d recommend here, based on my experience, and by all means this is open to debate:
Select your sequence’s timeline. Go to Sequence>Sequence Settings Override the “Editing Mode” by selecting “Custom”. Under “Video Previews” Set the “preview file format” to “QuickTime”. For most purposes then set your Codec to ProRes 422(HQ). Hit OK, then hit OK again…After that, I’d move on to give the system some apparently much needed TLC.
typical TLC steps which normally tend to resolve the types of issues you describe:Trash premier preferences. The need to do this is not an “Adobe Issue” it is a maintenance step, not unlike changing oil in your car. you can do this manually, or download digital rebellion’s preference manager: https://www.digitalrebellion.com/prefman/
(NOTE: Any preference setting you’ve made or kb shortcut that has NOT been sync’d to your cloud acct will be gone. As of 2014 you must sync to the cloud in order to keep your shortcuts, etc)
Trash your media cache. Same explanation as above. Go to Preferences>Media to find where the location of the media cache, and instead of “cleaning” the database through the preference pane in premier, just manually trash the contents of the folder.
Take out the trash.
(NOTE: After tossing media cache you’ll simply need to wait for premier to rebuild the cache for that project next time you open it)
After doing the steps above, reboot the computer, gracefully. If you’re the type who tends to press and hold the power button of your computer to force shut it down I’d recommend shutting it down then restarting while pressing cmd+alt+P+R to clear the NV/PRAM.
If the problem persists go to Disk utility and repair disk permissions on your system drive, then reboot gracefully (as in don’t press/hold the power button)
Should problems STILL persist you may have a permissions issue with your media/project folder – open perms by going to terminal and sudo chmod -R 777 the folder containing your project/media.
-
Thanks, Robert. I’ll give it a whirl tomorrow and let you know.
-
[Carlos Mandelbaum] “But even, for the sake of argument, if it was limited to Yosemite, the burden should not be upon us. If Premiere Pro CC 2014 is incompatible with Yosemite, the burden is on Adobe to inform us not to update.
But they have not.
Yosemite was released in Beta to developers last June and has been out since October 17. Perhaps Adobe’s engineers do not have the competence to create software that is compatible. Fair enough. But they should simply let us know before an important OS upgrade is released.”
Carlos,
While I don’t disagree with you in principle, your argument above has been argued by software users for years against virtually every software manufacturer under the sun, but unfortunately it’s a losing proposition, because virtually all manufacturers long ago implemented a “fake it until you make it policy.”
So, even though you may be 100% right, that will never save your bacon at the end of the day, the only thing that will is cloning your working boot drive before installing any update, so you always have a working system to fall back on.
David Roth Weiss
Director/Editor/Colorist
David Weiss ProductionsDavid is a Creative COW contributing editor and a forum host of the Apple Final Cut Pro forum.
-
@Robert Wentz,
Ok, I followed your advice. Only way to tell if it works is as I continue on projects.
With regards to your question about “different types of footage,” perhaps I could have been more clear.
I have a new client for whom I need to create cuts from footage with a variety of frame rates and dimensions. At first, I thought that was the culprit. So
I tried the workaround of rendering my sequences, but crash problem still persisted.In addition, when I have consistent footage, let’s say from a Canon 5D, and a sequence that exactly matches the source footage, the crashing has also happened then, though not so frequently.
Assuming that the mixed frame rate/dimensions are at least a partial cause of the problem, what would you recommend? Should I transcode beforehand, and to what? and through what (in your opinion) is the most efficient method?
In any event, thanks for the advice. I’ll keep you informed.
david
-
I had updated to the latest version when it came out and
found it too unstable/unresponsive to use for production work.I have since reverted to 2014.1
It seems like every other adobe release has issues.
Reply to this Discussion! Login or Sign Up