Return-Path: Received: from mail-qy0-f169.google.com ([209.85.216.169] verified) by media-motion.tv (CommuniGate Pro SMTP 4.2.10) with ESMTP-TLS id 4635603 for AE-List@media-motion.tv; Thu, 23 Feb 2012 18:41:20 +0100 Received: by qcsd16 with SMTP id d16so13803qcs.28 for ; Thu, 23 Feb 2012 09:47:50 -0800 (PST) Received-SPF: pass (google.com: domain of phil@bonfirelabs.com designates 10.229.137.20 as permitted sender) client-ip=10.229.137.20; Authentication-Results: mr.google.com; spf=pass (google.com: domain of phil@bonfirelabs.com designates 10.229.137.20 as permitted sender) smtp.mail=phil@bonfirelabs.com Received: from mr.google.com ([10.229.137.20]) by 10.229.137.20 with SMTP id u20mr1720359qct.64.1330019270831 (num_hops = 1); Thu, 23 Feb 2012 09:47:50 -0800 (PST) Received: by 10.229.137.20 with SMTP id u20mr1468405qct.64.1330019270453; Thu, 23 Feb 2012 09:47:50 -0800 (PST) Return-Path: Received: from [10.0.0.132] ([65.223.58.66]) by mx.google.com with ESMTPS id ef6sm5483638qab.7.2012.02.23.09.47.46 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 23 Feb 2012 09:47:48 -0800 (PST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Apple Message framework v1084) Subject: Re: [AE] Fastest way to render image sequence as mov From: Phil Spitler In-Reply-To: Date: Thu, 23 Feb 2012 09:47:44 -0800 Content-Transfer-Encoding: quoted-printable Message-Id: <49A10842-A140-4026-A196-573FEB2002B3@bonfirelabs.com> References: To: "After Effects Mail List" X-Mailer: Apple Mail (2.1084) X-Gm-Message-State: ALoCoQmFSVx5YajZN3wzeiHK99MqGXuF4ugyDRWTh4Ze509El1a0sg0OPZifFZ2QuNhDHXduX0WI I used to have an Apple Script that worked pretty well for compiling = image sequences, check around the Apple Script forums. I actually never render them any more from AE as they are such a pain to = re-compile, I render to multiple QT files, I have often rendered out 100 = QT files which may seem excessive but it gives the flexibility of an = image sequence but is much quicker to re-assamble. Phil Phil Spitler | Associate Creative Director | Bonfire Labs | t : = 415.394.8200 | c : 415.571.3139 | Bonfirelabs.com On Feb 23, 2012, at 8:43 AM, Evan Fotis wrote: > Didn't follow this thread from the beginning so perhaps this has been = addressed already but ..how about good ole mpeg streamclip? > i tried it and it takes image sequences. >=20 > On 23-Feb-12 10:35, Chris Zwar wrote: >> Well what an anticlimax! >>=20 >> Firstly I discovered that you need CS 5.5 in order to import an image = sequence into Adobe Media Encoder. We're on CS 5.0, so no luck there. >>=20 >> Then I discovered that whatever Adobe package is on my machine, it = doesn't include Premiere Pro. So no luck there. >>=20 >> Likewise it doesn't have Final Cut or Compressor, so no luck there. >>=20 >> I thought I'd try FFmpegX - the Mac gui front end to ffmpeg, but it = doesn't support image sequences either. I didn't have the time today to = figure out how to use ffmpeg from the command line, so I'll save that = for a rainy day. >>=20 >> Opening up the sequence in Quicktime Pro takes AGES, possibly longer = than the image sequence runs for anyway, and unless I stand there with a = stop watch there's no easy way to benchmark Quicktime Pro, as you'd have = to include the incredibly long time it takes to open the sequence before = you can begin exporting it. But in my case of opening a 20 minute = 1920x1080 image sequence, it took about 30 minutes just to open the = sequence, which is a very long time to wait before you can even begin to = export it... I don't know how long it took to actually export, as again = you'd need a stopwatch to measure it accurately. But it definitely = wasn't faster than real-time... >>=20 >> Inside AE CS5.0, with multiprocessors on and AE utilising 6 of them, = the image sequence begins to render very quickly. Initially AE predicts = a total rendering time of 30 minutes (for a 20 minute video). This is = looking pretty good until about 1/3 of the way through, and then AE = begins to slow down. And then it slows down more. The further through = the render it gets, the slower it renders. Eventually it finishes in 62 = minutes. But I'd guess that it took about 30 minutes to render the = first 80%, and another 30 minutes to render the last 20%. This is on a = freshly booted 8-core machine with no other apps running, 16GB ram. >>=20 >> I said in my original post that converting image sequences to = quikcktime is not one of AE's strengths. But I may have been wrong, = because so far it's the best I've got! >>=20 >>=20 >> -Chris >>=20 >> On 23/02/2012, at 4:23 AM, Phil Spitler wrote: >>=20 >>> I will be interested in seeing your results from the ffmpeg test. >>>=20 >>> Great tip, thanks Lloyd. >>>=20 >>> Phil >>>=20 >>>=20 >>> Phil Spitler | Associate Creative Director | Bonfire Labs | t = : 415.394.8200 | c : 415.571.3139 | Bonfirelabs.com >>>=20 >>> On Feb 22, 2012, at 3:46 AM, Chris Zwar wrote: >>>=20 >>>> Thanks all... I have completely overlooked Adobe Media Encoder. = I've installed FFmpeg and will benchmark them both this week. >>>> I do normally just use Quicktime Pro and have several encodes = running simultaneously, however when I have to encode a single 20 minute = image sequence into a H264 as fast as possible I'd like to know what the = best solution is. >>>>=20 >>>> I'll let you know what I discover... >>>>=20 >>>>=20 >>>> -Chris >>>>=20 >>>> On 22/02/2012, at 11:31 AM, Steve Oakley wrote: >>>>=20 >>>>> adobe media encoder... or prem pro as it supports img sequences. = load as clip, export. >>>>>=20 >>>>> s >>>>>=20 >>>>> On Feb 21, 2012, at 5:05 PM, Jim Curtis wrote: >>>>>=20 >>>>>> You can do multiple simultaneous exports with QT Pro, and max out = your multi-core pretty quickly. >>>>>>=20 >>>>>>=20 >>>>>> On Feb 21, 2012, at 5:02 PM, Chris Zwar wrote: >>>>>>=20 >>>>>>> Hi, >>>>>>>=20 >>>>>>> Just looking for some advice as to the fastest way to convert an = image sequence to a quicktime? This isn't one of AE's strengths. >>>>>>> Usually I'm happy with Quicktime Pro, but I'm currently working = on a 20minute video at 1920x1080 and any speed increases will be = valuable. Because we have a render farm everything is based on image = sequences - currently we're using JPGs at max quality. >>>>>>> I'm on a Mac, and usually rendering to h264. >>>>>>>=20 >>>>>>> Cheers, >>>>>>>=20 >>>>>>> -Chris >>>>>>>=20 >>>>>>>=20 >>>>>>>=20 >>>>>>> +---End of message---+ >>>>>>> To unsubscribe send any message to >>>>>>=20 >>>>>> +---End of message---+ >>>>>> To unsubscribe send any message to >>>>>=20 >>>>> +---End of message---+ >>>>> To unsubscribe send any message to >>>>>=20 >>>>=20 >>>> +---End of message---+ >>>> To unsubscribe send any message to >>>=20 >>> +---End of message---+ >>> To unsubscribe send any message to >>>=20 >>=20 >> +---End of message---+ >> To unsubscribe send any message to >>=20 >=20 > +---End of message---+ > To unsubscribe send any message to