-
Numerous error messages, virtual memory problem or not?
Hi there,
Really hope you can help me with this. I’ve gone over the forum and used many of the very helpful strategies suggested but so far no concrete solution.
I’ve been working on a project since just before Christmas with some very nice ex1 footage using CS3. During this time I didn’t have any problems and edited the project happily as well as a few smaller projects that were due over the last few months.
Recently I noticed that Premiere Pro was closing abruptly, usually saying something along the lines of ‘Adobe Premiere Pro has encountered a problem and needs to close’. After this would happen on reopening the project it would suggest I make a copy of said project to save rather than working from the original, presumably to avoid problems of corruption. I did this and as this didn’t occur frequently it wasn’t really a big problem.
Over the last week or so , just as I’ve nearly completed the project, these error messages have become more frequent, most usually occurring when rendering or exporting. As I have previously rendered and exported the entire project an I know that it isn’t a problem with the plug in effects or the footage/audio. Other error messages I get include ‘error comping movie’ and sometimes when rendering I don’t even get an error message, the dialogue box simply freezes on a certain arbitrary frame and that that. I have plenty of space both on my C Drive and on my external HDD where I keep all the video and where the scratch disc is set to.
Among the things I’ve tried include…
1. Reinstalling PPCS3
2. Installing all upgrades
3. Renaming any files with spaces in the name.
4. Copying the sequence to a new project
5. Increasing the OS virtual memory.
6. Using MSConfig to remove unnecessary start up problems.
7. Using enditall.exe immedietely before loading Prem Pro.
8. Rendering with the monitor window closed
9. Removing any titles as well as any images over 3000 pixels wide.
10. Defragging all HDD
11. Turning windows indexing off from my external HDD.
12. Smashing my head repeatedly against my desk.It seems like this must surely be a memory problem, I have had similar problems like this before when working on a project of this size over a long period of time. Next to this extent though. It has been suggested that I reformat my system but that seems to me to be overkill, especially given that I got my new external HDD only this Christmas.
Any suggestions will be massively appreciated. I am slowly rendering the project out to save time but I can only manage it in 30 second some blocks and sometimes it crashes before I can even save this progress after! Dear oh dear.
-
7 Replies
-
As an added bonus, Adobe Premiere Pro has now decided not to be able to save my project at all. Every time I get a succesful 30 secs or so rendered, on saving it says something along the lines of ‘Adobe Premiere Pro has encountered a problem whilst saving…please ‘save file as…’ in order to save your project. On attempting this however the same message comes up. Forcing me to eventually give up and load it up to try again.
-
I’ve attempted to work the footage AGAIN in another project and on opening it says ‘The scratch disc location is either write protected or unavaliabe. Premiere will set My Documents as the location instead.’
Perhaps somehow my external HDD is blocking my render files due to it becoming somehow an ‘unsafe’ location?
-
My guess is that Premiere is just running out of RAM. CS3 is only a 32-bit application, getting upgraded to 64-bit in CS5. I found it was not uncommon for Premiere CS3 to exhibit your symptoms in HD projects over a half hour in length, and/or with a fair number of source clips.
Things you can do that will help a bit: Close any timelines that you aren’t editing on. Switch from performance to memory mode in preferences-general. If your OS is 32-bit XP or Vista, make sure the 3G memory switch is set (Google it). I also keep my project window in list mode, although I’m not sure that really helps.
These fixes just open up a bit more memory, so they won’t completely fix your problem. For that, you may have to upgrade to 64-bit OS and apps.
-
Hi Eric. Thanks a lot for your response. I’ve since reinstalled CS3 and opened a new project, importing the former one into this. I’ve also deleted all my old preview file folders as they were piling up with copies of basically the same project which I felt might be adding to the confusion. So far things are running a bit better and I can manage to save my project. While rendering there are less freezes happening but rendering does always seem to stop before its finished at an arbitrary point saying ‘error compiling movie’. Once I open the project up again I can carry on as before. I’ve taken your advice and hit the 3G switch so hopefully that might help my problems, although it seems difficult to find out how to check if the switch is actually in effect?
Once again thank you for your prompt and useful advice,
Jonathan
-
The 3G switch seems to have helped a lot as crashes are clearly less frequent and the performance tab on windows task manager looks a lot better when rendering. Still having a lot of hassle though. Blah. Its so frustrating that its got like this when only a week ago it was fine.
-
Also I should add that this is Windows XP and a 64 Bit OS
-
The solution in the end was to abandon CS3 and just get CS4. I think what put me off before was assuming that since CS4 was the step up in the Prem Pro software it would be too taxing for a computer which was also seemingly being taxed by CS3. Actually the opposite applies, it seems if you have a 64 Bit system CS4 is the way to go for a smoother time working with it with less potential problems. Hope this helps anyway else having the same trouble.
Reply to this Discussion! Login or Sign Up