From: "Gary Reisman" <AE-List@media-motion.tv>
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: quoted-printable
MIME-version: 1.0 (Mac OS X Mail 11.3 \(3445.6.18\))
Subject: Re: [AE] updating and compatibility
Date: Thu, 03 May 2018 18:08:35 -0700
References: <list-6445222@media-motion.tv>
To: After Effects Mail List <AE-List@media-motion.tv>
In-reply-to: <list-6445222@media-motion.tv>
Message-id: <34E1710A-CA30-4B04-9047-93B0BA9D98A5@mac.com>

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:
>=20
> 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.
>=20
> S
>=20
>> On May 3, 2018, at 6:37 PM, henry birdseye <AE-List@media-motion.tv> =
wrote:
>>=20
>> And forcing users to re-encode previously viable elements to keep =
them usable is also very uncool.
>>=20
>>=20
>> 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.  :(
>>>=20
>>>=20
>=20