Return-Path: Received: from [207.46.163.143] (HELO na01-bn1-obe.outbound.protection.outlook.com) by media-motion.tv (CommuniGate Pro SMTP 4.2.10) with ESMTP-TLS id 5452310 for AE-List@media-motion.tv; Thu, 24 Apr 2014 16:32:18 +0200 Received: from CO1PR06MB265.namprd06.prod.outlook.com (10.141.71.15) by CO1PR06MB265.namprd06.prod.outlook.com (10.141.71.15) with Microsoft SMTP Server (TLS) id 15.0.929.12; Thu, 24 Apr 2014 14:32:13 +0000 Received: from CO1PR06MB265.namprd06.prod.outlook.com ([169.254.7.233]) by CO1PR06MB265.namprd06.prod.outlook.com ([169.254.7.233]) with mapi id 15.00.0929.001; Thu, 24 Apr 2014 14:32:13 +0000 From: Stephen van Vuuren To: After Effects Mail List Subject: RE: [AE] Rendering Direct to QuickTime MOV vs rendering out to image sequence first & RAM vs Render to file Thread-Topic: [AE] Rendering Direct to QuickTime MOV vs rendering out to image sequence first & RAM vs Render to file Thread-Index: AQHPX53wiNfpIo25rEOuB0exhl8v9Zsg0WFw Date: Thu, 24 Apr 2014 14:32:12 +0000 Message-ID: <78834d962ae14a768c3c0d59de79d050@CO1PR06MB265.namprd06.prod.outlook.com> References: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [24.163.5.74] x-forefront-prvs: 01917B1794 x-forefront-antispam-report: SFV:NSPM;SFS:(10019001)(428001)(189002)(199002)(377454003)(50986999)(76176999)(15202345003)(20776003)(87936001)(15975445006)(74316001)(16236675002)(2656002)(76482001)(54356999)(76576001)(33646001)(79102001)(19300405004)(46102001)(4396001)(81542001)(85852003)(92566001)(83072002)(86362001)(80022001)(80976001)(31966008)(99286001)(81342001)(74502001)(66066001)(77982001)(19580405001)(83322001)(19580395003)(74662001)(99396002)(24736002);DIR:OUT;SFP:1102;SCL:1;SRVR:CO1PR06MB265;H:CO1PR06MB265.namprd06.prod.outlook.com;FPR:A60AC515.A1D10D00.76F3BFAA.4E2E8DD.20255;MLV:sfv;PTR:InfoNoRecords;MX:1;A:1;LANG:en; received-spf: None (: sv2studios.com does not designate permitted sender hosts) Content-Type: multipart/alternative; boundary="_000_78834d962ae14a768c3c0d59de79d050CO1PR06MB265namprd06pro_" MIME-Version: 1.0 X-OriginatorOrg: sv2studios.com --_000_78834d962ae14a768c3c0d59de79d050CO1PR06MB265namprd06pro_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable AE renders as opposed to RAM previews often need help of a component or int= ermediary. I recently found out the QuickTime server for renders is 32-bit,= not 64-bit and I've found QuickTime renders the most unstable of a couple = of my boxes. Image sequence renders are usually direct from AE depending on= format and the most stable. stephen van vuuren 336.202.4777 http://www.insaturnsrings.com/ http://www.sv2dcp.com/ http://www.sv2studios.com/ A film is - or should be - more like music than like fiction. It should be = a progression of moods and feelings. The theme, what's behind the emotion, = the meaning, all that comes later. -Stanley Kubrick From: After Effects Mail List [mailto:AE-List@media-motion.tv] On Behalf Of= Anders Sundstedt Sent: Thursday, April 24, 2014 5:17 AM To: After Effects Mail List Subject: [AE] Rendering Direct to QuickTime MOV vs rendering out to image s= equence first & RAM vs Render to file Hi, How come when rendering a project directly to QuickTime .MOV it can often f= ail/stop during render, while if first rendering out to an image sequence (= TGA) and then rendering that to QuickTime .MOV it usually works? Same with RAM preview vs image sequence rendering. How come it often works = fine to do a RAM preview at 100% quality while when rendering out the same = sequence to image files it can often fail at a certain frame/frames that wo= rked fine in RAM preview? Thanks Anders Sundstedt --_000_78834d962ae14a768c3c0d59de79d050CO1PR06MB265namprd06pro_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

AE renders as opposed to = RAM previews often need help of a component or intermediary. I recently fou= nd out the QuickTime server for renders is 32-bit, not 64-bit and I’ve found QuickTime renders the most unstable of a couple of my= boxes. Image sequence renders are usually direct from AE depending on form= at and the most stable.

<= /p>

stephen van vuuren

336.202.4777

http://www.insaturnsrings.c= om/

http://www.sv2dcp.com/

http://www.sv2studios.com/

A film is – or s= hould be – more like music than like fiction. It should be a progress= ion of moods and feelings. The theme, what’s behind the emotion, the meaning, all that comes later.

–Stanley Kubrick=

<= /p>

From: After = Effects Mail List [mailto:AE-List@media-motion.tv] On Behalf Of Anders Sundstedt
Sent: Thursday, April 24, 2014 5:17 AM
To: After Effects Mail List
Subject: [AE] Rendering Direct to QuickTime MOV vs rendering out to = image sequence first & RAM vs Render to file

Hi,

How come when rendering a project directly t= o QuickTime .MOV it can often fail/stop during render, while if first rende= ring out to an image sequence (TGA) and then rendering that to QuickTime .MOV it usually works?

Same with RAM preview vs image sequence rend= ering. How come it often works fine to do a RAM preview at 100% quality whi= le when rendering out the same sequence to image files it can often fail at a certain frame/frames that worked fine in RAM preview?<= o:p>

Thanks

Anders Sundstedt

--_000_78834d962ae14a768c3c0d59de79d050CO1PR06MB265namprd06pro_--