From: "Chris Zwar" Received: from mail-pf1-f170.google.com ([209.85.210.170] verified) by media-motion.tv (CommuniGate Pro SMTP 6.1.0) with ESMTPS id 7462588 for AE-List@media-motion.tv; Thu, 07 Nov 2019 12:54:29 +0100 Received: by mail-pf1-f170.google.com with SMTP id 3so2535521pfb.10 for ; Thu, 07 Nov 2019 03:54:28 -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=tIU0Hlv/2fMBet3UBV7qQeDO/0DBp2HL5rwZGvYDm48=; b=Sd1OVOXbtfbVRqkuAeam67LXiMCXcfrtdJ4LxLCevPNSFQ5uc6KlPllN8i4SXjy4UH y1LBn+aPYRfnSx4E8FRFkhHhGG0KokgyTUjEtSObZikfVJGCYTpPBFj/uOwIGSGc3aAj eL30M/ma9vdL9VDCpEmigWD93nnqR18Yzt0FEPX7GYcCn7SWmXk9gvlreHWC/SH213eh y7U0B7HwwMFwmvtBS/sB7HBtwcz89OXy6A2aDJAeY+2diiNQbC1RVR+LuatFr2xbNGmE Qfs5oUsnPKN3HPxbNdYqQMP7y/gnn9KelPGgdNMKPHDSQJ8E0U2XB5didqEVzsZM7eLX Ue+A== 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=tIU0Hlv/2fMBet3UBV7qQeDO/0DBp2HL5rwZGvYDm48=; b=c6VaYTr5yNsNPg60oiAusY6hDeJoWE9NwIcNsFM65cdDdbcRa8rgSS7rWBETtyVZpr o0tyDsdV6JXN07yRInUSWecuyrXN6mCAaJ0MzkpHTxYnns/6qV45ML4Bjz1YOqb4ymRb s8ehRL3QYvZJNNd707+lekx/DpUxqr/T1tA+EqgyGf7+T2tX3p+5UmHwyzRCs5GBocds KBPG/4FY03u/IwM0gJDKeY2hXj/9PXxDazpK/JrHZ11AUmcJi1pvyDvYJ2KTCt3+2ENF VtWcEEvcx8pYvhYJdQj8YxFWjY4vBzVJNeJ45HRu/Ktd0/PzTsxAddLLz1R55UT60cHk LiTg== X-Gm-Message-State: APjAAAWzO3yvgZcHlbNTM9axnbbiDIzanQBiZW2roE6ZUuSKBM27gqrv TSpZp60HCo05tLeo1WF31t9G+znCOlE= X-Google-Smtp-Source: APXvYqxAqeweIPjbcybFDM+XpXZinbOGT5azI4j2gJqHLZHtLOzRiOpYQ7e5RRCQo4UuRUmf2MG7ow== X-Received: by 2002:a62:82c1:: with SMTP id w184mr3554283pfd.134.1573127666769; Thu, 07 Nov 2019 03:54:26 -0800 (PST) Return-Path: Received: from [192.168.0.3] ([101.164.85.130]) by smtp.gmail.com with ESMTPSA id f8sm2914329pgd.64.2019.11.07.03.54.24 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 07 Nov 2019 03:54:25 -0800 (PST) Content-Type: multipart/alternative; boundary="Apple-Mail=_5632DB8F-1421-4251-B92A-3B237744EE06" Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\)) Subject: Re: [AE] 2GB Comp Size Limit Date: Thu, 7 Nov 2019 22:54:21 +1100 References: To: After Effects Mail List In-Reply-To: Message-Id: X-Mailer: Apple Mail (2.3445.9.1) --Apple-Mail=_5632DB8F-1421-4251-B92A-3B237744EE06 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 Tim, Just wondering what resolutions you=E2=80=99re dealing with to have this = problem in 16 bit mode? Just today I tried to open a 12K square 32 bit = EXR and got the 2GB error message, with AE saying it would take 2.1GB to = open the file. But I haven=E2=80=99t seen the problem with 16 bit = images. I have even wondered if it=E2=80=99s possible to run into the = 2GB limit with an 8 bit image=E2=80=A6 -Chris > On 7 Nov 2019, at 4:31 pm, Tim Sassoon = wrote: >=20 > To any AE product people on the list, >=20 > The 2GB comp RAM allocation limit is starting to become a serious = problem for After Effects. I strongly suggest that the trouble be taken = to erase this rather low limit (32-bit internals?). A lot of us work on = giant screen and multi-screen projects where AE=E2=80=99s editorial = capabilities are a critical factor (my proxies are almost 8K), but then = we might have to finish the show in Nuke or Fusion to be able to render = complete scenes in 16 or 32-bit that could otherwise be finished just = fine in AE. That=E2=80=99s my situation right now - saved as TIFF=E2=80=99= s my output frames are over 2GB each. >=20 > Relatedly, AE's ProRes code seems to be a mixture of =E2=80=9Cold=E2=80=9D= and =E2=80=9Cnew=E2=80=9D ProRes - I can write a 15K ProRes 4444 file = from AE just fine, but AE won=E2=80=99t read them reliably, which was a = bit of a shock to find out. Fusion 16 reads AE's movies just fine, = though. >=20 > On the plus side, I=E2=80=99ve been around long enough to have = complained about the original 2K limit, the 4K limit, and now the 2GB = limit :-) >=20 >=20 > Tim Sassoon > Venice, CA >=20 >=20 >=20 >=20 >=20 --Apple-Mail=_5632DB8F-1421-4251-B92A-3B237744EE06 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8 Tim,

Just = wondering what resolutions you=E2=80=99re dealing with to have this = problem in 16 bit mode?  Just today I tried to open a 12K square 32 = bit EXR and got the 2GB error message, with AE saying it would take = 2.1GB to open the file.  But I haven=E2=80=99t seen the problem = with 16 bit images.  I have even wondered if it=E2=80=99s possible = to run into the 2GB limit with an 8 bit image=E2=80=A6

-Chris

On 7 Nov 2019, at 4:31 pm, Tim Sassoon <AE-List@media-motion.tv> wrote:

To any AE product = people on the list,

The 2GB comp RAM allocation limit is starting to become a = serious problem for After Effects. I strongly suggest that the trouble = be taken to erase this rather low limit (32-bit internals?). A lot of us = work on giant screen and multi-screen projects where AE=E2=80=99s = editorial capabilities are a critical factor (my proxies are almost 8K), = but then we might have to finish the show in Nuke or Fusion to be able = to render complete scenes in 16 or 32-bit that could otherwise be = finished just fine in AE. That=E2=80=99s my situation right now - saved = as TIFF=E2=80=99s my output frames are over 2GB each.

Relatedly, AE's ProRes = code seems to be a mixture of =E2=80=9Cold=E2=80=9D and =E2=80=9Cnew=E2=80= =9D ProRes - I can write a 15K ProRes 4444 file from AE just fine, but = AE won=E2=80=99t read them reliably, which was a bit of a shock to find = out. Fusion 16 reads AE's movies just fine, though.

On the plus side, I=E2=80=99= ve been around long enough to have complained about the original 2K = limit, the 4K limit, and now the 2GB limit :-)


Tim = Sassoon
Venice, CA






= --Apple-Mail=_5632DB8F-1421-4251-B92A-3B237744EE06--