-
All replies
-
Helpful answers
-
Aug 24, 2011 8:35 AM in response to Dirk Williamsby BenB,It's losing track of render files somewhere. Doesn't seem to be universal bug, but report it to Apple (feedback page) anyway. If you're not changing anything at all, not unmounting drives or anything, try trashing pref files, which fixes many bugs. (Preference Manager from Digital Rebellion, free)
-
Aug 24, 2011 9:02 AM in response to BenBby hafken,if that doesn't work, try deleting all render files within the FCPX interface for both the project and events that are involved.
-
Aug 24, 2011 12:02 PM in response to BenBby Dirk Williams,I unmount my CalDigit Raid before I turn my Mac Pro off for the night. I make sure I quit FCX before turring everything off. Both the project and events sit on the Raid drive. Do you see any problems in what I'm doing?
NOTE: Please don't tell me to never shut down my system at night. I live in the middle of the desert, and it gets too hot in the house to leave it on all night... thanks ;-)
-
Aug 24, 2011 12:26 PM in response to Dirk Williamsby James Cude,Are you saying things continue to need rendering as you work or a brand new restart of the program when the last time you made a move that was totally rendered has become unrendered. It will keep rendering along as you work, that's 'background rendering.' As long as you make changes that need to be rendered, things will continue to need to be rendered. Also can you say more about your project? What sort of footage and resolution are you working with?
-
Aug 24, 2011 12:58 PM in response to James Cudeby Dirk Williams,Everything is done rendering before I quit the program. The next day I boot the program and everything that was rendered yesterday, has to be re-rendered. So yes, everything becomes un-rendered. But I don't have to re-render stuff that has been rendered during the time while I'm working on the project.
It just a short 3 minute project. The footage is ProRes 422.
NOTE: FCX don't not do true "background rendering". You have to stop working before it starts rendering again. The term "background rendering" is misleading… but that's for another discussion.
-
Aug 24, 2011 5:04 PM in response to Dirk Williamsby blimpmedia,★HelpfulGuys I'd like to also confess that I too have the same problem as Dirk.
I work of a 2011 MacBook Pro (running 10.6.8) with a CalDigit VR attached, if I Quit FCP X, eject the CalDigit, Power everything down, then power everything back up again and open my last project (which was totally rendered), everything needs to be re-rendered again.
For the time been what I've been doing is splitting my project in section, after completing/rendering, I export the storyline to a master ProRes 422 QuickTime file.
I've tried all the obvious things, trashing prefs, deleting renders, HD permissions etc... I found non of those to make a diferance.
Dirk, I strongly suggest if you haven't finished your edit, leave your system running till you do, then export to a ProRes.
I know it's annyoyng, but we really don't have a choice right now.
-
Aug 24, 2011 6:05 PM in response to blimpmediaby Dirk Williams,I don't feel so alone now... FCX does not support external monitoring. I knew that going in. But now we find out, it does not support external raid units. You know what they say: "Fool me once, shame on you. Fool me twice, shame on me."
-
Aug 25, 2011 6:56 AM in response to Dirk Williamsby hafken,So are we putting the cause of this problem down to using external RAID as a host for Events/Projects?
Is the original media inside the Event as well, or is it referenced elsewhere?
-
Aug 25, 2011 7:05 AM in response to hafkenby Dirk Williams,It looks that way. I'd like to confirm this with a few others. Maybe there is not enough people out there yet that are using FCX with an external RAID.
Yes, the original media is inside the Event. It is not referenced elsewhere.
-
Aug 25, 2011 7:47 AM in response to Dirk Williamsby blimpmedia,Interesting Dirk, I on the other hand don't copy the original media to the event, instead I reference, but on the other hand I have FCP X transcode optimize media on import.
Do you have your CalDigit connected via a eSata connection or FW800?
-
Aug 25, 2011 8:27 AM in response to blimpmediaby Dirk Williams,eSATA. I'll have to try the not copying the original media to the event method.
The project that won't keep the render was imported having FCP X transcode the media.
-
Aug 26, 2011 5:11 PM in response to Dirk Williamsby James Cude,Interesting- more details please. It'd be nice to know if this is due to files living on a particular type of external drive.
-
Aug 26, 2011 7:10 PM in response to James Cudeby Dirk Williams,A 3TB CalDigit VR connected via eSATA to a Mac Pro. Not much more I can tell you...
-
Aug 28, 2011 4:02 AM in response to Dirk Williamsby blimpmedia,I'm running FCP X on a 2.3GHz Quad-core Intel Core i7 MacBook Pro with 8 GB Ram, and running OSX 10.6.8.
For storage I use a 4 TB CalDigit VR enclosure and connect it to my MacBook Pro via the FASTA-1ex SATA ExpressCard (Driver FASTA-1ex v.1.1.6).
I tested the enclosure via the FW 800 and eSATA connection, and found if the media lives on the CalDigit VR enclosure, the render files disappear once you eject and turned off the drive.
As a test, I threw some media on a Western Digital My Passport Studio Portable External Hard Drive, added a few clips, rendered and ejected the drive. After re-starting and opening the project, all the render was still in tact.
It appears renders are only being lost when using RAID.
Can you guys test this as well?