|
|
We're interested to know what is going on here as well. We've actually inflicted damage to our san drives by rendering a reel of tiff files (around 30,000 to a folder) for a feature in preparation for a DCP. The tiffs are then ingested into a Fuze system for the DCP but creating the folders with so many files can be very problematic. We thought it was the san system under Metasan management, but maybe it's just an OSX hangover. Davinci writes the tiffs really, really fast, too, real time or better, so we think that could be an issue, too. We tried a render out of AE with this many files and did not seem to have the same issue.
On May 31, 2012, at 1:12 PM, Chris Meyer wrote: I don't know if that's still the case, but the Mac's file system used to really bog down when too many files were in one folder. A very long still image sequence was one such case. Short of re-exporting as a movie (which is what I would do), you could try breaking the sequence up into individual folders, and then append the shorter sequences together. Don't know if that would fix it, but that's what I would try, FWIW.
good luck - Chris
On May 31, 2012, at 12:18 PM, adam mercado wrote:
I have a 14 minute sequence exported as a TIFF sequence. Trying to compile this with the mastered audio and working with the still sequence is very very slow. Importing into QuickTime, FinalCut or Premier causes hugely excessive lag times as the program processes every frame.
Is there a way to optimise this process short of exporting a flattened QuickTime movie and deleting the TIFF framed afterwards, which would seem a little redundant after all. Adam Mercado Influxx Media Production Fullerton, CA
Moving Images. For Business 714°928°9896
|
|
