Return-Path: Received: from dub0-omc4-s18.dub0.hotmail.com ([157.55.2.93] verified) by media-motion.tv (CommuniGate Pro SMTP 4.2.10) with ESMTP id 5463479 for AE-List@media-motion.tv; Mon, 05 May 2014 21:24:19 +0200 Received: from DUB128-DS7 ([157.55.2.71]) by dub0-omc4-s18.dub0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675); Mon, 5 May 2014 12:24:18 -0700 X-TMN: [x8P/cIqPuPVdvDQPtaIAzd+zJbLr8Kyi] X-Originating-Email: [anders@sundstedt.co.uk] Message-ID: Return-Path: anders@sundstedt.co.uk From: Anders Sundstedt To: "After Effects Mail List" References: In-Reply-To: Subject: Re: [AE] Rendering Direct to QuickTime MOV vs rendering out to image sequence first & RAM vs Render to file Date: Mon, 5 May 2014 20:24:16 +0100 Organization: Sundstedt Animation MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0028_01CF689F.FCAEDA00" X-Priority: 3 X-MSMail-Priority: Normal Importance: Normal X-Mailer: Microsoft Windows Live Mail 16.4.3528.331 X-MimeOLE: Produced By Microsoft MimeOLE V16.4.3528.331 X-OriginalArrivalTime: 05 May 2014 19:24:18.0748 (UTC) FILETIME=[9C3ABFC0:01CF6897] ------=_NextPart_000_0028_01CF689F.FCAEDA00 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hi Chris, Sorry for the delay. From what I can remember now, I think it was an = =E2=80=9Coutput module=E2=80=9D fail/error. Thanks Anders From: Chris Zwar=20 Sent: Thursday, April 24, 2014 2:07 PM To: After Effects Mail List=20 Subject: Re: [AE] Rendering Direct to QuickTime MOV vs rendering out to = image sequence first & RAM vs Render to file On 24/04/2014, at 7:16 PM, Anders Sundstedt = wrote: How come when rendering a project directly to QuickTime .MOV it can = often fail/stop during render, while if first rendering out to an image = sequence (TGA) and then rendering that to QuickTime .MOV it usually = works? Hi, What sort of fails are you getting? Are they specific to rendering = quicktimes or are they After Effects rendering fails? It's not hard to get rendering errors and fails but I can't think of = many that are limited to rendering to Quicktimes. The rendering process = and the output process are separate. I often run into problems with the = number of particles in Particular, for example, but that's a general = rendering error and it makes no difference if I'm rendering to a = Quicktime or image sequence. If you have motion blur cranked up too = high (e.g. > 360 degrees, I think you can go up to 720) then you can get = some pretty weird results and crashes but again, not limited to = quicktimes. And heaps of plugins can be quirky or unstable, especially = any that use Open GL. But again - not restricted to quicktimes. Prior = to CS5 there was always the risk of a memory buffer error, but since CS5 = in 2010 that hasn't been a problem and was just as much a problem with = image sequences as quicktimes.=20 If you are rendering to a network drive using CS 6 or earlier then you = will get a fail if the file size goes over 2.15 GB. It's a massive pain = in the **** but I believe it has been fixed in CC. Unfortunately I'm = still on CS6 and am used to rendering to the desktop and then copying = the finished quicktime to the network to avoid this stupid bug. You = won't have this problem rendering an image sequence to a network drive = because an individual frame will not be over 2 gig. The only other regular quicktime fail that I get is "After Effects = error: internal verification failure, sorry! {could not find itemframe = we just now checked in}". This only happens when using multiprocessing, = and I've only had it when doing a simple conversion of an image sequence = to a Quicktime. It's hugely frustrating because multiprocessing can = make things 5 - 6 times faster. It's a problem I've had at different = companies, on different computers, and it still happens in After Effects = CC. Massively annoying and I hope it is fixed soon. Are these the problems you're having or is it something else? Basically = - what sorts of error messages or problems are you getting?=20 -Chris ------=_NextPart_000_0028_01CF689F.FCAEDA00 Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: quoted-printable
Hi Chris,
 
Sorry for the delay. From what I can remember now, I think it was = an=20 =E2=80=9Coutput module=E2=80=9D fail/error.
 
Thanks
Anders
 
From: Chris Zwar
Sent: Thursday, April 24, 2014 2:07 PM
Subject: Re: [AE] Rendering Direct to QuickTime MOV vs = rendering out=20 to image sequence first & RAM vs Render to file
 
On 24/04/2014, at 7:16 PM, Anders Sundstedt <anders@sundstedt.co.uk> = wrote:
How come when rendering a project directly to QuickTime .MOV it = can often=20 fail/stop during render, while if first rendering out to an image = sequence=20 (TGA) and then rendering that to QuickTime .MOV it usually=20 works?
 
Hi,
 
What sort of fails are you getting?  Are they specific to = rendering=20 quicktimes or are they After Effects rendering fails?
 
It's not hard to get rendering errors and fails but I can't think = of many=20 that are limited to rendering to Quicktimes.  The rendering process = and the=20 output process are separate.  I often run into problems with the = number of=20 particles in Particular, for example, but that's a general rendering = error and=20 it makes no difference if I'm rendering to a Quicktime or image = sequence. =20 If you have motion blur cranked up too high (e.g. > 360 degrees, I = think you=20 can go up to 720) then you can get some pretty weird results and crashes = but=20 again, not limited to quicktimes.  And heaps of plugins can be = quirky or=20 unstable, especially any that use Open GL.  But again - not = restricted to=20 quicktimes.  Prior to CS5 there was always the risk of a memory = buffer=20 error, but since CS5 in 2010 that hasn't been a problem and was just as = much a=20 problem with image sequences as quicktimes.
 
If you are rendering to a network drive using CS 6 or earlier then = you will=20 get a fail if the file size goes over 2.15 GB.  It's a massive pain = in the=20 **** but I believe it has been fixed in CC.   Unfortunately = I'm still=20 on CS6 and am used to rendering to the desktop and then copying the = finished=20 quicktime to the network to avoid this stupid bug.  You won't have = this=20 problem rendering an image sequence to a network drive because an = individual=20 frame will not be over 2 gig.
 
The only other regular quicktime fail that I get is "After Effects = error:=20 internal verification failure, sorry! {could not find itemframe we just = now=20 checked in}".  This only happens when using multiprocessing, and = I've only=20 had it when doing a simple conversion of an image sequence to a = Quicktime. =20 It's hugely frustrating because multiprocessing can make things 5 - 6 = times=20 faster.  It's a problem I've had at different companies, on = different=20 computers, and it still happens in After Effects CC.  Massively = annoying=20 and I hope it is fixed soon.
 
Are these the problems you're having or is it something else?  = Basically - what sorts of error messages or problems are you getting? =
 
 
-Chris
 
 
 
 
------=_NextPart_000_0028_01CF689F.FCAEDA00--