Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Adobe Premiere Pro Strange Occurence after moving capture files

  • Strange Occurence after moving capture files

    Posted by Jerry Black on October 16, 2007 at 10:13 pm

    What I am reporting has to do with rendering errors as a result of moving the raw capture files. Fortunately, this happend on two pieces that were not very large nor where there were many edits.

    I had edited both pieces in PP CS3 after capturing just to get the initial cuts and edits in place. At this time the raw video capture files were located in the same directory as the project files (default location for PP CS3). A few days later I needed to free some space on the main SATA array and moved the raw capture file of these two clips to another single internal SATA device. When I opened the project and told PP the new location of the capture files, then began a new render with final quality settings, I then began to encounter render errors that haulted rendering. The message and history are now cleared unfortunately, since I figured out how to correct the issue, but the message had to do with no video detected at the frame. Not very informatived at all.

    After spending quite some time zeroing in on the problem area and looking frame by frame, at the pont where rendering stopped I was able to find the bad frames which were completely undetectable playing and searching for the defects. These areas showed up as a frame or two with badly pixilated video which could be decoded. THIS DID NOT EXIST WHEN I DID AN INITIAL RENDER OF THE TWO CLIPS after the initial capture. After locating and removing the bad frames from each clip, rendering completed normally.

    I believe the cause was the fact that I moved the capture files from one drive to another sinced it happened to two different clips with different capture files. Remember, an initial rendering of both clips produced no issues. It only occured after I moved the raw captures. Why they became damaged is a mystery. Moving the captured files back to the original location on the SATA Array DID NOT FIX THE PROBLEM so they were indeed damaged by the move.

    This is the first time I have ever encountered this issue and would caution anyone from moving capture footage until after the project is fully rendered and completed.

    Hope this helps someone else from making the same mistake.

    Jeff Brown replied 18 years, 6 months ago 3 Members · 2 Replies
  • 2 Replies
  • Vince Becquiot

    October 17, 2007 at 12:26 am

    Absolutely. That’s why there is a project manager. Make sure you use the copy to folder to move things around.

    Vince

  • Jeff Brown

    October 17, 2007 at 12:12 pm

    …sounds like it could have been from a disc error. That would get replicated one induced.

    -jeff

We use anonymous cookies to give you the best experience we can.
Our Privacy policy | GDPR Policy