| ||||||||||
| Hi, I always work with tiff sequences because we have a render farm, and unfortunately there's always that extra step of converting them into a quicktime for playback with audio, which always seems to be SUPER URGENT because the producer needs it NOW! If you want to work in an editing package, or play back with audio then you'll need to render to quicktime for best performance - especially if you're working with uncompressed or 16 bit tiffs. There's no real way around that, even jpg sequences can get a bit choppy if the resolution is high enough. I started a thread a few months ago trying to find the fastest way to convert an image sequence to a quicktime, and oddly enough I discovered that most of the time After Effects with multi-processing on is the quickest. FFmpeg, which is free but requires some basic command-line knowledge, can be faster on long image sequences and has the advantage of doing a great h264 compression. Our render farm (deadline) can automatically start an FFmpeg compression when an image sequence has finished rendering. I was working on an image sequence that was over 50,000 frames long and have never had any issues with directories, OS X or the SAN. I have had issues with file paths being longer than 256 characters, but I've never had any technical issues related to the number of files in a directory. Quicktime 7 is very slow to open image sequences - when you get a really long sequence it can take longer just to open the sequence in quicktime 7 than it does to render it out in AE - that's before you even begin exporting. Compressor is better but there's still that initial delay - I assume it's counting frames and checking they're all there or something. So basically - if you want real-time playblack then you'll have to go to quicktime first, and while ffmpeg is free but it's a bit of a handful if you're not used to it, but After Effects with multi-processing on is a good option. -Chris On 01/06/2012, at 4:18 AM, adam mercado wrote:
|
