From: "Lloyd Alvarez" <AE-List@media-motion.tv>
Received: from aescripts.com ([162.252.107.88] verified)
  by media-motion.tv (CommuniGate Pro SMTP 6.1.0)
  with ESMTPS id 6445230 for AE-List@media-motion.tv; Fri, 04 May 2018 03:04:46 +0200
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed;
	d=aescripts.com; s=dkim; h=Content-Type:To:Subject:Message-ID:Date:From:
	In-Reply-To:References:MIME-Version:Sender:Reply-To:Cc:
	Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date:
	Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id:
	List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive;
	 bh=c8njGJuKZqa5Cv5XDb0oP2JEwsTYNRWFE7AoRqt58TQ=; b=ET3NdvGid1dfjnJSI5pWrv2M2
	YofGOg2aPI/MepJCUY++X3TC05kF0Z9NbKW0gbOOGG+UT4N9Kx+8SXMfS4qGBXRsAdOOpDFt1rLwK
	KPOG3/9wRk6B/4MGKCr20F3iWFKK0/4wRIGj0fe3MNHOPsEGdXokfUXazfoXIOCAGuqtmnNEIYbmN
	r4OA5lFq/rMTJ2+PaNLOILeSGwjix/HXijYR7rVOl6pfEmEe9lHHstkx+ZrNmX6WQ8pE8RXlOHeDV
	wGk67Qdb7dHgM2umuhaEqs15e/HrhGF7kFlJdRRssYZytENvUH86BeYaDl5Yf9nTwddinA1kgGcdY
	Q4CtDw0mg==;
Received: from mail-vk0-f45.google.com ([209.85.213.45])
	by aescriptsmhm.magemojo.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128)
	(Exim 4.90_1)
	(envelope-from <lists@aescripts.com>)
	id 1fEPFL-0009BQ-Jb
	for AE-List@media-motion.tv; Fri, 04 May 2018 01:10:51 +0000
Received: by mail-vk0-f45.google.com with SMTP id x204-v6so12426544vkd.7
        for <AE-List@media-motion.tv>; Thu, 03 May 2018 18:10:51 -0700 (PDT)
X-Gm-Message-State: ALQs6tCh7Rxyum85Dc1orkTGfz6Zn0O3jprn1he4z+r9lsD+JnrjV86q
	ViPVCPnVn+P0qbd6nmHzM6Dyk92kplIrGnd8O3Y=
X-Google-Smtp-Source: AB8JxZpjJgr4ZVocnfeZRdbZvyJVvgDCt9dY/HAuTet45irwgkMshY+ka4aYYUKxm2QqMjWM9QdSdtyBq2m/RE0KZ2Y=
X-Received: by 2002:a1f:2f8a:: with SMTP id v132-v6mr22980301vkv.34.1525396246328;
 Thu, 03 May 2018 18:10:46 -0700 (PDT)
MIME-Version: 1.0
References: <list-6445235@media-motion.tv>
In-Reply-To: <list-6445235@media-motion.tv>
Date: Fri, 04 May 2018 01:10:34 +0000
X-Gmail-Original-Message-ID: <CAOPhT+FNDCHqmmMU1ijG-esEA524xsmXcQf6iQRtA2E8oLm7ZA@mail.gmail.com>
Message-ID: <CAOPhT+FNDCHqmmMU1ijG-esEA524xsmXcQf6iQRtA2E8oLm7ZA@mail.gmail.com>
Subject: Re: [AE] updating and compatibility
To: After Effects Mail List <AE-List@media-motion.tv>
Content-Type: multipart/alternative; boundary="000000000000678170056b56fd1e"

--000000000000678170056b56fd1e
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

You can use AfterCodecs to render HAP :)

https://aescripts.com/aftercodecs/

Lloyd


On Thu, May 3, 2018 at 9:09 PM Gary Reisman <AE-List@media-motion.tv> wrote=
:

> I can render out a h.264 movie out of the current FCPX no prob tho.
> .so can=E2=80=99t blame Apple on this one I don=E2=80=99t think.
>
>
> > On May 3, 2018, at 5:02 PM, Steve Oakley <AE-List@media-motion.tv>
> wrote:
> >
> > blame apple then as they are the gulity party in killing off QT32 and a=
n
> codecs which are implemented via QT32. Adobe is simply keeping their app
> current wiith what the OS can, or in this case can=E2=80=99t deliver.
> >
> > S
> >
> >> On May 3, 2018, at 6:37 PM, henry birdseye <AE-List@media-motion.tv>
> wrote:
> >>
> >> And forcing users to re-encode previously viable elements to keep them
> usable is also very uncool.
> >>
> >>
> >> On 5/3/2018 7:34 PM, Gary Reisman wrote:
> >>> Forcing users to run an additional app or use AME just to render out
> reference/h.264 movies or similar is..  not so cool Adobe.  :(
> >>>
> >>>
> >
>
>
> +---End of message---+
> To unsubscribe send any message to <ae-list-off@media-motion.tv>
>
--=20
Cheers, Lloyd

--000000000000678170056b56fd1e
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div><div dir=3D"auto">You can use AfterCodecs to render HAP :)</div><div d=
ir=3D"auto"><br></div><div dir=3D"auto"><a href=3D"https://aescripts.com/af=
tercodecs/">https://aescripts.com/aftercodecs/</a></div><div dir=3D"auto"><=
br></div><div dir=3D"auto">Lloyd</div><div dir=3D"auto"><br></div><br><div =
class=3D"gmail_quote"><div>On Thu, May 3, 2018 at 9:09 PM Gary Reisman &lt;=
<a href=3D"mailto:AE-List@media-motion.tv">AE-List@media-motion.tv</a>&gt; =
wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8e=
x;border-left:1px #ccc solid;padding-left:1ex">I can render out a h.264 mov=
ie out of the current FCPX no prob tho.<br>
.so can=E2=80=99t blame Apple on this one I don=E2=80=99t think.<br>
<br>
<br>
&gt; On May 3, 2018, at 5:02 PM, Steve Oakley &lt;<a href=3D"mailto:AE-List=
@media-motion.tv" target=3D"_blank">AE-List@media-motion.tv</a>&gt; wrote:<=
br>
&gt; <br>
&gt; blame apple then as they are the gulity party in killing off QT32 and =
an codecs which are implemented via QT32. Adobe is simply keeping their app=
 current wiith what the OS can, or in this case can=E2=80=99t deliver.<br>
&gt; <br>
&gt; S<br>
&gt; <br>
&gt;&gt; On May 3, 2018, at 6:37 PM, henry birdseye &lt;<a href=3D"mailto:A=
E-List@media-motion.tv" target=3D"_blank">AE-List@media-motion.tv</a>&gt; w=
rote:<br>
&gt;&gt; <br>
&gt;&gt; And forcing users to re-encode previously viable elements to keep =
them usable is also very uncool.<br>
&gt;&gt; <br>
&gt;&gt; <br>
&gt;&gt; On 5/3/2018 7:34 PM, Gary Reisman wrote:<br>
&gt;&gt;&gt; Forcing users to run an additional app or use AME just to rend=
er out reference/h.264 movies or similar is..=C2=A0 not so cool Adobe.=C2=
=A0 :(<br>
&gt;&gt;&gt; <br>
&gt;&gt;&gt; <br>
&gt; <br>
<br>
<br>
+---End of message---+<br>
To unsubscribe send any message to &lt;<a href=3D"mailto:ae-list-off@media-=
motion.tv" target=3D"_blank">ae-list-off@media-motion.tv</a>&gt;<br>
</blockquote></div></div>-- <br><div dir=3D"ltr" class=3D"gmail_signature" =
data-smartmail=3D"gmail_signature">Cheers,
Lloyd</div>

--000000000000678170056b56fd1e--