-
All replies
-
Helpful answers
-
Aug 28, 2011 8:18 AM in response to blimpmediaby Dirk Williams,The only other external drive I have, is a raid. But I'll test that one anyway…
Here is something weird I found that might solve the problem. When you close FCX, make sure you do not have the project you've just worked on that has any effects added to it open. Make a 5 second dummy project, and open that one before shutting down. I think what is happening is that the last project that was opened, loses it's rendering. I'll need to check that everyday for a few days. So far my method worked this morning. When I booted FCX, the dummy project showed up in the timeline. Then I went and clicked on the projected that has a lot of effects, and it was fine.
-
Aug 28, 2011 4:18 PM in response to Dirk Williamsby blimpmedia,Dirk,
Excellent workaround (for now). Be sure to send feedback so we can try get this fixed.
-
Aug 31, 2011 6:41 PM in response to blimpmediaby Dirk Williams,So far I've been using my method for awhile and it works. Has anybody else had any sucsess with this workaround?
-
Nov 2, 2011 10:03 AM in response to Dirk Williamsby Mark Terry3,Dirk, has this still been working for you? I'm sitting here watching FCP X re-render a 1.5 hour video yet again.
I'd love to hear that this work around still works.
-
Nov 2, 2011 2:30 PM in response to Mark Terry3by Dirk_Williams,Hey Mark, yes and no. 1 out of the 6 projects I have going on in FCP X, it had to re-render. It was something that I did some resizing to. The other five were fine and held their render. I have not heard too much from anyone else on this issue. I don't think a lot of Pros are using FCP X.
-
Jan 10, 2012 4:12 PM in response to Dirk Williamsby TRC1,I'm having the same issue at times but it seems random. Some days I boot up, open FCPX and nothing has to be re-rendered, and other days a full hour or more of re-render time is required.....usually it's just small clips but nerve racking when working under a deadline and you think you are done to say the least.
I'm not using raids, just firewire drives that are not disconnected when shutting down. This happened a few times when I was NOT copying media to the events folder, just referencing it from the original location.
More recently it happened in a project where I used the "copy the media to the event folder" option, however it happened after simply opening another project in the timeline, then going back to the original project in the timeline. Nothing was changed in either project while open and FCP was never shut down.
Trashing prefs seems to help with slowdown issues but doesn't have any effect on this. From my experience it seems fairly random.
Any updates on this would be appreciated.
-
Jan 10, 2012 8:40 PM in response to TRC1by burningarms,I've had this issue as well. Stopped using FCPX for the time being, so can't comment too thoroughly, but here's what I've found… It seems that if rendering was the very last thing you did before shutting FCPX down, you will lose the connection to the render files. Probably just a database write issue. The workaround I found was, after you've rendered your project, make a small change like adding a clip then deleting it again. If you close FCPX now, then reopen, you should be fine. No dummy project switching needed.
I've tested this a few times and seemed consistent on my setup. Sent a bug report to Apple about it with this info already.