From: "Brendan Bolles" Received: from nail.lmi.net ([66.117.140.18] verified) by media-motion.tv (CommuniGate Pro SMTP 6.1.0) with ESMTPS id 6363428 for AE-List@media-motion.tv; Wed, 29 Nov 2017 02:29:16 +0100 Received: from [192.168.1.20] (unknown [12.42.42.62]) by nail.lmi.net (Postfix) with ESMTPA id EEB58E42F8 for ; Tue, 28 Nov 2017 17:32:56 -0800 (PST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Apple Message framework v1085) Subject: Re: [AE] New AE script- Rendergarden In-Reply-To: Date: Tue, 28 Nov 2017 17:32:38 -0800 Content-Transfer-Encoding: quoted-printable Message-Id: <0F6FB50B-6C07-40EA-8DCB-6B939DDFD678@fnordware.com> References: To: "After Effects Mail List" X-Mailer: Apple Mail (2.1085) On Nov 28, 2017, at 5:09 PM, robertw wrote: > As to whether it re-renders to stitch the segments together, I think = not. At least in my limited testing, i could find no visible difference = between the RG output and a direct AE output using ProResHQ and 4444. I = mean NO difference, even blown up 200%. Correct, the combining of movie segments does not involve re-encoding, = while the Post Render Actions do (since they usually are converting your = render to a different codec). If you see shifts in the Post Render Action movies, are you doing the = comparison in After Effects? ProRes movies often look different in = QuickTime player. And ProRes is a lossy YUV codec, so you expect at = least a small change from the original RGB. If there's something beyond that, send us some steps to reproduce and = maybe we can get to the bottom of it. Maybe the FFmpeg command line = could be altered. Brendan