From: "Warren Heaton" Received: from st43p00im-ztdg10073201.me.com ([17.58.63.177] verified) by media-motion.tv (CommuniGate Pro SMTP 6.1.0) with ESMTPS id 7450446 for ae-list@media-motion.tv; Thu, 17 Oct 2019 00:50:21 +0200 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=me.com; s=1a1hai; t=1571266458; bh=A0+HtK0pHkk52Zf1Cz5O28tYh/IyCBhtLw0cMwm63x8=; h=From:Content-Type:Subject:Date:To:Message-Id; b=XE3REPviE4mHBLZrlzHh/V1Xb+u8nDadFSJnR31eVAYERYYdLzrg4PV77Wi6KXW9a kik5L6l4IAhbvCw3nGFI3Bw9w5ZaV+/HPlpgOAcFjSZeaEOQeV3OswVJD2iE9tmuOm BnVI1NQiVsuI68Rvw2HxbkyBF84TIr8JeEHwVNtAGq5wuiZioHj7zje2dwjl62ezZK kh8exfiOJJdLBGSuRIl8qCDZoYofYuBqLn3X6PGlxwnH2/lReYZ7Tb5nU68dKyGHwQ poDDSkpSlYDS+4y/yoAn1o6Eldu0F9N/CFD97TTi2if7HMIDwPMEh1Tv7fPFQm6AKD vW0BMns4I0soA== Received: from [192.168.2.7] (unknown [170.20.116.90]) by st43p00im-ztdg10073201.me.com (Postfix) with ESMTPSA id C828C222E80 for ; Wed, 16 Oct 2019 22:54:17 +0000 (UTC) Content-Type: multipart/alternative; boundary="Apple-Mail=_9D818C15-C7D2-4BB6-BDFF-2A5FC2EEF2A5" Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\)) Subject: Re: [AE] HAP Support Date: Wed, 16 Oct 2019 15:54:16 -0700 References: To: After Effects Mail List In-Reply-To: Message-Id: <853FA68D-37B3-4E2B-93EF-07D01FC4D231@me.com> X-Mailer: Apple Mail (2.3445.9.1) X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:,, definitions=2019-10-16_08:,, signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 suspectscore=0 malwarescore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1015 mlxscore=0 mlxlogscore=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1906280000 definitions=main-1910160189 --Apple-Mail=_9D818C15-C7D2-4BB6-BDFF-2A5FC2EEF2A5 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 For HAP delivery, I keep a macOS 10.9.5 boot drive around which has = QuickTime 7.6.6 and the HAP components installed. I think AE 10.5.1 = (CS5.5) is the version of AE. So, I create content with the current = tool set and reboot once the client has approved the sample MP4 movies = or whenever a HAP version needs to be created for the coder. Not ideal, = but it works. -Warren > On Oct 16, 2019, at 3:29 PM, Chris Zwar = wrote: >=20 > 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 >=20 > -Chris >=20 >=20 >=20 >> 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 >=20 --Apple-Mail=_9D818C15-C7D2-4BB6-BDFF-2A5FC2EEF2A5 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8 For = HAP delivery, I keep a macOS 10.9.5 boot drive around which has = QuickTime 7.6.6 and the HAP components installed.  I think AE = 10.5.1 (CS5.5) is the version of AE.  So, I create content with the = current tool set and reboot once the client has approved the sample MP4 = movies or whenever a HAP version needs to be created for the coder. =  Not ideal, but it works.



-Warren






On Oct = 16, 2019, at 3:29 PM, Chris Zwar <AE-List@media-motion.tv> wrote:

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=99= s 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=_9D818C15-C7D2-4BB6-BDFF-2A5FC2EEF2A5--