Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Apple Final Cut Pro Legacy Mediamanager failing seemingly at random

  • Mediamanager failing seemingly at random

    Posted by Shawna Talbot on May 30, 2012 at 10:01 pm

    So my boss whats to media manage a bunch of our sequences to send out to a sizzle company. Typically we’ve media manage our items to the drive we’re sending off. Only this time we’re sending a huge amount of data.

    We’re using a Lacie BIG 6TB via thunderbolt cable and trying to media manage 4.4TB worth of footage. It starts off fine and then for some reason it keeps crashing about halfway through. It says it’s going to take 4 hours so we’ll let it go and work on another computer, but come check on it every hour or so.

    Is there a reason why it keeps crashing? Is there something we could be doing to make this a smoother process? We haven’t changed our media settings at all from when we’ve done 2TB media manages. Is it because of the size we’re attempting?

    Shawna Talbot replied 14 years, 2 months ago 2 Members · 6 Replies
  • 6 Replies
  • Andrew Kimery

    May 30, 2012 at 10:41 pm

    The size could have something to do with it. Is there an error message that comes up or just FCP just freeze?

    Have you tried only doing one sequence at a time?

  • Shawna Talbot

    May 30, 2012 at 10:46 pm

    There’s an error message and as soon as I can get a hold of the person who keeps closing it out before I see it I’ll be able to tell you what it says. Or at least I think there is? Maybe it just freezes. I just keep getting told it stopped working. Will update this when I hear back.

    Actually maybe FCP just freezes if they know for a fact that it keeps failing around the half way mark.

    And no, we haven’t tried to do it one of the time like that as there are a lot of sequences, but maybe that’s just what we’ll have to do.

  • Andrew Kimery

    May 30, 2012 at 10:52 pm

    You could also try splitting up the sequences into two batches to see if that works. If batch A goes fine but batch B fails then there might a corrupt sequence or piece of media that is causing the problem. Take batch B and split it into and see if one group fails again. You’ll have to keep splitting the remaining sequences into two groups until you find the one that is causing the problem. And then you’ll have to find the piece of media that’s causing the problem (assuming it is a piece of media of course).

    If splitting it into two batches works then odds are it was just too much for FCP to handle in one big chunk.

    -Andrew

  • Shawna Talbot

    May 30, 2012 at 10:54 pm

    Yeah, that’s actually what my plan is to try in a bit. (There’s an editor using FCP currently on the machine we need). I just figured I’d jump the gun and try to see if these was a common type problem for others who’ve tried to media manage large flies before.

    🙂 Thanks for the quick response!

  • Andrew Kimery

    May 30, 2012 at 11:05 pm

    Hey, no sweat. Good luck!

  • Shawna Talbot

    June 5, 2012 at 7:38 pm

    Sorry to take so long getting back to you on this. Office has been a bit of a mess lately with a bunch of deadlines suddenly being pushed up. Not that my answer will help much. Asked what the error said and the person said they didn’t look at it. Just clicked: okay.

    I bet you can imagine my annoyed response to that. They then mentioned that it was a huge wall of text because the FCP program itself had crashed. Not sure how much I can really trust this person’s word, but what can you do when you didn’t see the error yourself? So sounds like FCP itself crashed about halfway into the media copying and gave out a wall of text.

    So much help there. I’m just going to break the project up I’ve decided when I get back to it. However, that may be a bit as that has actually been one of the few things that has gotten it’s deadline pushed back.

    Ah, the wonderful world of TV, right?

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