From: "Chris Zwar" Received: from mail-pf1-f169.google.com ([209.85.210.169] verified) by media-motion.tv (CommuniGate Pro SMTP 6.1.0) with ESMTPS id 7450442 for AE-List@media-motion.tv; Thu, 17 Oct 2019 00:25:14 +0200 Received: by mail-pf1-f169.google.com with SMTP id y72so265083pfb.12 for ; Wed, 16 Oct 2019 15:29:11 -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=+9cddY6pkUf4PyFNWcD1IcsNht8bQqMrz1NRkDk5isk=; b=qvtvo0xiAxiyx9sn9WmjJfRY/1Rnc1Fsjf5gH4yipMPPw4hBOb7CwXJQ/3g8zcl25M X8ForJxpKzWsr+UwDrXJ3TsJDhQ0l9RCnHwk0bZOLiVEC+8xx9HugKZe3ILnHMxOWMuE wzZNAxAnFqa2bS0FZHix6KKtdAijpjO4gq+e0SmpVLdQQYlxx6otg9+aBBRtsm7rHI/c 2nsWW4mZzZ7lZz0vy8kZXO7g/xLIuABUcz7/nPLtrX/82DPh5fJkQsSY0xraKoZHAVQE chxSVHdLpCT/rqYscFuJypWb9zgQa/XEplNRbn186eDQtryOU2gaKbMeg7Hb+mFleP3G SejQ== 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=+9cddY6pkUf4PyFNWcD1IcsNht8bQqMrz1NRkDk5isk=; b=NijZhxqhRmswBMve8wNxFQSwWPq/k+SVApYolmk7uhjNibiJoyl+Cg357L07Qb44GU +PS4YFINXn4w7qRodexCvYiB43LiSfOLl0AMeQDZH0rGp1QFYC3QubwqN5PraigCSd4M m3gPFwoVAByEIndQ40LA4RI9VpJfXETDgx4x8eg510lYydX9sslSoaEmVlpqeiXI/Eb8 dcfvQO17b75TmEGkAcvbIXzwE/KLTWBrjEHT89rIK/GbBVjcKxChBbPrqaGAviovBqa0 o22A1Lf5Ls5a8hmiR6HD2B7D/ESoqIUgYtVUVWZs4V7Fbpangj1Uy+MubYEprwFcSHRN 75sA== X-Gm-Message-State: APjAAAU93vRh3F0nvbB/M8y6eqCON079ZQssY2LhFxUfvJfhYNmk6PEg HU2YAq8SZNsYiqpcdeSPFubJVLlu9Zk= X-Google-Smtp-Source: APXvYqzMmE3ubIQx8oSzF8t11ktlYhuJMJbAJyMrEJw2OE6J7ODBLFWMvCSLQzuK1cfaWkeITLpiNg== X-Received: by 2002:a17:90b:914:: with SMTP id bo20mr363693pjb.6.1571264949650; Wed, 16 Oct 2019 15:29:09 -0700 (PDT) Return-Path: Received: from [192.168.1.141] ([210.8.181.146]) by smtp.gmail.com with ESMTPSA id x10sm99310pfr.44.2019.10.16.15.29.08 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 16 Oct 2019 15:29:09 -0700 (PDT) Content-Type: multipart/alternative; boundary="Apple-Mail=_9F55E6D0-782E-4D96-8425-9165A6D442A9" Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\)) Subject: Re: [AE] HAP Support Date: Thu, 17 Oct 2019 09:29:05 +1100 References: To: After Effects Mail List In-Reply-To: Message-Id: <7C9C7881-10CB-458A-9F24-389FCE619341@chriszwar.com> X-Mailer: Apple Mail (2.3445.9.1) --Apple-Mail=_9F55E6D0-782E-4D96-8425-9165A6D442A9 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 Yeah Michael, I was wrong, sorry. Adobe introduced native Hap import = but not rendering. =20 I=E2=80=99ve spent years working on large scale productions that need = very specific output formats so I totally understand the frustration of = not being able to meet client=E2=80=99s demands with the current = toolset. I can only assume that this is very clear evidence that a = solution is coming soon=E2=80=A6 -Chris > On 17 Oct 2019, at 7:04 am, Michael Powers = wrote: >=20 > Hi Victoria, this is the link I used from your post: > https://github.com/disguise-one/hap-encoder-adobe-cc/releases = > HapEncoder-1.0.9-rc1-win64.exe > =20 > I also tried latest standard install: > HapQuickTimeCodec.Windows.v12.msi > =20 > Chris, I am not make anyone feel bad. I am trying to get a = long-standing situation remedied. After two years, I think Adobe needs = to fix it. Five years in the future, will there still be limited HAP = functionality in Adobe products because of a decision Apple made seven = years prior? > =20 > I think Adobe has made a big misstep trying to force the render queue = to AME. They should have improved After Effects=E2=80=99 render queue = functionality with folders. It is the best way to retain a history of a = project=E2=80=99s workflow, render paths, and render times. > =20 > =20 > Mike Powers > Director of Animation \ Cramer > =20 > 781.278.2354 > mpowers@cramer.com > https://vimeo.com/mpowers > 3DBOXX W8920Processor 32.0 GB RAM=20 > Dual Xeon CPU E5-2670 0 @ 2.60GHz, 2601 Mhz, 8 Core(s), 16 Logical = Processor(s) > Windows 10 Enterprise - 1809 > NVIADIA Dual RTX2080TI 11GB V 419.35 > =20 > =20 > =20 > =20 > =20 > =20 > From: After Effects Mail List >=20 > Sent: Tuesday, October 15, 2019 7:34 PM > To: After Effects Mail List > > Subject: Re: [AE] HAP Support > =20 > =20 > On 16 Oct 2019, at 5:24 am, Michael Powers > wrote: > Adobe did a great disservice to its pro event user base when it = dropped AfterFX HAP support.=E2=80=9D > =20 > I always feel sorry for the Adobe staff when I see comments like this. = Adobe did not drop Hap support. Apple deprecated quicktime, and hap is = a quicktime codec. So when Apple stopped quicktime codecs from working, = all 3rd party quicktime codecs - including Hap and dxf - became = unavailable. In actual fact, Adobe introduced native Hap support so you = can still render Haps. The problems here are solely to do with Apple = and not Adobe. > =20 > However, like you, I just looked and I can=E2=80=99t see Hap either. = I=E2=80=99m using 16.1.2 on Windows, and I can see the Apple ProRes = options but not Hap. It=E2=80=99s not showing up on my Mac in CC 2019 = either, or CC 2018. > =20 > I know that native Hap support was there at some point because I was = one of the squeaky wheels crying out for it, as I used to do a lot of = events work that needed Hap. I was very happy when it was introduced = and I used it a lot. > =20 > But it does look like it=E2=80=99s disappeared=E2=80=A6? > =20 > =20 > -Chris --Apple-Mail=_9F55E6D0-782E-4D96-8425-9165A6D442A9 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8 Yeah = Michael, I was wrong, sorry.  Adobe introduced native Hap import = but not rendering.  
I=E2=80=99ve spent years = working on large scale productions that need very specific output = formats so I totally understand the frustration of not being able to = meet client=E2=80=99s demands with the current toolset. I can only = assume that this is very clear evidence that a solution is coming = soon=E2=80=A6

-Chris



On 17 Oct 2019, at 7:04 am, Michael Powers = <AE-List@media-motion.tv> wrote:

Hi = Victoria, this is the link I used from your post:
https://github.com/disguise-one/hap-encoder-adobe-cc/releases
 
I also tried latest standard = install:
 
Chris, I = am not make anyone feel bad. I am trying to get a long-standing = situation remedied. After two years, I think Adobe needs to fix it. Five = years in the future, will there still be limited HAP functionality in = Adobe products because of a decision Apple made seven years prior?
 
I think = Adobe has made a big misstep trying to force the render queue to AME. = They should have improved After Effects=E2=80=99 render queue = functionality with folders. It is the best way to retain a history of a = project=E2=80=99s workflow, render paths, and render times.
 
 

Mike Powers
Director of Animation \ Cramer
 
781.278.2354
mpowers@cramer.com

https://vimeo.com/mpowers

3DBOXX = W8920Processor          = 32.0 GB RAM 
Dual Xeon CPU = E5-2670 0 @ 2.60GHz, 2601 Mhz, 8 Core(s), 16 Logical Processor(s)
Windows 10 Enterprise - = 1809
NVIADIA Dual RTX2080TI 11GB V = 419.35
 
 
 
 
 
 
From: After Effects Mail List = <AE-List@media-motion.tv> 
Sent: Tuesday, October 15, 2019 = 7:34 PM
To: After Effects Mail List = <AE-List@media-motion.tv>Subject: Re: [AE] HAP Support
 
 
On 16 Oct 2019, at 5:24 = am, Michael Powers <AE-List@media-motion.tv> wrote:
 Adobe did a great disservice to = its pro event user base when it dropped AfterFX HAP support.=E2=80=9D
 
I always feel sorry for = the Adobe staff when I see comments like this.  Adobe did not drop = Hap support.  Apple deprecated quicktime, and hap is a quicktime = codec.  So when Apple stopped quicktime codecs from working, all = 3rd party quicktime codecs - including Hap and dxf - became unavailable. =  In actual fact, Adobe introduced native Hap support so you can = still render Haps.  The problems here are solely to do with Apple = and not Adobe.
 
However, like you, I just looked and I can=E2=80=99t see Hap = either.  I=E2=80=99m using 16.1.2 on Windows, and I can see the = Apple ProRes options but not Hap. It=E2=80=99s not showing up on my Mac = in CC 2019 either, or CC 2018.
 
I know that native Hap support was there at some point = because I was one of the squeaky wheels crying out for it, as I used to = do a lot of events work that needed Hap.  I was very happy when it = was introduced and I used it a lot.
 
But it does look like it=E2=80=99s disappeared=E2=80=A6?
 
 
-Chris

= --Apple-Mail=_9F55E6D0-782E-4D96-8425-9165A6D442A9--