From: "Roei Tzoref" Received: from mail-io0-f169.google.com ([209.85.223.169] verified) by media-motion.tv (CommuniGate Pro SMTP 6.1.0) with ESMTPS id 6445274 for AE-List@media-motion.tv; Fri, 04 May 2018 09:16:50 +0200 Received: by mail-io0-f169.google.com with SMTP id g1-v6so15225330iob.2 for ; Fri, 04 May 2018 00:22:58 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=bzdd7JjmkSKWPMhcLiFeVvzVjbaND4BqAKM7UuQFTVU=; b=j9oH+SCH1HjjF2cCC2GSSKxrQgVLYcKg5H4k0ZxVtn9AkEDKmQhPkM0A/14co6z8vV SXYsJfO7p6zLZ98UfQgC8uJwa2jauJTqwxHKB4FjcvUtvHcQimN+ou3hMg8ejL3tKi3X tIqIi9IEc7Eb00gWmb1OA2JRy0Vudho1UFKXwUoNIZ9bUF16OZTxZreCuuvmie5qzx48 125dA7JXZEdylNEMSY1rjvo1xujygmI17OzYx0Spg2FnfQljqF4yBOXUrIa6rB2GfEUa 5FLxr7/cIadgCGzT1f7uL8UPtouSPv7mDXlNI9ya8xyROks5IdrkrLcqKhetqVd0ExV7 PinQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=bzdd7JjmkSKWPMhcLiFeVvzVjbaND4BqAKM7UuQFTVU=; b=rygnYFR/PARI1Kzivozs6S1KRaHyNU2Zh2Y9eV2WwVzSWz0g49FmbVLo5fALZf4m/P f6XT5EEvD8zoxBznxViu30CmL41ANaId8Tpblse0jVBaqBVMXVNgqJGkpHtEFGi8mYPx Y9qT3csJx0VOsIhA9Uu5Tcd2gBSyxtw/sF0RZidqfWTjbtMJvkYF6Jktk2efn7BRm/MX BterSMIDXsQCMG/mH4A+TA7H8e5DrlO2OOpujDLd/Pj8yAYJ5wgwmmFepi49pzur5djZ wSXdtWptIXs9JUdaB6sdXjMsLNdYujw125JV79WDdIFethcHUqt1Qab60HnC0d5I5NzA 5/RQ== X-Gm-Message-State: ALQs6tAZ7FYEuP9ZSox4fNL96+7n4k8cNz85ngSUaL3XZN3sW2EpE+qN L5WDEzFIfBe1usIzYdYkQTZ7QCFBrcet9hV1DeM= X-Google-Smtp-Source: AB8JxZojsTI9bOOUFwJAHfXRmwI426T7vtmWQcwts0LB3gl5dGTLjI0YjO5RQCmDEewtgDhWxHLYsFYFrntU7tfKf8A= X-Received: by 2002:a6b:e614:: with SMTP id g20-v6mr12526085ioh.1.1525418576297; Fri, 04 May 2018 00:22:56 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: Date: Fri, 04 May 2018 07:22:45 +0000 Message-ID: Subject: Re: [AE] updating and compatibility To: After Effects Mail List Content-Type: multipart/alternative; boundary="0000000000005fc713056b5c30a0" --0000000000005fc713056b5c30a0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable I never used H264 on QT because the quality is poor and size could reach x10 times over AME's H.264. When CC2014 came and took my native H.264 in Ae, and my yellow U.I color, I did not update and only a year later, when the U.I looked better, came to terms with using AME for mp4 (and the blue color) and it worked well and actually made me work faster since I could render delivery formats and keep working. It's not as fast per render that's true. A year ago when AfterCodecs came out, I immediately purchased and sent all my feature requests to Antoine the developer. Using that in Ae for fast, small size, great quality mp4 like the old days. Now with many codecs missing, a part of me is relieved for narrowing the options so I could focus only on a few. QT Png was my best friend because I rendered graphics on alpha for short durations and had to deliver lossless online - it's the best compression/quality ratio you can get. But it's the slowest.. now that it's gone, after some testing, I switched to AfterCodec's ProRes 4444. They say in the FAQ you should not use it for broadcast, but I give my stuff to editors and it seems to work just fine. Small size, lossless quality, and 10bit. Animation still is the fastest and reliable 8bit option and in a news station I work on, that's what the use to transfer graphics to the editors. 8 bit is fine since there is no color correction or any other further image manipulation. When I need to send video from Ae to further processing (color mostly), I got used to DNx and my editor's work with it too. I also send AfterCodec's ProRes422 HQ preset at times. For Digital intermediate, I might use Cineform4. For sequence, I shifted to using DPX over PNG (I may have waited way too long to do that) Mantaining compatibilty with old projects can be annoying, but I keep old versions of Ae. CC2017 is my backup version for these things if I need to open a project that uses legacy codecs. I might transcode if I want to use the new features. That's about it. I feel I am covered. On Fri, 4 May 2018 at 5:07 Steve Oakley wrote: > thats where we where going with MOX which remains in beta status. > documented, no patent encumbrances, source code available, already uses > industry *open* standards like MXF as container. > > endless conversations adobe should create and release basically this, so = a > community took this on. really what it needs is testing, maybe some tweak= s, > and better adoption. > > otherwise h.264 and Mpeg2 are as close as we get to universal codecs. > h.264 iframe 10/12 bit 444 is certainly respectable. > > as for legacy codecs=E2=80=A6 many of the big ones are supported like DV2= 5 / 50 > /100, Mpeg2, Animation. PhotoJpeg, Mjpeg A and B would be welcome > additions. after that, who knows. do we really need or want to see cinepa= k > movs of some corp video from 1992 ? > > the warnings have been out for YEARS this time was coming. I converted a > lot of stuff a couple years ago, and even in the last few months found an= d > converted a bunch of old mov files. that said, SD on a 4K screen is a > postage stamp of bad quality, never mind a few odd 320 movs. those I > actually deleted. even the broadcast stuff I had from the late 90=E2=80= =99s now > kind of doesn=E2=80=99t matter much and isn=E2=80=99t so watchable anymor= e=E2=80=A6 well you want > to see 98 degrees first national TV appearance ? thats was on my reel but= I > don=E2=80=99t think its so entertaining anymore, nor do I show it or most= of the > stuff I worked on even with big names in it from that era just because it > looks pretty crappy now. > > S > > > On May 3, 2018, at 7:45 PM, Stephen van Vuuren > wrote: > > > > Adobe and other media companies (Avid etc.) should have pressed hard > that the core codecs used in media files from Apple, Dolby, Microsoft etc= . > should have some type of open source decode/encode for future digital > preservation. > > > > We are not just talking about client files on commercial jobs which is = a > pain. There is massive amount of material (films, television shows, > documentaries, personal memories) created with those codecs and combine > that with the poorly thought out rush to dump physical media means there > will be likely be a greater loss of original masters than in the flammabl= e > film days. > > > > Only people who've thought to output films to DCP format (JPEG2000 is > archival quality and open sourced or a physical non-encrypted format - no= n > copy protected bluray is about as good as what can be had there as other > than 35mm film, there is no high resolution, high color depth physical > media. > > > > A ProRes or Avid file is not a master - those codecs could well suffer > the same fates in 10, 20, 30 years. > > > > This is a huge stick our head in the sands problem that will never go > away, only get worse. > > > > -----Original Message----- > > From: After Effects Mail List > > Sent: Thursday, May 3, 2018 8:23 PM > > To: After Effects Mail List > > Subject: Re: [AE] updating and compatibility > > > > Apple can be especially uncool. Dolby is on my list too. > > > > > > On 5/3/2018 8:02 PM, Steve Oakley 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 a= pp > current wiith what the OS can, or in this case can=E2=80=99t deliver. > >> > >> S > >> > > > +---End of message---+ > To unsubscribe send any message to > --0000000000005fc713056b5c30a0 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
I never used H264 on QT because the quality is poor = and size could reach x10 times over AME's H.264. When CC2014 came and t= ook my native H.264 in Ae, and my yellow U.I color, I did not update and on= ly a year later, when the U.I looked better, came to terms with using AME f= or mp4 (and the blue color) and it worked well and actually made me work fa= ster since I could render delivery formats and keep working. It's not a= s fast per render that's true.

A year ago when AfterCodecs came out, I immediately purchased an= d sent all my feature requests to Antoine the developer. Using that in Ae f= or fast, small size, great quality mp4 like the old days.

Now with many codecs missing, a part of m= e is relieved for narrowing the options so I could focus only on a few.=C2= =A0

QT Png was my best f= riend because I rendered graphics on alpha for short durations and had to d= eliver lossless online - it's the best compression/quality ratio you ca= n get. But it's the slowest.. now that it's gone, after some testin= g, I switched to AfterCodec's ProRes 4444. They say in the FAQ you shou= ld not use it for broadcast, but I give my stuff to editors and it seems to= work just fine. Small size, lossless quality, and 10bit.

Animation still is the fastest and reliab= le 8bit option and in a news station I work on, that's what the use to = transfer graphics to the editors. 8 bit is fine since there is no color cor= rection or any other further image manipulation.=C2=A0

When I need to send video from Ae to further= processing (color mostly), I got used to DNx and my editor's work with= it too. I also send AfterCodec's ProRes422 HQ preset at times.=C2=A0

For Digital intermediate,= I might use Cineform4.=C2=A0

For sequence, I shifted to using DPX over PNG (I may have waited way = too long to do that)

Man= taining compatibilty with old projects can be annoying, but I keep old vers= ions of Ae. CC2017 is my backup version for these things if I need to open = a project that uses legacy codecs. I might transcode if I want to use the n= ew features.=C2=A0

That&= #39;s about it. I feel I am covered.

On Fri, 4 May 2018 at 5:07 Steve Oakley <AE-List@media-motion.tv> wrote:
thats where we where going with MOX which remains in bet= a status. documented, no patent encumbrances, source code available, alread= y uses industry *open* standards like MXF as container.

endless conversations adobe should create and release basically this, so a = community took this on. really what it needs is testing, maybe some tweaks,= and better adoption.

otherwise h.264 and Mpeg2 are as close as we get to universal codecs. h.264= iframe 10/12 bit 444 is certainly respectable.

as for legacy codecs=E2=80=A6 many of the big ones are supported like DV25 = / 50 /100, Mpeg2, Animation. PhotoJpeg, Mjpeg A and B would be welcome addi= tions. after that, who knows. do we really need or want to see cinepak movs= of some corp video from 1992 ?

the warnings have been out for YEARS this time was coming. I converted a lo= t of stuff a couple years ago, and even in the last few months found and co= nverted a bunch of old mov files. that said, SD on a 4K screen is a postage= stamp of bad quality, never mind a few odd 320 movs. those I actually dele= ted. even the broadcast stuff I had from the late 90=E2=80=99s now kind of = doesn=E2=80=99t matter much and isn=E2=80=99t so watchable anymore=E2=80=A6= well you want to see 98 degrees first national TV appearance ? thats was o= n my reel but I don=E2=80=99t think its so entertaining anymore, nor do I s= how it or most of the stuff I worked on even with big names in it from that= era just because it looks pretty crappy now.

S

> On May 3, 2018, at 7:45 PM, Stephen van Vuuren <AE-List@media-motion.tv> w= rote:
>
> Adobe and other media companies (Avid etc.) should have pressed hard t= hat the core codecs used in media files from Apple, Dolby, Microsoft etc. s= hould have some type of open source decode/encode for future digital preser= vation.
>
> We are not just talking about client files on commercial jobs which is= a pain. There is massive amount of material (films, television shows, docu= mentaries, personal memories) created with those codecs and combine that wi= th the poorly thought out rush to dump physical media means there will be l= ikely be a greater loss of original masters than in the flammable film days= .
>
> Only people who've thought to output films to DCP format (JPEG2000= is archival quality and open sourced or a physical non-encrypted format - = non copy protected bluray is about as good as what can be had there as othe= r than 35mm film, there is no high resolution, high color depth physical me= dia.
>
> A ProRes or Avid file is not a master - those codecs could well suffer= the same fates in 10, 20, 30 years.
>
> This is a huge stick our head in the sands problem that will never go = away, only get worse.
>
> -----Original Message-----
> From: After Effects Mail List <AE-List@media-motion.tv>
> Sent: Thursday, May 3, 2018 8:23 PM
> To: After Effects Mail List <AE-List@media-motion.tv>
> Subject: Re: [AE] updating and compatibility
>
> Apple can be especially uncool. Dolby is on my list too.
>
>
> On 5/3/2018 8:02 PM, Steve Oakley 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=E2=80=99t deliver.<= br> >>
>> S
>>


+---End of message---+
To unsubscribe send any message to <ae-list-off@media-motion.tv>
--0000000000005fc713056b5c30a0--