Mailing List AE-List@media-motion.tv — Message #64020
From: Stephen van Vuuren <AE-List@media-motion.tv>
Subject: RE: [AE] updating and compatibility
Date: Fri, 4 May 2018 01:16:48 +0000
To: After Effects Mail List <AE-List@media-motion.tv>

+1000 for AfterCodecs. I’ve used that heavily in recent times for all HAP and ProRes on Windows rendering.

 

From: After Effects Mail List <AE-List@media-motion.tv>
Sent: Thursday, May 3, 2018 9:11 PM
To: After Effects Mail List <AE-List@media-motion.tv>
Subject: Re: [AE] updating and compatibility

 

You can use AfterCodecs to render HAP :)

 

 

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’t blame Apple on this one I don’t 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 an codecs which are implemented via QT32. Adobe is simply keeping their app current wiith what the OS can, or in this case can’t 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>

--

Cheers, Lloyd

 
Subscribe (FEED) Subscribe (DIGEST) Subscribe (INDEX) Unsubscribe Mail to ListMaster