-
Premier Pro CS6 constantly crashing
-
Thanks for the reply Tim. I was / am using version 6.02 of Premier. A typo in the first post I made. Still today the application crashes virtually as soon as I try to do anything with the project-file I’m working with. I also tried, as instructed by the Swedish Adobe Support, to create a new project and there reimport all my footage / sequences. Same issue again. I also tried throwing preference files, clearing plugin and application caches. Same problem. Last but not least I repaired all drives to my system with no issues found as well as repaired permissions to my system drive. That sadly didn’t solve my issue either.
I am the admin user and I tried to create a new user prior to reinstalling the whole suite this morning. The new user experienced similar crashes. I tried uninstalling all plugins (including the Kona 3 stuff) prior to reinstalling. Same issues. The crashes are very sporadic and unpredictable – i.e. it crashed when I navigated the timeline, edited parameter in some footage and so forth. I would call the crashes completely random.
The footage I’m using ranges from H264-files to MFX (Canon C300) as well as some QuickTime ProRes. I figured going “all native” was the way to do things in Premier hence I’m going that route. I also had a few MP3 and AAC audio-files as well as a WAV / AIFF or two. On top of that there are a series of stills (JPEG + PSD primarily). All should be RGB color space and not insane sizes.
System setup is the following:
– MacPro 2008 8×2.8Ghz
– 16GB of RAM
– 1×512 GB + 1×256 GB SSD (System + Project Drive) as well as 2x2TB HDD’s (Project Archive, Old System 10.6 partion as well as Time Machine partion).
– Radeon 4870 GPU
– AJA Kona 3 VPU + latest driver (for card and Adobe Suite)
– External eSATA RAID (HighPoint card, not 100% sure about model ID)
– OSX 10.8.2 + all updates available
– Adobe Production Premium CS 6 + all updates available
– Other software include Final Cut Pro 7, Final Cut Pro X, Compressor, Episode 6, Mocha Pro 3 – all with their latest versionsNote that the system is a completely clean install as well. Need more info than the above?
-
I recently had the same problem with Premiere Pro and I traced the problem to some high resolution stills that I was working with in a certain project. I have been working on a new project without any stills and the software has worked perfectly.
-
A theory I have is as you say here – I might have one or more corrupt / broken files that PrPro is trying to interoperate or what not. I guess that is a risk of working all native also (given there should be a fall-back that prevents the editing environment from loading “bad” footage).
-
You may be able to identify problem files this way: when the project loads, sometimes it will hang or crash on certain files. You should be able to see that in the lower left corner as it’s loading the media. If it hangs or crashes on a certain file, transcode it.
Another issue with PPro is plugins… if you have any 3rd party plugins, uninstall them. You may want to call AJA as well; sometimes the latest version of PPro doesn’t play well with the latest AJA plug-ins.
-
I’ve tried to run with zero plugins loaded (including AJA-stuff) with similar crashes so sadly no-go there. AJA also officially support 6.02.
Bad footage is a possibility. The project doesnt always crash at load though… Will see if I can get around to look into that. I re-built the edit FCP7 when all this “sh-t” happened so good for this particular project.
-
If it was a media file that was good enough to make it through the import process, but was corrupt enough to crash the app, I would think that Erik would notice that he’s “touching” the clip in question every time he crashes…it should be pretty obvious.
Erik, have you tried to launch PPro and just make some color bars and black and see if they can be placed on a sequence and played? That way you initially eliminate media altogether…
Then I might try import one clip…try it on a sequence…if that works, save the project…make a new project, try a different (preferably a different format) clip and see if that works…etc.
There are a couple of possibilities here…
You’ve done a clean install and tried to run the system with only CS6, otherwise I would have said that the most likely scenario was another application in conflict with PPro…several versions ago I had to change anti-virus programs because PPro would crash whenever I tried to create a sequence (?!)
As it is, if the issue is not tied to a media file, then it’s obviously some fundamental thing, and I’d look to things like the status of the targeted cache file disk…is it full? Possibly display card drivers…other system drivers, etc.
While we’ve seen Mac users with issues, there are Mac users who seem to be functioning reasonably well. Unfortunately I’ve been away from Macs as my primary platform for a decade, so troubleshooting system-level stuff on Macs isn’t really my thing these days.
TimK,
Director, Consultant
Kolb Productions,Adobe Certified Instructor
-
There are thousands of variables here, but if it’s an issue of bad media…What if you try creating a new project with everything but the H264 files? I’ve had some trouble with H264 files in the past. Then you could try a new project with just jpegs, etc, and deduce from there.
If you have bad media, your project won’t always crash when the particular clip loads as the project opens. Sometimes the program is fussy in general but handles the bad clips well for a while. Then eventually you’ll get “Media Pending” messages or green screen or the clip will un-link.
If any of those things come up on a particular clip, transcode the clip right away. I had this issue with a multi-codec, 600+ clip project this summer. About 6-7 of the clips were bad, some (if not all) were H264 (though there were plenty of other H264 clips that worked fine).
I know this is a headache, but PPro is a great program. I hope you find a solution.
-
I’ve been having the same problem.
CS6.02. Brand new Mac Pro 12-core with 64GB RAM, Kona LHe plus, Quadro 4000. Boris BCC and a few other assorted plugins.
Crashes randomly with the “Sorry a serious error has occurred” message. Yesterday I spent some time on the phone with Adobe support to address the problem.
The support guy had me create a root user on the Mac, and operate Premiere under that user as a temporary trouble-shooting procedure. Suddenly, Premiere is working faster, has far better real-time CUDA playback performance and is crash-free. Unfortunately, the Kona card is not recognized. But then, maybe that’s what’s causing my problems?
I’ve just started using Premiere after years of Avid DS and Final Cut 7. I really like lots of things about Premiere, but if we can’t get all the parts to work properly together, I’ll have to move on from Premiere.
-
I am in the same boat.
Mac Pro 5.1 12 core
16gb ram
OSX 10.6.8, 10.7.5. 10.8.2. doesn’t matter – I have boot drives for all and get the error on allPeter Tours
TnT Video Services, Inc.
Fort Lauderdale, FLTRI EA5 1974-1977
Convergence ECS1B 1977-1979
Sony BVE 500 1979 – 1984
Datatron Vanguard 1984 – 1993
GVG VPE141 1993 – 1998
Media 100 1995 – 2006
Final Cut Pro 2005 to not too much longer
Adobe Creative Cloud -
Sorry to hear about all the problems you folks are having.
This “Serious error…” thing must be Mac related.
I recently got so pissed at Apple I decided to get a HP Z820. I havent seen any issues like you are reporting.
In fact its been rock solid with Kona 3 external display.
Phil, I also switched from Avid DS and FCP 7 prior to Premiere and my experience with dynamic link and After Effects capabilities has far exceeded my expectations.
Did you work at KPBS many years ago? It seems when I was on the studio crew I heard folks mention you by name.
Tom Daigon
PrP / After Effects Editor
http://www.hdshotsandcuts.com
https://www.youtube.com/watch?v=DxPrG3WUyz8
(Best viewed at 1080P and full screen)
HP Z820 Dual 2687
64GB ram
Dulce DQg2 16TB raid
Reply to this Discussion! Login or Sign Up