Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Adobe Premiere Pro urgent, please! – ppro1.51 can`t reopen existing project

  • urgent, please! – ppro1.51 can`t reopen existing project

    Posted by Alex Horvath on January 31, 2006 at 4:12 pm

    Using ppro1.51 with cineform AHD on a HPx9300 quad.

    While editing an error occured (something like “dobey…” and “path”). Closed the warning-window and had the chance to save. Closed premiere and tried to open the project again after restarting premiere. Project opens just so far that you can see a clip-picture in the preview-window and than quits premiere.
    Urgent help would be apprechiated!

    Alex Horvath replied 20 years, 3 months ago 4 Members · 10 Replies
  • 10 Replies
  • Alex Horvath

    January 31, 2006 at 4:45 pm

    actual error-message is:
    [\dev\CaptainDoby\Backend\Src\Sequence\LinkContainer.cpp-226]

  • Steven L. gotz

    January 31, 2006 at 4:54 pm

    I suggest you open an earlier Auto-Save file or copy and go from there.

    Steven
    http://www.stevengotz.com

  • Alex Horvath

    January 31, 2006 at 5:05 pm

    thx, that`s what we did, but problem is, going ahead with the project, causes the same error message!
    What could cause this error?

    Isn`t there any opportunity to see if there is a error in the opened projectfile in the editor?

    It`s a big project and we are too far advanced to use the latest copy, it

  • Steven L. gotz

    January 31, 2006 at 6:20 pm

    I don’t know anyone capable of looking at the file and seeing the error.

    What are you doing when you say “going ahead with the project”?

    Steven
    http://www.stevengotz.com

  • Alex Horvath

    January 31, 2006 at 6:42 pm

    thx for the answer steve.

    “going ahead” means, open a 3h old project, start cutting again and than this errormessage appears again, sometimes when putting clips from projectmanager to timeline, sometimes when shifting clips at the timeline.
    We are doing only cuts, nothing else.

    not good, not good…

    alex

  • Steven L. gotz

    January 31, 2006 at 10:09 pm

    I have no idea what the message means, but if I were you, I would create a new project and import the old one into the new one just to see if the problem is in the header area of the file. Unlikely, but easy rnough to try.

    And delete all of the preview files. That might be causing a problem.

    Steven
    http://www.stevengotz.com

  • Alex Horvath

    January 31, 2006 at 10:39 pm

    As I thought the solution was found in the projectfile (opened with editor)
    I searched for “Linkcontainer” and found 132 Linkindexes. Deleted index for index and tried to reload the project. Finally I found a defect(?) one and I could restart my project.
    Until now th errormessage doesn`nt come again.
    What makes me wondering is, that after restarting the project, it was exactly the same project, nothing was missing after deleting the link index, and finally nobody knows what really happened….

    alex

  • Aanarav Sareen

    February 1, 2006 at 7:58 pm

    As a word of caution: Always make a backup copy of your project before making changes to it in the editor. ALthough you seem to have done it properly, a lot of people may kill the entire project if something is deleted accidentally.

  • Jeanfr

    February 1, 2006 at 9:43 pm

    Another way to open a seemingly corrupted project file is to start another project and import the old project into. This method could also have worked in this case.

    =======================
    JF Robichaud
    Low Budget Productions

  • Alex Horvath

    February 2, 2006 at 1:43 pm

    [JF Robichaud] “Another way to open a seemingly corrupted project file is to start another project and import the old project into. This method could also have worked in this case.”

    Yes could but did not: Imported in a new project, after a while the errormessage showed up again and again…

    alexx

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