Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Forums Apple Final Cut Pro Legacy FCP 7 Autosaves go offline and then can’t reconnect to media

  • FCP 7 Autosaves go offline and then can’t reconnect to media

  • Scott Clements

    March 2, 2013 at 12:32 am

    Hi, guys.

    I’m having a really bad problem with my fcp project’s autosaves. They are essentially useless, because when I need to access one, it is offline. Then, when I try to reconnect to the media, it says that the reel, start and end and rate are all wrong (which they really aren’t) I think the project file may have been corrupted? But I’ve tried saving as a new project and even copying bins over to a fresh project and the same thing keeps happening. So, it’s very scary working with this project now as my autosave doesn’t help. I’ve also tried trashing prefs and repairing disk permissions, but neither worked. Anyone have any suggestions? Has this happened to anyone else out there?

    Film Editor, London UK

  • Spencer Averick

    March 2, 2013 at 1:57 am

    This happened to me once before. I think I simply changed the name of the autosaved file back to the original file name and everything connected. So instead of “Project File_08-26-12” I deleted the date and just called it “Project File”. For some reason FCP got confused when the project file’s name was different, which is obviously not always and shouldn’t be the case.

  • Scott Clements

    March 2, 2013 at 2:18 am

    Hi, thanks for the response. I tried that, but in this case it wasn’t the issue. I simply couldn’t make the autosave reconnect to the media. I tried opening an autosave at the same time as the project on the drive, but it gave an error about the project being unreadable or being too new for this version of FCP (which is not the case). What I discovered was that I if copied the main project file to my computer and ejected the external drive that had all the media on it, I could open the autosave and the main project side by side. I then copied and pasted the latest sequence from the autosave into the main project and was able to relink. It was a fix, but obviously not ideal. Something is definitely wrong with my autosaves (this has happened a few times before, but I didn’t have time to investigate it too much) I think the external drive may have problems. Disk Utility said it was fine, but it seems to be the rotten apple here.

    Film Editor, London UK

  • Nick Meyers

    March 2, 2013 at 10:42 pm

    that’s a really weird problem, and i haven’t experienced it myself (fortunately!)

    i wonder, have you tried accessing the autosave version in the “Restore” function in the file menu?


  • Scott Clements

    March 3, 2013 at 2:58 am

    Thanks for the suggestion, Nick. I’ve never had to do that in the past with autosaves, but I’ll give it a try.

    Film Editor, London UK

  • Bret Williams

    March 4, 2013 at 12:50 pm

    That’s the correct way to utilize an autosave. Shouldn’t have to do all the reconnecting media. It should open with the correct name as well and you just do a save. But still, something sounds funky.

  • Nick Meyers

    March 4, 2013 at 1:58 pm

    i dot know if the “restore” approach will be better or not,
    just thought i’d throw that in.

    but i just remembered…

    whenever i crashed, my autosaves would open with some clips offline.
    always the same one, and the common factor was they had no reel#
    some were exports of edited shows,
    some were music files

    but it always happened when opening an autosave.

    this is 7.03

    in my case, reconnecting worked and was pretty quick.


  • Nick Meyers

    March 4, 2013 at 2:00 pm


    i was happy to live with my reconnect after crash.
    but if you find that lack of reel# is the cause of your problems,
    then maybe you should add reel#s to your clips.


  • Bret Williams

    March 4, 2013 at 3:27 pm

    Originally, autosaves only existed on their own, but people couldn’t see to grasp the idea that the project name is paramount in keeping things neat and tidy in FCP legacy, and that before opening the autosave they optimally should move it to the project folder, name the old version something else, and then rename the autosave the same name the older version had, THEN open it. Moving it keeps the directory structure in tact, and renaming it will keep your capture scratch in tact, and keep you from having a mess of autosaves of an auto save.

    Or to alleviate all that mess, use the restore function, which was introduced 7 or 8 years ago to make life simpler.

  • Scott Clements

    March 4, 2013 at 4:15 pm

    Thanks for the tip about the restore. I just used the autosaves the old fashioned way.

    Unfortunately, the restore function brought up the error message: ‘This project is unreadable or may be too new for this version of Final Cut’.

    I might try adding reel numbers to all my clips.

    Film Editor, London UK

Viewing 1 - 10 of 16 posts

Log in to reply.

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