All of a sudden, PPro stops responding - correction, the WHOLE COMPUTER stops responding. Mouse won't move, alt-tab doesn't work, ctrl-alt-del doesn't work - I actually have to power cycle the machine.
This is not a very complex project (the project file is only ~1.4MB). Four bins for footage, audio, titles, & misc. extras, five sequences, and a few video effects. HDV footage from a Sony HVR-Z1P, approx 2.5 hours total.
I've been working this project (the first since I upgraded from 5.5) since Saturday 24 November. Up until 60 minutes ago, all was well. Then I switched from one sequence to another and it hung the computer. This machine has NOT had any driver updates since before I started the project. Nor has it had new or updated software installed today - including windows updates. I don't let anything update while I'm editing, and I don't update application software in the middle of a job unless it's a fix for a specific problem. There is no real-time anti-virus or anti-malware software on this machine, although I scan periodically.
I've tried to import the old project into a brand new project, and still it hangs. I open an old project, and it's fine, so I'm guessing I've got a corrupted project file. I'm about to try opening the previous version to see if that works, but I'll post this first in case the computer hangs again.
Is there any other way to "clean" a project file, or to run PPro in "safe mode" or a debug/logging mode?
I'll be returning to CS5.5 for the next project - perhaps wait a while until CS6 stabilises.
John T Smith wrote:
What I have read as a "sometimes" cure is to open a new project and then import the old into the new
That's a standard troubleshooting step but it looks like you tried this already. You can also try using the Project Manager.
Yes, I made a new project and imported the old one. It locked up again when I tried to switch to a particular sequence.
I usually have 3 or 4 (or more) sequences when editing - one for each camera's footage, a "scratchpad" for testing or playing around with effects, and one called "assembly" where the actual edits happen.
This project locks the computer whenever I try to view the sequence containing camera 1's footage. Fortunately the "assembly" sequence seems to be OK - which is good, because I would NOT like to have to do it all from scratch. Maybe if I delete that sequence and create it again - it's just a container for viewing the footage from a particular camera, no great loss if it has to be deleted and recreated.
Well, that worked for about 10 minutes
I removed all other sequences from the project, saved, exited, started again, and it was fine to begin with, but it locked up again while I was using JKL to jump forwards and backwards to choose an edit point. Had to power cycle the machine again.
Project manager is now trying to create a new trimmed project. I suppose I can also create a new project, and just import the sequence, instead of importing the entire project.
Well, well, well. The brand new trimmed project hung after about 10 minutes. This time it hung in the midst of a save (not autosave). It also left bits of menu on the screen, so I thought "this time, I'll investigate the video driver".
Yep, it's the latest 306.97 from nVidia
Yep, the gamers' forums are full of "hang" and "freeze" complaints with this version. There are recommendations to adjust a few of the settings such as Power management mode from "adaptive" to "full performance" and multi-display/mixed GPU acceleration from "multiple display performance mode" to "compatibility performance mode", so I'll give those a try before rolling back the driver.
Given the stability of Windows 7, it's very, very difficult for a program to lock up the whole machine and cause you to hard reboot. That kind of situation is almost certainly indicative of a deeper level system problem somewhere. PP may be the trigger, but it's not likely to be the actual cause.
That's what I thought - how could an application cause a hard lock? Anyway, it seems to be caused by the video driver - at least, following nVidia recommendations and changing a couple of settings has improved the situation - I haven't seen this kind of video driver/hard lock problem for a long time - probably in the days of WinXP service pack 1.