Terry
Forum Replies Created
-
I just finished an 80 min project that was almost entirely made up of 4000×4000 stills… with complex moves and sometimes 5 layers (all stills). After much deliberation I ended up using Stage Tools Moving Picture Producer (with FCPHD 4.5 ram HUGE 800 U320r). I tried it first as a plug-in, but with the high res stills, it proved unusable as it brought my system down to a slow crawl. Producer looks just like the plug-in however it is a stand-alone application. I would create my moves and then export a QT movie to FCP, which would then allow me to further tweak the look (color correction, filters etc.) without bogging down the system memory cache when working directly with a still. The one flaw is that there is no way to import a scratch audio track for timing in Moving Picture Producer (windows version allows this). So if timing is critical, one has to flip between FCP and MPP and take accurate timecode notes (MMP utilizes timecode). The time it took to render out a QT movie (10 bit uncompressed corresponds almost directly with the length of the movie so 2 mins length = 2 mins render roughly) and then importing into FCP was miniscule compared to rendering out the same move within the plug-in version of FCP.
-
I’m in a similar quandry… The show is 80 minutes and 99% are QT movies made from still images output from Moving Picture Producer. The only original footage are the still files without the ‘moves’. I’ve got some 250 GB of QT to archive! Perhaps I should just dump it to tape or maybe there is a cheap firewire drive that I buy and then just forget about using again… hmm.
-
Even after the re-render in high yuv — still doing it… The only way around it is to match the source file frame, freeze it and apply attributes from the sequenced clip. This is very strange – I’ve never come across this before.
-
It does it on every clip – sometimes very obviously – sometimes not. I was able to get around it by matching the frame with the original source clip, freezing it, then applying attributes from my sequence clip. Now, what I discovered after the fact was that the sequence setting was in RGB render mode — I re-rendered it in YUV high and will now see what happens when I try the freeze.