Export DV project is taking ages!

[Steve Eisen]

Is your timeline fully rendered?

Steve Eisen
Eisen Video Productions
Vice President
Chicago Final Cut Pro Users Group

[Mattias Molen]

After about one hour at 0% I cancelled the export. I can change the sequence settings but since it’s not my project I’d rather not. Unless ofcourse it fixes the problem 🙂

The timeline is fully rendered.

[Mattias Molen]

I’ll certanly try that. Thanks! I appreciate your input.

Wich “usual litany of corrective steps to counter FCP weirdness” do you mean?
The things i’ve tried are in my first post. I’ll try anything else.

[Mattias Molen]

Ok, first thing tomorrow morning.

[Mattias Molen]

Repaired permissions. No luck! Still slow. Nothing’s changed. I don’t understand why my CPU’s are barely doing a thing during export.

[Mattias Molen]

Oke,

So now i tried exporting via Compressor. After about 5 minutes it stops the export with the following message: “Processing service request error: Final Cut Pro.app generated an error or unexpectedly quit”

Anybody?

[Glen Hurd]

When you say it’s rendered, are you saying that you’re working in a multitrack timeline with all the original video elements – and that the timeline has been rendered? Or are you working off a self-contained master file that is in its own sequence for title work? I’m assuming the former, but didn’t want to assume.
If the former, then when you add a title, that segment becomes unrendered, and if there’s a corrupted file/graphic underneath, it may be giving you trouble. Even if a timeline doesn’t need to be rendered for playback, it does for final export.
Try setting an in and out (I-O) point of an already rendered segment of the timeline (without your titles) of about 1 minute and see if that will export normally.
If that doesn’t work then open up another project entirely and see if you can export to the same location with the new program. You may be experiencing something program or system wide if you can’t – like a corrupted destination drive. If there isn’t another project, make one quickly to the same settings using some of the same source footage. It’s a simple test to see if the problem is deeper than your show.

If the first render of the 1min output goes OK, then you need to dig around the files/graphics/filters involved in the area where you’re laying titles.
So what I would do next – is then choose an IO around each title area and try and export each one until I find out which one is locking up the system. Control-B disables clips selectively so you can see which clip may be giving you trouble, trying an export after each is disabled.

If a simple I-O of one minute off a virgin portion of your timeline doesn’t export, but other shows are behaving themselves, then you might want to try changing the opacity down and upI to remove the render of a clip), re-render the clip only, and try to export with an I-O on that clip’s area again.

Not seeing your timeline makes it hard to even guess where the problem could be, so I’m using my imagination a little. Just trying to help.

[Mattias Molen]

SOLVED!

We cloned the 500GB FireWire disk with carbon copy cloner. Then reopened the project, reconnected media files and hit export. Still no luck. Then we tried export via Compressor and that worked.

Compressor exported the movie in under 15 minutes without any problems.

So we don’t know the exact problem but it had something to do with the disk.

I’m glad it’s all good now. Thanks everyone!