-
FCP 7.0.3 export problem
Having problems exporting 90-minute doc through “share” or compressor. Audio is fine; export fails in making mpeg 2, sometimes as long as 45 minutes into the encoding. I get a QT error 0 message.
This is not a new problem, and i have successfully employed the workaround of exporting self-contained QT and putting that through Compressor. BUT….I would rather not have corrupted files in my timeline, if that is indeed the issue. This project has a lot of still photos and archival video from many different sources and I want a fully functional timeline as we head into post production. Last time this happened on this project, we used Digital Rebellion corrupt clip finder to identify problem files, and that did the trick. This time around, it doesn’t find any such files in the timeline.
So, I’ve decided I must run exports on the timeline in chunks to try to narrow down the problem to one scene, and then narrow it down within that scene to find the problem clip. Very time consuming.
Questions:
Does this sound like it will work?
Is there a more efficient way to do figure out what the problem is?Thanks in advance, COW community!
Regards,
DavidMac Pro 2 x 2.66 GHz Quad Core Intel Xeon; 8 GB DDR3; OS X Lion 10.7.4; FCS3.
-
9 Replies
-
I would use episode to do the job.
Rainer
-
hmmmm not familiar with it but it looks like an encoding program. does it have a function to indentify bad clips?
Mac Pro 2 x 2.66 GHz Quad-Core INtel Xeon; OS X Lion 10.7.4; FCS 3.
-
It is the best encoding program we work with. I don’t know about bad clips. If Digital rebellion can’t repair them, I don’t know. Through digital rebellion you can also repair Compressor. Perhaps your clips aren’t bad and it is just Compressor.
i would make a mov in the original codec you work with and then go with episode.good luck
Rainer
-
[David Lewis] “So, I’ve decided I must run exports on the timeline in chunks to try to narrow down the problem to one scene, and then narrow it down within that scene to find the problem clip. Very time consuming.
Questions:
Does this sound like it will work?”
That is the traditional method to search corrupted files and works great, but instead of exporting by chunks, try just rendering the time-line by chunks (then you should be able to exporting the whole movie at once).
If you are able to render the full time-line, that means that there are not files corruption issues and the problem is somewhere else.
rafael -
thanks rafael. it has been fully rendered, but i can’t think of what else the problem might be or how to go about figuring it out. any thoughts?
Mac Pro 2 x 2.66 GHz Quad-Core INtel Xeon; OS X Lion 10.7.4; FCS 3.
-
David,
When FC starts to make glitches without any apparent reason is time for a bit of maintennance.
I would start by repairing permissions,if that doesn´t helps, then trashing FC preferences, and if the issue still doesn´t get fixed, I would run DiskWarrior.
rafael -
yeah i’ve come to the same conclusion. did permissions a few days ago, and that didn’t work. ran test exports on several small sections of the sequence today to try to identify problem clips, and the results made no sense. some failed immediately on start and then ran all the way through when i clicked “submit” again! tommorow will be time to do a full reinstall. i will be back if that doesn’t work. thanks!
Mac Pro 2 x 2.66 GHz Quad-Core INtel Xeon; OS X Lion 10.7.4; FCS 3.
-
well, did the full reinstall, still won’t export to mpeg 2 via compressor. frustrated and at a loss for what to do next. apple, of course, will provide no support.
Mac Pro 2 x 2.66 GHz Quad-Core INtel Xeon; OS X Lion 10.7.4; FCS 3.
-
here is what the error log looks like:
<?xml version=”1.0″ encoding=”UTF-8″ standalone=”yes”?>
Mac Pro 2 x 2.66 GHz Quad-Core INtel Xeon; OS X Lion 10.7.4; FCS 3.
Reply to this Discussion! Login or Sign Up