Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Apple Final Cut Pro Missing Event !?!?!

  • Jeremy Garchow

    January 23, 2013 at 8:01 pm

    [Julian Bowman] “I do have this drive backed up by CCC (carbon clone copy) on a daily basis. “

    First, you can find the Event name by clicking on one of the clips in the Project, open the Inspector, choose the gear icon, and Choose “Show File Status”.

    Second, in your Final Cut Events folder there should be a bunch of folders and those are the names of your Events. Any folders in there that aren’t listed in your Events Browser?

    Third, does your backup have a folder that your main drive doesn’t?

    Jeremy

  • Steve Connor

    January 23, 2013 at 8:09 pm

    [Julian Bowman] “Could it be because I am backing up the drive using CCC? Every time I load FCPX it stops and says there are 2 versions of everything and one won’t load, because of the backup drive it obsesses over reading because it appears no one at Apple seemed to think X users could possible have more than one drive, and I have to click OK or continue or some such to boot up, but I have done little bits before and never lost an Event like this.

    This could be a factor, you should never have two events or projects with exactly the same name on your system and available to FCPX. It doesn’t mind how many drives you have but it gets confused if you have two that are exactly the same.

    Steve Connor
    ‘It’s just my opinion, with an occasional fact thrown in for good measure”

  • Julian Bowman

    January 23, 2013 at 8:12 pm

    yeah, see my other recent post, it looks like it is causing problems. So what do I do? Does this mean I simply cannot back up my entire work drive because FCP X is basically unstable due to us not being allowed to ‘turn off’ drives we don’t want on there?

    I’ve experienced my HDD dying and losing 5 jobs which were active that I had to rebuild. Do I have to go back to not having a daily back-up?

    is this not a SERIOUS design flaw?

  • Jeremy Garchow

    January 23, 2013 at 8:14 pm

    You should backup to a different folder on your backup drive. This way FCPX won’t try and mount the identical Events.

  • Steve Connor

    January 23, 2013 at 8:17 pm

    Get “Event Manager X” https://assistedediting.intelligentassistance.com/EventManagerX/ this will enable you to move the backup copies of your Events and Projects to a location where FCPX can’t see them. It’s also great for managing which projects you have visible in FCPX. It should be built into FCPX but it works very well and it’s only $4.99

    Steve Connor
    ‘It’s just my opinion, with an occasional fact thrown in for good measure”

  • James Culbertson

    January 23, 2013 at 9:45 pm

    I’ve never encountered this kind of issue fortunately.

    I personally wouldn’t do an external backup to another internal drive such that FCPX can see both when it is open. This seems to confuse FCPX. I do external backups to an external drive that is never mounted when I am working in FCPX. If I need to backup to an internal drive I use the FCPX duplicate command.

  • Jeremy Garchow

    January 24, 2013 at 2:41 am

    [James Culbertson] “I personally wouldn’t do an external backup to another internal drive such that FCPX can see both when it is open. This seems to confuse FCPX.”

    Exactly right.

    FCPX has certain rules that need to be followed. Once you follow them, it’s all good.

    For instance, this is a direct lift from the manual: “Important: To avoid issues, it’s essential that you place the backup files in a folder (named “2012 Final Cut Pro Backups,” for example) that is not at the root level of your external storage device.”

    That’s rule number 1.

    So, Julian, if you’re using CCC, make your destination a folder that’s on the root of the backup drive. Apple gave the examples of “2012 Final CUt Pro Backups” but you can use whatever you want. Then in CCC, point the destination to that folder. This way, FCPX will not see the FInal Cut Events folder on the root of your backup, and therefore, there’ll be no problems.

    Also, using FCPX’s media management capabilities (like the duplicate Event command) give the duplicated Event a new ID, and will be able to keep track of the separate Events.

    Jeremy

  • Handy Galaherang

    January 24, 2013 at 4:25 am

    Here is from Larry Jordan’s blog https://www.larryjordan.biz/fcpx-manage-media/

  • Michael Sanders

    January 24, 2013 at 12:51 pm

    I use Chronosync to sync my main work drive to a folder on a Drobo.. works fine and even if the drobo is online FCP X doesn’t read the backup as its hidden below the root level.

    Michael Sanders
    London Based DP/Editor

  • Julian Bowman

    January 24, 2013 at 4:09 pm

    Right, I think I understand you – I basically make a folder in my back up 2tb rushes drive called say backup, then do the backup INTO that folder so the structure will be

    2tb rushes BU: backup > all folders including FCP Events.

    Thus when scanning this BU drive it will only see the folder I named backup.

    If this is correct then that makes sense and nice one, thank you 🙂

    Will try it and see if it works out ok.

    Thanks all for the input.

    And just for clarity, I use CCC to back up the whole drive, rushes n all rather than doing specific FCP X backups. I figured that through CCC i’d have the projects backed up too.

    And yes, I do realise that I need to figure out how to ‘handle’ FCP X so to speak, and losing this job is a pain but it was/is only small which is why I am diving in now, to see what needs handling 🙂 So glad to have hit this snag now.

    I still believe that FCP X should allow us to ‘turn off’ drives we don’t want it to see within the app. I have Event Manager X but it is a clunky way of doing this. It just seems sensible and logical to turn off drives that have no relevance to the editor. Or maybe that’s just me.

    Anyway, thanks again for solving the mystery and offering tips.

Page 2 of 3

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