Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Apple Final Cut Pro Legacy Cant export sequence without freezing…

  • Cant export sequence without freezing…

    Posted by Paul Harb on December 7, 2008 at 4:28 am

    Im trying to export a rather long sequence and every time I try and export it, the machine freezes up. Ive tried a number of workarounds. copying to new sequence to carious codecss when rendered freezes, creating new project, throwing away prefs, everything I try to do freezes up like something has become corrupt in the sequence? Not sure what else to do…any ideas would be appreciated. thks.

    Paul

    Paul Harb-Producer/Director
    Wrong Beach Multimedia
    Dual 3.2 GHz Quad/10.5.5/8GIG RAM/FCP 6.0.4/QT 7.5.5

    Andrew Commiskey replied 17 years, 5 months ago 3 Members · 2 Replies
  • 2 Replies
  • Bill Dewald

    December 7, 2008 at 4:41 am

    You’re on the right track, you’re probably either dealing with a corrupt sequence, or some corrupt media.

    A third possibility is a oversized still image on the sequence. That would be an easy one. Is that the problem?

    When you said “copying the sequence to various codecs”, did you mean changing the codec in the sequence settings? Or changing the output settings?

    When you said – “creating new projects”, did you copy the sequence from your old project to a new project? Or copy/past the contents of your sequence into a new sequence?

    Do you have enough free space for the export on your target drive?

    Is the sequence rendered? If so can you trash the render files and re-render? If not, can you render it first?

    If it is un-rendered, and the render fails, try rendering small chunks at a time. This will isolate the corrupt section of the timeline.

    If/once you isolate the corrupt part, try:

    1. making the footage offline, and then re-ingesting

    2. deleting the section from the timeline, and recreating it by hand

    3. deleting and re-ingesting the offending media.

  • Andrew Commiskey

    December 8, 2008 at 4:07 pm

    It might be something as simple as corrupt render files. Trash your render files and re-render. I’ve seen this happen more than once.
    Drew

    Chaos is the beginning of everything.

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