Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Apple Final Cut Pro FCPX – All keywords / Compound clips – gone!

  • FCPX – All keywords / Compound clips – gone!

    Posted by Mark Allen on September 26, 2011 at 8:05 pm

    In order to really test FCPX I decided to edit an actual commercial project. Otherwise, it’s hard to know how it performs. After 2 days of work, I have hit a huge problem I’m hoping someone can help me solve quickly as my deadline is fast approaching.

    Out of old habit, I decided to duplicate the file called “CurrentVersion.fcpevent” in my folder that contained all my media and change the name of the new one to “_v02”. I even duplicated another one and set it onto a different folder for safety. I opened up the _v02 and it came up with an error and all my keywords and compound clip collections were gone. What did remain was the storyline project… but that’s not a lot of good when I’m still swapping clips and finishing my edit.

    So I quit FCPX, tossed that new one in the trash, and opened the file that was there before.

    Same problem. I moved that file to another drive, put in the back up duplicate I made…. opened… same problem.

    Somehow my effort to make a safecopy has completely destroyed my keywords and compound clip collections and basically the entire event except for the edit project? Is there any solution for this?

    Mark Allen
    Allucinari
    http://www.markallen.net/demo

    Gerald Baria replied 14 years, 7 months ago 4 Members · 6 Replies
  • 6 Replies
  • Andy Neil

    September 27, 2011 at 12:43 am

    I think you’re a victim of the autosave function. Obviously, you know now not to duplicate the currentversion.fcpevent, but when you opened that file, it opened the actual current version of your event. The error of having two versions of that file probably caused the keywords to go missing, but since it opened if FCPX, that state was saved to the currentversion.fcpevent. Closing and restarting only returns you to that same place.

    If you have Time Machine, you might be able to find a version of the event before you messed with it. If not, I don’t know that there’s anything you can do.

    You can (and should) certainly try trashing preferences, as it does no real harm to do so, but I wouldn’t expect it to work.

    In the future, I would suggest either using the duplicate Event function in the program, or else duplicating the entire event folder and changing the folder name. I see that “currentversion.fcpevent” file as a sort of preference, not like the project files that we’re used to dealing with FCP 7.

    Andy

    https://www.timesavertutorials.com

  • Mark Allen

    September 27, 2011 at 3:20 am

    I appreciate the information.

    I am so on the fence with this app. There are things I really liked, but – boy – there are things that are frustrating.

    Duplicating files for safety/back-up is standard procedure in every application I’ve ever worked with in the last 20 years – I think it’s a little irresponsible for Apple to allow such a common and simple action to be so destructive. If you are not meant to touch something in the finder, those things should be made hidden or enclosed.

    I am totally dumbfounded and now facing probably a sleepless night rebuilding this (in FCP7) just to make a deadline. Not a good first impression especially after so much preparation to give it a fair test.

    (About time machine – these files were on my external drive because i couldn’t fit all the media on the internal… and I didn’t back up the external except for the one file I was modifying which apparently didn’t help.)

    Mark Allen
    Allucinari
    http://www.markallen.net/demo

  • Mark Allen

    September 27, 2011 at 3:39 am

    So I took a break from this while waiting for some responses and edited another project due Wednesday in FCP7. Finished it, decided I’d take one last look at the FCPX project file. Opened up FCPX and suddenly – my event is there again.

    I have no idea why or how. I did nothing but use FCP7 all day since posting my problem. (And before posting I’d opened and closed FCPX a few times and restarted.) So I really have no solid solution for anyone who does this in the future except “Try opening FCP7 and making a new project and using that, then quitting and try again.” You could be right about the preferences if FCP7 and FCPX share preferences. I’m a little nervous about quitting FCPX!

    I’ve now followed the correct way of duplicating the project inside FCPX and will finish the spot there… very very strange.

    Mark Allen
    Allucinari
    http://www.markallen.net/demo

  • Davee Schulte

    September 27, 2011 at 5:33 am

    See, the app does have a mind of its own. It sensed your frustration and replaced your event. Everything really has changed in post!

  • Andy Neil

    September 27, 2011 at 5:54 am

    I’m glad you got your event back, but keep in mind that you CAN duplicate from the finder…you just happened upon the way to cause problems. 🙂

    It’s similar to the file structure you see in P2 cards and such. If the lastclip.txt file is missing or corrupt, then you lose access to the video files that were created on the camera.

    As soon as I noticed that the actual event file is called, “currentevent”, I realized that ALL events had a file with the exact same name. That told me that if I wanted to duplicate the event from the finder, that I needed to duplicate the entire folder (which is labeled as the name of the event).

    I understand why this tripped you up; FCP 7 contains the entire project info in a single project file, but FCPX doesn’t. Luckily this didn’t cause any permanent damage to your event/project.

    Andy

    https://www.timesavertutorials.com

  • Gerald Baria

    September 28, 2011 at 5:43 am

    Ahahaha. Everything really did. Thats how smat FCPX is.:)

    But seriously though, at its current state. Everytime a weird thing happens on FCPX, usually its fixed by either a relaunch or a restart.

    Quobetah
    New=Better

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