Return-Path: Received: from omr16.networksolutionsemail.com ([205.178.146.66] verified) by media-motion.tv (CommuniGate Pro SMTP 4.2.10) with ESMTP-TLS id 4731084 for AE-List@media-motion.tv; Fri, 01 Jun 2012 00:52:33 +0200 Received: from cm-omr1 (mail.networksolutionsemail.com [205.178.146.50]) by omr16.networksolutionsemail.com (8.13.8/8.13.8) with ESMTP id q4VMsoQY010735 for ; Thu, 31 May 2012 18:54:50 -0400 Authentication-Results: cm-omr1 smtp.user=chris@chriszwar.com; auth=pass (PLAIN) X-Authenticated-UID: chris@chriszwar.com Received: from [122.150.240.225] ([122.150.240.225:49231] helo=[192.168.0.5]) by cm-omr1 (envelope-from ) (ecelerity 2.2.2.41 r(31179/31189)) with ESMTPA id B5/23-06474-9B6F7CF4; Thu, 31 May 2012 18:54:50 -0400 From: Chris Zwar Mime-Version: 1.0 (Apple Message framework v1084) Content-Type: multipart/alternative; boundary=Apple-Mail-1--579565453 Subject: Re: [AE] [OT] Working with still sequences Date: Fri, 1 Jun 2012 08:54:47 +1000 In-Reply-To: To: "After Effects Mail List" References: Message-Id: X-Mailer: Apple Mail (2.1084) --Apple-Mail-1--579565453 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=iso-8859-1 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: > 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. >=20 > 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. >=20 > Adam Mercado > Influxx Media Production > Fullerton, CA >=20 > Moving Images. For Business > 714=B0928=B09896 > http://www.influxx.com > http://www.twitter.com/influxx > http://www.linkedin.com/in/influxx > http://influxx.tumblr.com/archive > http://www.flickr.com/photos/influxx >=20 >=20 >=20 >=20 >=20 --Apple-Mail-1--579565453 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=iso-8859-1
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=B0928=B09896




=


= --Apple-Mail-1--579565453--