Activity › Forums › Adobe Premiere Pro › Crashy McFreeze-alot
-
Mike Cohen
November 12, 2008 at 8:46 pmeverything is standard def DV, 4:3, 720×480.
Since my last post I have been successful in editing my project with all of my lower thirds deleted. For whatever reason, the other half dozen supers are stable, but the lower thirds make the project as stable as a 1940’s office building in an earthquake. This explains why I had so much trouble.
I make my titles by opening a title, then hitting the button which makes a copy of the title under a new name, so as to not have to re-create anything. Could doing this repeatedly create corrupt titles? The titles become part of the project file, which IMHO is stupid, so it stands to reason the whole project would go south if there is a bad title.
Before I made my sans title project, I exported each title to a file.
In my new project, whenever I imported one of the titles, the project became unstable.
As a final experiment, I imported the old titles into a completely new project with all new video, and the project became unstable.
Finally, even with my stable title free project, I had problems exporting my timeline to a file. Error compiling movie. I had to export in 5 smaller pieces, then re-assemble in a new project, make new titles and I’m done.
I suppose I could have created the new titles in the stable title free project, but why ruin a good thing?
Ok, I think this mess is solved.
Thanks
Mike
-
Tim Kolb
November 16, 2008 at 4:20 amThis is an annoying issue that I’ve had some trouble tracing myself…
I know that in some projects (not all, but frequently) I experience instability when I use titles…I often use the button that is effectively the “save title as” button…
I thought it was just me…
TimK,
Director, Consultant
Kolb Productions,CPO, Digieffects
-
Mike Cohen
November 16, 2008 at 8:22 pmit seems save title as is the culprit, although only causing a problem in this one project. Good to know I am not going crazy.
Mike
-
Ty Wood
February 18, 2009 at 1:45 pmI think you’re (or were) using CS3 and getting the problem, but I came across the thread for getting the exact same error in CS4 Premiere.
“An unknown error occurred while saving the project. Select Save As from the File menu…”
The problem seemed to have rooted from the point of doing sound design on a 45min project–lots of audio level rubber bands, and audio effects on nearly every clip.
I’m not sure what the problem is specifically related to.. memory, external drives, media not all in one folder–these all seems to be solvents that have worked for some people.
My project is too large to fit all within one drive, so I can’t be sure if it would help or not.
Practically every problem I’ve had in CS4 seems to be related to “ImporterProcessServer.exe”. Not only does this process “quit unexpectedly” while working on projects, but if I get the “An unknown error occurred while saving the project. Select Save As from the File menu…” error–I cntr-shft-esc, and End Process on “ImporterProcessServer.exe”. Premiere will lag a bit as the hard drive thinks, and then stabilize, and allow you to save without getting the error.. thus saving your changes and you aren’t screwed.
Save as soon as possible after the force quit–after the ImporterProcessServer process is gone, Premiere is bound to crash or have other problems. One I have is often the audio doesn’t work, and I have to restart Premiere. But at least all your changes got saved, which is extremely awesome in an extremely poor situation.
Hope this is of help to anyone else who comes across the thread. Times like there I wonder where the testers went. Premiere obviously isn’t a high priority on the Suite.
T.W.
Reply to this Discussion! Login or Sign Up