-
Not Responding
While my system is stable for the most part, the one problem I run into periodically is the “Not Responding” variety.
I can be doing something as simple as editing a title or simply switching between Premiere and Media encoder (especially so when encoding something – in fact with Media encoder encoding I’d better not want to do much of anything else) or Windows Explorer and the program locks up, part of the screen goes white – sometimes if I wait it out it recovers, sometimes not. Larger projects cause more such problems (project file over 50 megabytes, lots of titles).
I have my auto-save set for 5 minutes just in case, annoying but it has saved me from re-work on numerous occasions.
If Not Responding does not recover, eventually I need to do a force quit or sometimes get the AppCrash error.
CS 4.2.1.0, i7 860 @ 2.8ghz, 8gig ram, Win 7 64-bit, Projects saved to system drive (250gig), media on 1.5TB internal SATA drive, Media Encoder renders to 3rd internal 1TB drive, GTX 260
Thanks
Mike Cohen
-
2 Replies
-
Mike – One thing I have noticed, on both PC and Mac, is that when doing something when Autosave pops up can hang up PPro. Happens quite frequently to me. Especially if I am typing in numbers in the Effect Pallette. I’ve made my Autosave to be less frequent, but hit Save keystrokes more often – those keys will probably be the first to wear out on my keyboards… Haven’t experienced much problems with AME though.
TC -
Just today I was discussing this issue with our computer guy – he asked what kind of problems I encounter. On the i7 machine which is tastier than the Core2duo system, I made a basic HDV sequence, stacked 4 layers of video and a title and hit play – it played with the expected jitters when using full quality (this is CS4 by the way).
Granted running on a non-raid internal drive perhaps this level of performance is expected
So we turned on the resource monitor, hit play, and the Premiere interface areas of the screen went pale (about 50% opacity white over the program – no “not responding” error – just sat there. I waited a few minutes, then hit the X to close the program, and got the APPCRASH info saying the premiere.exe had crashed – obviously.
Odd that having the resource monitor displayed would cause a program crash – or perhaps coincidence.
Anyway…
Reply to this Discussion! Login or Sign Up