-
1) Does 10.0.0.6 force re-rendering of everything? 2) Can I pick scratch disk
1) I just upgraded to xxxx6 and it’s re-rendering a ton of stuff. I also proved brain-dead and, at first, some files were on unmounted external drives.
Is it because files were missing at first or is everyone finding xxxxxx6 re-renders everything?
2) Can I specify scratch disk?
I have a MBP Early 2011 / 2.Ghz/ i7 /8 GB
with two hard drives–Boot= 300GB SSD with 500GB 7200rpm in optical bay.Testing has shown editing is smoother with everything– app plus data– on the SSD rather than data on HD.
The SSD can sustain 200 Megs a second read/write, the HD only 100MB.
But I’ve also been told it’s not good to be constantly rewriting to SSD, like with render files.
Any ideas how to handle?
Thanks
-
1 Reply
-
There is no “scratch” disk. FCP X addresses one of the biggest concerns of FCP 7, that scratch disk settings were not attributed to projects, by making renders always within the project. The project is actually a directory where versions, renders, and all data required for the project is stored. So if you’re putting your project on your computers program drive, then that’s where the renders will be.
And sure, it probably does perform better. It’s an SSD. But you’re gonna eat up space pretty quick.
10.0.6 does seem to negate most of the renders for my previous projects. The only renders it kept were color grading. If the only effect on a clip was color grading, then it didn’t become unrendered.
If you’re not putting your projects & events on an external, I would turn off background rendering for sure. I’d do it anyway.
Reply to this Discussion! Login or Sign Up