FCP Un-Renders!
 

After I export (when using QT Conversion) the timeline seems to revert to being unrendered!!! Why would this happen?

I had exactly the same thing happen during the week when using QuickTime conversion to export a still image. It took over 20 minutes to re-render the sequence. Perhaps it only happens with QuickTime conversion? I've had no problems exporting as a QuickTime movie or exporting using Compressor.

I've no idea why it happens, but my current "workaround" to protect my renders (if I needed to use QuickTime conversion again) would be:

1/ Copy the sequence in the Browser (Command C) and then paste in the Browser (Command V). (And perhaps give the copied sequence a different name.)
2/ Double-click the copied sequence in the Browser to open it in the Timeline.
3/ Export using QuickTime conversion from the copied sequence and lose the renders in the copied sequence (and thus protecting your renders in the original sequence).
4/ When done, go to the Browser and delete the copied sequence.

Does anyone else have any ideas? This seems like a major problem, or is it only happening to a small few??

It would help to know the environment you're in: What version FCP and QT?

Hi Robert!
I am running the latest (I think): FCP = 6.0.4 and QT 7.5. I think I actually figured out the issue... I was in an HDV 1080i60 timeline, but I had changed the sequence settings so that the render controls were using ProRes422 instead of HDV. It was with these settings that I was experiencing the problem.

I then set the sequence video encoder to ALSO be ProRess422 and then re-rendered and then re-exported (QT conversion) and my render stayed in tact! Maybe you can confirm or deny this for me, but I think that if your sequence video encoder settings don't match your render encoder settings, than a QT CONVERSION (not QT movie or Compressor export) will make your sequence un-rendered. Sorry that was a rambling mouthful!
-Steve

I was using FCP 6.0.4, QT 7.5, native HDV720p25 sequence with the rendering set to ProRes 422.

It looks like you nailed it, Steve.