Jackson Childs
Forum Replies Created
-
That’s great. Too bad I didn’t have money to buy that and then they discontinued that architecture 🙂 I feel kind of SOL right now.
-
I really don’t know! I’ve never figured this out. In my case I was trying to export 20+ minutes and it would crash FCP to have to do all that rendering at once. In my experience the re-render takes about as long as rendering it in the first place. It seems like for certain renders the re-render is standard. Smoothcam for instance is very finicky and so a variety of actions on the timeline (rendering something else for instance) will un-render those clips. Don’t know why. But so having it take 30 minutes for 1-2 minutes seems odd unless that’s how long it initially took to render. One thing that I’ve done is to take individual clips from the timeline and drop them in the browser, than export those. When you re-import whatever that was as a quicktime clip, no more rendering is necessary (unless you do some more filtering on it then). There may be some very marginal loss in image quality from doing this I don’t know. That can make it easier to work with problematic timelines, particularly stuff you’ve brought over from motion. Of course then you can’t go back and forth between programs (which is dicey anyway because Motion is unstable but you have to do it sometimes!).
-
The two strategies were suggested as general troubleshooting, not as related to each other.
-
Ok, no one’s reading this now but maybe it will help someone later on! I’m just guessing but is it possible the render problem comes up because the smooth cam clips were all rendered on a separate time line? Smoothcam is a rather mysterious filter and so for instance if you render one smooth cam clip on a timeline with other, unrelated smooth cam clips, those others are often then unrendered. So what I (and others) do is take individual clips and render them on a separate time line. Then you don’t have to re-render other clips (unless they are linked to bits of material on the timeline where you rendered!). But so maybe this creates a problem when you try to export the whole rendered timeline. Maybe you have to render everything together on the timeline, otherwise Final Cut will force you to do that when you try to export the whole timeline. I’m grasping at straws here! I wish I could find out because troubleshooting with an 86 minute timeline is a gigantic headache involving day-long renders!
-
Ok, I repaired permissions and couldn’t find any corrupt clips. I realize now that the clips that become unrendered when I try to export are all smoothcam clips. So something about those clips is causing a problem when trying to export. I’ll have to do more research on it but it doesn’t look good.
-
self-contained movie at cuurent settings.
-
Yeah, I don’t want to export unrendered cause that doesn’t work currently, and any way would probably take a day at least. So yes, I have rendered everything and then if I attempt to export: 75% is now unrendered. So I want to know specifically why that is happening. Are you suggesting it is doing that because of the permissions, or because clips are corrupt and will render fine but when you export they de-link or go missing? If so great I will try to fix those things. I’m pretty ignorant about this stuff.
-
Hi John, thanks for your help. That maintenance pack looks very helpful. However I’m still wondering why my rendered timeline is unrendered when I try to export a quicktime movie. Is that normal? I’m assuming that if the timeline isn’t rendered the export will take far longer than it would if it was rendered, which makes isolating the problem in the way you describe very time consuming.