From: "Chris Zwar" Received: from mail-pf1-f177.google.com ([209.85.210.177] verified) by media-motion.tv (CommuniGate Pro SMTP 6.1.0) with ESMTPS id 7187603 for AE-List@media-motion.tv; Fri, 09 Nov 2018 13:57:34 +0100 Received: by mail-pf1-f177.google.com with SMTP id p17-v6so904723pfj.12 for ; Fri, 09 Nov 2018 05:10:09 -0800 (PST) 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=T0LZ+93bHH6UgGoucdrRtG/47oJfWyoTH7TyK6LVbdc=; b=pk/5VatNGLIB1CQSI/YlDbcnU6p0YK8vgfiZ2YsCSMw1lE0ioBXNnLWqnuoHflFXFt XtuD+zY+VCx0GkoBC7GMDcFIU0/6uB2qe0f8mlSZn02iS6u2VAU8LdolPmIa951v96JO rJ3+/ULit+9SG92w6zwRPmSmb8Z89MiZBg7JOU6WGBskefDHedn/BSRAUFCxp3UIt/OC UQ3ejUBY7HbGCS4xGXK92GYz8n1JrlAVWffSz6MZbp0C6nu0hiB+cDE/sf/QX175eYSi qoTrPp897ktueVfk/qWN2AvjqPZ68s+puq/SQzK+KSgb0Lxivw/nDIK/k6BweEh6Qygb MZ4Q== 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=T0LZ+93bHH6UgGoucdrRtG/47oJfWyoTH7TyK6LVbdc=; b=Hr7qy+FQ4nMwrSzhMtilse6NIyZWqoZmRVx7es8EKj0Onw+Bxm4s/Hx0VUb5rjIgPT /Yjh+nxeqhnED+4TphHOETwukH6+36Af1+UB5DqfLcUisK8SEujmDDkguXEDVe64w/Ni tekEY5Yj4lLeXoiSj1c7u0yeRMW6z/a1eLk6SG7Rq+L3UGFlq7oz7RAv483vx/GH4P5A Bk5TUB7ZiI4iEQDgxz5fvLjihuMxVwLgAUpw8yT7WzZJjNECh1g2bd2FrTcPqUWJVBm1 3GTnCMWf0G/amvppH+phqg15ck4VpOvPzbnl6NJRL/d7dc6KugAlOKgKm4gwtOo0ViwN XReA== X-Gm-Message-State: AGRZ1gJJ/80VwYYgrb+nEZP4U8Fke9KKH98+CZHwDEM/F2HWP/BKcXN4 evfYqlbdSJhQb8AN38w2WAt3mXihBjc= X-Google-Smtp-Source: AJdET5fp3dFRy1M6RcIb0V05cgZtqgEQVGyqiSD1WLvxmw31EaOh+HHPUwmlwQEMT9uHsQVvyscaxg== X-Received: by 2002:a63:61c8:: with SMTP id v191mr7478127pgb.242.1541769007672; Fri, 09 Nov 2018 05:10:07 -0800 (PST) Return-Path: Received: from [192.168.0.4] ([101.164.85.130]) by smtp.gmail.com with ESMTPSA id p14-v6sm6575155pgn.45.2018.11.09.05.10.05 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 09 Nov 2018 05:10:07 -0800 (PST) Content-Type: multipart/alternative; boundary="Apple-Mail=_475D5829-02B5-48C6-8D5D-23918BD1FA32" Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\)) Subject: Re: [AE] ProEXR 2.0 Date: Sat, 10 Nov 2018 00:10:03 +1100 References: To: After Effects Mail List In-Reply-To: Message-Id: <5DAFC14D-7717-47BC-8313-12298D49D83B@chriszwar.com> X-Mailer: Apple Mail (2.3445.9.1) --Apple-Mail=_475D5829-02B5-48C6-8D5D-23918BD1FA32 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 It=E2=80=99s passed midnight here but I=E2=80=99ve pushed out an article = on EXRs & After Effects: = https://www.provideocoalition.com/after-effects-exrs-compositing-with-big-= boy-toys/ = Hope this helps and thanks again to Brendan! > On 9 Nov 2018, at 8:15 am, Michael Powers = wrote: >=20 > Thnx Brendan. I just used the ProEXR Cryptomatte on a projected this = week in AE 2019. I prerendered all the mattes I needed in AE. It is = great to be able to get Mattes out of a 3ds MAX/Arnold project. I only = used object to save on channels. > =20 > From: After Effects Mail List >=20 > Sent: Thursday, November 8, 2018 1:56 PM > To: After Effects Mail List > > Subject: Re: [AE] ProEXR 2.0 > =20 > =20 > On Nov 8, 2018, at 10:33 AM, Teddy Gage > wrote: > =20 > Brendan I tried to use cryptomatte on a few comps in AE using the = previous version and it was brutally, unworkably slow. Render times = ballooned to long lengths like over an hour per frame at high bit depths = or big comps- how is the speed of this new implementation? > =20 > =20 > That sounds like you were running into the problems Chris made me = aware of. If you were, the speed improvements in the release will be = dramatic! > =20 > What was happening (ever since AE CS6 and before!) is that when you = had an EXR sequence and AE was running EXtractoR or something, AE would = read the EXR header many, many times=E2=80=94once for each channel, in = each instance of EXtractoR. When you add in Cryptomatte the EXR header = gets much bigger, multiplying the problem. The result was that these EXR = sequences could be unbearably slow. For some reason AE didn't do this = when you just had a single frame. > =20 > The latest release of AE is still doing this, I believe, but this = version of the OpenEXR plug-in always caches channels and also headers. = This makes things much better, as I think Chris will attest. > =20 > =20 > Now, Cryptomatte is still not the fastest thing. After all, it usually = processes 12 EXR channels in one pass. Some proxy creating might be = wise. > =20 > =20 > But the extreme slowdown there was before should now be gone. > =20 > =20 > Brendan --Apple-Mail=_475D5829-02B5-48C6-8D5D-23918BD1FA32 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8 It=E2=80=99s passed midnight here but I=E2=80=99ve pushed out = an article on EXRs & After Effects:

https://www.provideocoalition.com/after-effects-exrs-compositin= g-with-big-boy-toys/

Hope this helps and thanks again to Brendan!


On = 9 Nov 2018, at 8:15 am, Michael Powers <AE-List@media-motion.tv> wrote:

Thnx = Brendan. I just used the ProEXR Cryptomatte on a projected this week in = AE 2019. I prerendered all the mattes I needed in AE. It is great to be = able to get Mattes out of a 3ds MAX/Arnold project. I only used object = to save on channels.
 
From: After Effects Mail List = <AE-List@media-motion.tv> 
Sent: Thursday, November 8, 2018 = 1:56 PM
To: After Effects Mail List = <AE-List@media-motion.tv>Subject: Re: [AE] ProEXR 2.0
 
 
On Nov 8, 2018, at 10:33 = AM, Teddy Gage <AE-List@media-motion.tv> wrote:
 
Brendan I tried to use cryptomatte on a few = comps in AE using the previous version and it was brutally, unworkably = slow. Render times ballooned to long lengths like over an hour per frame = at high bit depths or big comps- how is the speed of this new = implementation?
 
 
That sounds like you were running into the problems Chris = made me aware of. If you were, the speed improvements in the release = will be dramatic!
 
What was happening (ever since AE CS6 and before!) is that = when you had an EXR sequence and AE was running EXtractoR or something, = AE would read the EXR header many, many times=E2=80=94once for each = channel, in each instance of EXtractoR. When you add in Cryptomatte the = EXR header gets much bigger, multiplying the problem. The result was = that these EXR sequences could be unbearably slow. For some reason AE = didn't do this when you just had a single frame.
 
The latest release of AE is still doing = this, I believe, but this version of the OpenEXR plug-in always caches = channels and also headers. This makes things much better, as I think = Chris will attest.
 
 
Now, Cryptomatte is still not the = fastest thing. After all, it usually processes 12 EXR channels in one = pass. Some proxy creating might be wise.
 
 
But the extreme slowdown there was before should now be = gone.
 
 
Brendan

= --Apple-Mail=_475D5829-02B5-48C6-8D5D-23918BD1FA32--