-
ERROR message prevents editing a file
I am in the midst of editing a 50 minute video, which I have broken up into shorter segments, each a project unto itself, then I will edit them all together as one program. In the past I have had major problems with ‘long’ projects, hence the shorter segment technique.
Things were going quite well, until segment (project) #4. While editing, an Error Message came up, the familiar “Adobe Premiere Pro CS3 has encountered a problem and needs to close etc.’. Usually, I can get past this and continue editing, but not this time. Each time I open the file to continue editing this message pops up, just after I move the mouse. I can open other sequences in the same project without problems. And, all the previous segments (projects) function fine.
Since the project is large I put the 30 hours of video on an external drive and do the actual editing on an internal drive and save a back up to another internal drive (actually the C: drive, on which I also have my scratch disks)
The external drive is nearly full, but I’m only using it as ‘storage’ and I have checked it for errors. It’s a 500 gigabyte drive and I have 29.6 Gigabytes left. It seems to be working fine, although it could the culprit I suppose.
This particular segment does have a rolling title scene, created by the Adobe titler, but so do the other segments. I know that can sometimes be problematic.
While investigating my error problem I realized the C: drive was also nearly full, so I dumped a lot of files and defragmented it. I also checked and defragmented my editing harddrive. I figured that would solve the problem, but it did not.
Other steps taken:
* I up-dated my viceo card
* I created a new accountIf anyone has an idea what the problem may be and how to solve it, please let me know. I have invested 8 hours in this segment and don’t want to lose it. Of course, I’ve spent more than that trying to solve the problem and probably should have just re-edited the darn thing. But, I’m stubborn!
Thanks!
Wendall
Filmmaker42
Sorry, there were no replies found.