Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Apple Final Cut Pro Legacy save as doesnt always save my latest

  • save as doesnt always save my latest

    Posted by Bob Flood on March 22, 2006 at 9:50 pm

    hi

    fcp 5.0.4, g5 dual 2.7, os 10.4

    I have on numerous occasions gone to open a project and it is not how i saved it ie its missing changes. and when i open my last autosave the changes are there.

    so then i save it as the latest version replacing whats there, work some more, and close, saving my changes when done

    next day i open it and stuff is not there?

    ie I have myproject, my project2, myproject3. I open myproject3 and its missing stuff. I go into the archive vault, open “myproject3 date time” and save as my project3, replacing the older version (trying to keep the number of folders down)

    from then i save all, but then i open myproject3 the next day, and its missing stuff again!

    does doing a save all NOT save to the last thing you saved as? do i have to close myproject3, and re open it before it will save correctly? and does the save dialogue that comes up as you close a project really work?

    i am baffled by this, and first thought it was learning curve, but now i cna say it really is happening. I dont have time to conduct experiments to see if it follows save all or save or wahtever, so can anyonel explain this?

    thanx in advance

    bee eph

    Bob Flood replied 20 years, 1 month ago 3 Members · 6 Replies
  • 6 Replies
  • Bret Williams

    March 23, 2006 at 5:07 pm

    You’re obviously confusing projects. For example if you do a save as project1, project2, project3, and then continue to work, just which project are you now making the new changes in? Perhaps you’re making changes to project 2 instead of project 3, etc. It’s easy to confuse things if you have more than one project open.

    I highly discourage the save as practice anyway. It is not the way FCP was designed to work. It complicates the media folder structure exponetially. Every time you render or digitize in the new project name, FCP creates a new media folder for the new project. If you want to use save as for backup purposes, I’d suggest doing a save as project-backup1, project-backup2, etc. But continue to always work withe the file called “project.” Since doing a save as will open the save as project name, that can be a problem if you forget to save as, close the project, open the old project.

    Autosaves fix this problem, but some of us like a little more control. I personally simply go to the finder and right click on my project and choose ‘duplicate” every so often. It numbers it and everything for me and it’s quicker and simpler than save as.

    When you open a backup, wheter it be your own or an autosave, you need to first change the name of the backup to your current project name so that the media folders all stay nice and neat. It will also keep autosave from making an autosave of an autosave, which is just ugly.

  • Arnie Schlissel

    March 23, 2006 at 6:13 pm

    Bret’s right. Using ‘Save As’ to create a new project every day will create extra folders for Capture Scratch & renders that will make media management a nightmare with large projects that take a long time.

    Instead of making duplicate files, why not just make duplicate timelines? Duplicate your TL every morning & give it a new date. Now all of your renders & media will be in the proper places & easy to find, but you still have a daily record of cuts to refer back to.

    Arnie
    https://www.arniepix.com

  • Bob Flood

    March 23, 2006 at 6:22 pm

    BRET

    Thanx!

    i can safely say i am not confusing projects

    I only do save as to make a new project. from that point on i continue to work and save that project.

    Lets say i am working on myproject1 and my system crashes. well my atosaves are at 10 min intervals, so chances are my last autosave is more current than my last save, so instead of re opening myproject1, i open the latest autosave of myproject1. once its open and i am sure its ok, i save as overwriting myproject1 i continue through the day, and i save all when i am done (as well as as often as i can remember).

    HOWEVER

    when i come in the next day, myproject1 is not how i saved it, BUT myproject1 last autosave is

    so, like i say, save all or save project doen not always seem to work

    do i have to 1. open the autosave. 2. save as myproject1, 3
    close the autosave and myproject1 and 4 open my project1 to keep working

    i though once you did a save as and overwrote a project, from then on thats the project you were working on. I mean, thats how everything else works

    bee eph

    Bob Flood
    Greer & Associates, Inc.

  • Bret Williams

    March 23, 2006 at 9:17 pm

    I do that. But I also make project backups. Duplicate timelines is pretty useless for project corruption problems.

  • Bret Williams

    March 23, 2006 at 9:25 pm

    I just tested your workflow and it worked just fine on my machine. I opened a project, did a save as, deleted a clip, saved, then quit fcp and opened the saved as project. Clip was deleted.

    You’re doing something weird or your machine isn’t operating correctly. Are you SURE you’re overwriting the same project you are later opening? Perhaps you have 2 copies on different drives or something? Perhaps you’re overwriting a copy in “FCP projects” and then later trying to open a copy from the desktop?

    I think you just need another set of eyes over your shoulder, because the workflow you described should be fine.

  • Bob Flood

    March 24, 2006 at 12:24 am

    thanx bret

    By knowing that the procedure i am following is the right one and is not suspect, i can rule out operator error or that im nuts, and can now focus trouble shooting elsewhere. like these fine fine apple computers….

    sorry couldnt resis that one

    bee eph

    Bob Flood
    Greer & Associates, Inc.

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