From: "Chris Zwar" Received: from mail-pf1-f171.google.com ([209.85.210.171] verified) by media-motion.tv (CommuniGate Pro SMTP 6.1.0) with ESMTPS id 7136739 for AE-List@media-motion.tv; Mon, 20 Aug 2018 01:42:59 +0200 Received: by mail-pf1-f171.google.com with SMTP id p12-v6so5842338pfh.2 for ; Sun, 19 Aug 2018 16:52:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chriszwar-com.20150623.gappssmtp.com; s=20150623; h=from:mime-version:subject:date:references:to:in-reply-to:message-id; bh=/a+pQkiU/1R3xDo7yZNlclqFKmDl0HFeWuydxq1g8KY=; b=e1oLARh18bM1fTUG5tTAd4AomsAnZxIc2JzxARvrIjkLNw0qoI0rrQToLf2hHKWkvF sG16XtG6OFgBSivuPCmq1pwk1lrOdIAT8jd/64eqDzv/j3P38q34zDCrYAQa2kMNDwpI yZe213i9rcDZUz73hr6wPx5Jn/0UZE2G8/wzC+RFQ019EoSv6yTf+U+/8t+/xCPifSQV rH6HonYwA9hK0KlwSPKeMAGzTG153BNVQL/bZUY1GkXUfUZRVOXfi+y0MxNnsdBV/R4J XrcJFPltsGgOMhiFvQ02XgW8lFUdllSB63I7an7jMmJJVEzYiDnXHuc8xuNFOZduv7Yq LJhw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:mime-version:subject:date:references:to :in-reply-to:message-id; bh=/a+pQkiU/1R3xDo7yZNlclqFKmDl0HFeWuydxq1g8KY=; b=FWD4nYIpIGhJRw1TBPM0fwigZ3AJ0sFPBQxPjyAYJnKEOoUdbjuchrkvfw7T/sYbI6 hUq07TyI4fv65abTU335nDEUivL3ipkYh/5X92MUhs0glCjnMgFIesFXj8QkrK4lVIiv 6AX2iQr0VlkG+gc7XdhJcKIxNzFyojwVNL0iPVmwTfq8zNDOOwDRY8S5VXoUdE7FQDW8 0ez+rjbSrwvZ00AVpb5SRfyFzuR0tDf4ZZe+JE8fHiRVugiz2rcwi6LV40U14WtnX8eM 2vvwrG+CmBiJCUHUPSYw5KQD6A/HRVYRS8ZM46+5BzuUR9nskEPr8/wYz+wgDi7aQku3 D0Aw== X-Gm-Message-State: AOUpUlEge5oorqKfi0U4eQ9cvBV0X6i0EbLmhtrhJumMSHOozUPz4URE F6Y9KZQj7PEjjHGjDvSviNFgX+o4Zho= X-Google-Smtp-Source: AA+uWPyk/R13qyKnOM7fQ//0mJsnMVCO5c4r/8A18WfH9CCXAI3EYw5FJlLGsyVnhusYJwY1sOQyPg== X-Received: by 2002:a63:25c6:: with SMTP id l189-v6mr1770755pgl.159.1534722764848; Sun, 19 Aug 2018 16:52:44 -0700 (PDT) Return-Path: Received: from [192.168.0.4] ([101.164.85.130]) by smtp.gmail.com with ESMTPSA id y18-v6sm9361246pfl.90.2018.08.19.16.52.43 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 19 Aug 2018 16:52:44 -0700 (PDT) Content-Type: multipart/alternative; boundary="Apple-Mail=_2043597C-37A7-4772-82A4-E784D4CC7C8F" Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\)) Subject: Re: [AE] Problems (bug) with EXR sequences Date: Mon, 20 Aug 2018 09:52:40 +1000 References: To: After Effects Mail List In-Reply-To: Message-Id: <8A7FF02F-ABA5-462A-A765-65CC0B2C3975@chriszwar.com> X-Mailer: Apple Mail (2.3445.9.1) --Apple-Mail=_2043597C-37A7-4772-82A4-E784D4CC7C8F Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 Adobe are looking into it, but I think the actual bug is at the Adobe = end. Basically, if you have a sequence (as opposed to a single frame) = then After Effects reads the header information in the EXR more = frequently than it needs to. EXRs can have large headers depending on = the number of channels and so this can add up to lengthy delays - even = worse over a network. Brendan=E2=80=99s clever workaround is to cache the header of the EXR in = memory, so this behaviour becomes much faster. In one case I had an EXR = sequence that was originally rendering at 2 1/2 mins per frame (150 = seconds per frame) and with Brendan=E2=80=99s latest patch this came = down to a about 3 - 5 seconds per frame. Obviously that is a MASSIVE = improvement, and this is before the actual bug itself has been fully = investigated and fixed. EXRs under a certain size don=E2=80=99t seem to show the problem, which = is why it may not have been identified before. The EXRs I am using have = Cryptomattes, which bump up the header size significantly. Unfortunately I am on a strict NDA for this project but if I can find a = suitable unrestricted demo sequence I=E2=80=99ll post an article / = tutorial on it. -Chris > On 19 Aug 2018, at 11:11 am, J Bills wrote: >=20 > Just for my own future ref, were there any other details about the = disfunctional exr sequences to share? They were multichannel - any = certain flavor (piz, etc) or anything else to be aware of? >=20 > Hopefully whatever it was is fixed in short order. --Apple-Mail=_2043597C-37A7-4772-82A4-E784D4CC7C8F Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8
Adobe are looking into it, but I think the actual bug is at = the Adobe end.  Basically, if you have a sequence (as opposed to a = single frame) then After Effects reads the header information in the EXR = more frequently than it needs to.  EXRs can have large headers = depending on the number of channels and so this can add up to lengthy = delays - even worse over a network.

Brendan=E2=80=99s clever workaround is = to cache the header of the EXR in memory, so this behaviour becomes much = faster.  In one case I had an EXR sequence that was originally = rendering at 2 1/2 mins per frame (150 seconds per frame) and with = Brendan=E2=80=99s latest patch this came down to a about 3 - 5 seconds = per frame.  Obviously that is a MASSIVE improvement, and this is = before the actual bug itself has been fully investigated and = fixed.

EXRs = under a certain size don=E2=80=99t seem to show the problem, which is = why it may not have been identified before.  The EXRs I am using = have Cryptomattes, which bump up the header size = significantly.

Unfortunately I am on a strict NDA for this project but if I = can find a suitable unrestricted demo sequence I=E2=80=99ll post an = article / tutorial on it.


-Chris


On 19 Aug 2018, at 11:11 am, J = Bills <AE-List@media-motion.tv> wrote:

Just for my own future ref, were there any = other details about the disfunctional exr sequences to share?  They = were multichannel - any certain flavor (piz, etc) or anything else to be = aware of?

Hopefully whatever it was is fixed in short = order.

= --Apple-Mail=_2043597C-37A7-4772-82A4-E784D4CC7C8F--