Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Apple Final Cut Pro Legacy Media Manager: Error Found During Processing?

  • Media Manager: Error Found During Processing?

    Posted by Brad Bussé on February 25, 2009 at 1:35 am

    I’m trying to archive a project w/ Media Manager the same way I normally do; open the project, select the final timeline, use Media Manager to Copy timeline w/ relevant media to a new location. However, I can’t get this project to work; it seems to copy all of the media, but then at the end the sequence doesn’t get created. Instead, I get an “Error Found During Processing” message;

    “The following error was found during the processing of your selection by Media Manager.

    Sequence Error: Unable to add clip to sequence. Possible media limits problem in clip or sequence.”

    Anyone know how to get around this? I tried copying with all media instead of clipping source w/ handles, but to no avail.

    Brad Bussé replied 15 years, 10 months ago 2 Members · 5 Replies
  • 5 Replies
  • Brad Bussé

    March 4, 2009 at 9:40 pm

    Anyone seen this error before?

  • Chance Chancellor

    July 22, 2010 at 3:57 pm

    I am now having that same error.

    “When we are done with a project we like to use media manager to consolidate only the used video (with handles) to save space.

    This has never posed a problem until lately. On about five of the last projects when the media manager begins reconnecting media we get the following error:

    “Sequence Error: Unable to add clip to sequence. Possible media limits problem in clip or sequence”

    The only option is to abort so a new sequence is never created. Also, it will not tell me which clip caused the error. I tried moving everything into a new sequence and got the same error. Then I tried it without handles, then I tried it without deleting the unused media. I have also tried the projects on other computers (All 10.6.4, all FCP 7.02) All had the same error.

    The only other reference to this error I can find deals with a multicam edit. None of these projects have any multicam edits.

    Anyone got any ideas what is going wrong? I have tried to think if we are doing anything differently lately and the only thing i can come up with is using more of Tiffen’s DFX filters. ”

    I also posted this on Apple Discussions :https://discussions.apple.com/thread.jspa?threadID=2516299&tstart=0

    Anyone else had experience with this issue?

  • Brad Bussé

    July 22, 2010 at 4:20 pm

    I don’t remember the outcome, but it very well could be due to the 55mm/Tiffen DFX filters– I use those extensively.

  • Chance Chancellor

    July 22, 2010 at 7:05 pm

    OK, I think I have found a workaround. It is not pretty.

    First to find the clip with the error:
    1.Duplicate the sequence you want to Media Manage.
    2.Use remove attributes to remove all filters in the sequence.
    3.Media manage as normal.

    Now you will get an error on a clip. This time it will tell you the clip name and create a sequence successfully with the affected clip offline.

    (Mine was from a Sony EX3, had one color correction and a broadcast safe filter. Additionally it had a high speed ramp and we used a freeze frame from the clip) I suspect the freeze frame as the culprit.

    Now that you know the affected clip go back to your original sequence with the filters:
    1.Duplicate that sequence
    2.Delete the problematic clips
    3.Media manage as normal
    4.Manually move the affected clip in the finder to the destination where you are consolidating your media.
    5.Paste the bad clips back into your consolidated sequence in final cut.
    6.Reconnect your problematic clips to the one you moved in the finder.

    I am finishing up a test consolidate right now. Hopefully it will work.

    Hope this helps others, like I said it is not pretty, but it is a workaround.

    Thanks for the quick reply Brad. That helped me pin it down.

  • Brad Bussé

    July 22, 2010 at 7:26 pm

    Thanks for posting the solution.

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