Return-Path: Received: from [208.97.132.66] (HELO homiemail-a4.g.dreamhost.com) by media-motion.tv (CommuniGate Pro SMTP 4.2.10) with ESMTP id 4865832 for AE-List@media-motion.tv; Sun, 07 Oct 2012 06:50:40 +0200 Received: from homiemail-a4.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a4.g.dreamhost.com (Postfix) with ESMTP id 38B3151C063; Sat, 6 Oct 2012 21:52:42 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; c=nofws; d=influxx.com; h=references :in-reply-to:mime-version:content-type:message-id :content-transfer-encoding:from:subject:date:to; q=dns; s= influxx.com; b=BooeI4DUVDr81pJh9nS9VSXPj2IWC1Vv/lXxT6+waWVh16ykk 6tLoRfSLVTJYvGT60tGBOZTvLJi7eYmPVoMWrzwzuab7IHDuo40KRVfXOSY9uGGH pw9GsAO9OoNr7cM8STUH2F9V4vuEppVibq9aVUahY4IQTQubL9eWZsgVlo= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=influxx.com; h=references :in-reply-to:mime-version:content-type:message-id :content-transfer-encoding:from:subject:date:to; s=influxx.com; bh=G7OLteThbnNMf8zYTF8x5krp49M=; b=A/n1XtTGOJJt5Am/VXYMjpoFSVnV G49r6PdmCNwfsh+RpMF+XbWR0VaY02k29bhrI5l9gSEBcUk4bNRia0zTH4lgvlLG I7vYZ4kU+GjQgsAqHLAkemCKHwpw9JU2ZrisjtQYScVeTVZmTiW+Z/h+OBGPSDaY c3T0rdtpRCvFN9Q= Received: from [192.168.1.75] (76-206-254-56.lightspeed.irvnca.sbcglobal.net [76.206.254.56]) (Authenticated sender: adam@influxx.com) by homiemail-a4.g.dreamhost.com (Postfix) with ESMTPA id E965951C062; Sat, 6 Oct 2012 21:52:41 -0700 (PDT) References: In-Reply-To: Mime-Version: 1.0 (1.0) Content-Type: multipart/alternative; boundary=Apple-Mail-AE0193F3-23C0-4E25-B0D6-CC476CCB1EBA Message-Id: <7125DB6F-2649-4319-AB04-AA5C9569480F@influxx.com> Content-Transfer-Encoding: 7bit X-Mailer: iPhone Mail (10A403) From: Adam Mercado Subject: Re: [AE] incorrect colors on output to client Date: Sat, 6 Oct 2012 21:52:40 -0700 To: After Effects Mail List --Apple-Mail-AE0193F3-23C0-4E25-B0D6-CC476CCB1EBA Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Well you mentioned PNG and that is my codec of choice when I get those colou= r shift issues and need uncompressed or alpha. Try rendering a PNG sequence o= r a QT with PNG as format Sent from the ubiquitous Apple communication device I like to call Boris. He= nce the brevity and poor spelling.=20 On Oct 5, 2012, at 10:34 AM, Greg Balint wrote: > Thanks everyone for the help. >=20 > I ended up rendering everything out at PhotoJPEG 98%.. file-sizes went WAY= down and the client loves the quality.. plus!!!!!! it fixed/didn't show the= QT Gamma issue! So I'm now a big fan. My entire render folder was 5.59Gb.= vs nearly 25Gb+ previously. My client actually called to ask if it had a hi= ccup in the uploads because of how small the folder was. >=20 > Does anyone know a similar QT codec to PhotoJPEG that can do Alpha Channel= and doesn't disable MultiProcessing in AE like PNG codec does? >=20 > Basically I need an embedded alpha channel codec which looks pretty much u= ncompressed, 8-bit is probably fine, is useable with FCP on Mac and Premiere= on PC, and doesn't take up a TON of space like Animation codec does, which a= lso takes advantage of AE's MP capabilities. >=20 > ///Greg Balint > //Art Director / Motion Graphics Designer > /321.514.4839 > delRAZOR.com/=20 > On 10/5/2012 7:11 AM, Darren H wrote: >> Hi Greg, >>=20 >> The only difference is bit rate. HQ gives better quality at bigger file s= izes, though in some cases where I've compared frames, I've struggled to see= the difference. They're both 10bit.=20 >>=20 >> D.=20 >>=20 >> On Friday, 5 October 2012, Greg Balint wrote: >>>=20 >>> Can anyone, off hand, tell me what the diffs are between HQ and non-HQ? >>>=20 >>>=20 >>> ///Greg Balint >>> //Art Director / Motion Graphics Designer >>> /321.514.4839 >>> delRAZOR.com/=20 >>> On 10/4/2012 7:54 PM, Gary Berendsen wrote: >>>> I've been haing that as well, since cs6, well 5.5 as well. = =20 >>>> prores non hq solved it for me. >>>>=20 >>>>=20 >>>> Gary Berendsen - VFX Generalist >>>> Czaar Peter Straat 157-159 >>>> 1018 PJ Amsterdam >>>> garyberendsen.com >>>> gary@garyberendsen.com >>>> +31614385398 >>>> skype: garyberendsen >>>>=20 >>>>=20 >>>>=20 >>>>=20 >>>>=20 >>>>=20 >>>> On Oct 5, 2012, at 1:52 AM, Brian Maffitt wro= te: >>>>=20 >>>>> I missed the detail about it showing up in the final edit. If that's t= rue, this is something else. >>>>>=20 >>>>> Brian >>>>>=20 >>>>>> Also this. I was gonna mention that. But if they see the shift in fcp= for final edit I guess it does matter. They can't just gamma shift it back?= >>>>>>=20 >>>>>> On Oct 4, 2012 7:46 PM, "Brian Maffitt" wro= te: >>>>>> Before you completely panic, I think you may be seeing a fairly well-= know Quicktime-on-Windows display bug. It only affects how the movie looks w= hen played in Quicktime, not when used in another application. Take a look a= t the same clip in VLC and see if it looks OK. >>>>>>=20 >>>>>> > Hey all, >>>>>> > >>>>>> > I'm running into some gamma issues or something, which I've never s= een before. >>>>>> > >>>>>> > I've previously had issue with the H.264 bug, where renders would c= ome out lighter, almost looking like their gamma was bumped up. I know what t= hat looks like and how to alleviate it. >>>>>> > >>>>>> > This however, is a completely different ball of yarn. >>>>>> > >>>>>> > Basically.. I can take a ProRes 422 HQ file from my client (who wo >=20 --Apple-Mail-AE0193F3-23C0-4E25-B0D6-CC476CCB1EBA Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 7bit
Well you mentioned PNG and that is my codec of choice when I get those colour shift issues and need uncompressed or alpha. Try rendering a PNG sequence or a QT with PNG as format

Sent from the ubiquitous Apple communication device I like to call Boris. Hence the brevity and poor spelling. 

On Oct 5, 2012, at 10:34 AM, Greg Balint <greg@delrazor.com> wrote:

Thanks everyone for the help.

I ended up rendering everything out at PhotoJPEG 98%.. file-sizes went WAY down and the client loves the quality.. plus!!!!!! it fixed/didn't show the QT Gamma issue!  So I'm now a big fan.  My entire render folder was 5.59Gb. vs nearly 25Gb+ previously. My client actually called to ask if it had a hiccup in the uploads because of how small the folder was.

Does anyone know a similar QT codec to PhotoJPEG that can do Alpha Channel and doesn't disable MultiProcessing in AE like PNG codec does?

Basically I need an embedded alpha channel codec which looks pretty much uncompressed, 8-bit is probably fine, is useable with FCP on Mac and Premiere on PC, and doesn't take up a TON of space like Animation codec does, which also takes advantage of AE's MP capabilities.

///Greg Balint
//Art Director / Motion Graphics Designer
/321.514.4839
delRAZOR.com/
On 10/5/2012 7:11 AM, Darren H wrote:
Hi Greg,

The only difference is bit rate. HQ gives better quality at bigger file sizes, though in some cases where I've compared frames, I've struggled to see the difference. They're both 10bit. 

D. 

On Friday, 5 October 2012, Greg Balint wrote:

Can anyone, off hand, tell me what the diffs are between HQ and non-HQ?


///Greg Balint
//Art Director / Motion Graphics Designer
/321.514.4839
delRAZOR.com/
On 10/4/2012 7:54 PM, Gary Berendsen wrote:
I've been haing that as well, since cs6, well 5.5 as well.
prores non hq solved it for me.


Gary Berendsen - VFX Generalist
Czaar Peter Straat 157-159
1018 PJ Amsterdam
+31614385398
skype: garyberendsen






On Oct 5, 2012, at 1:52 AM, Brian Maffitt <brian@totaltraining.com> wrote:

I missed the detail about it showing up in the final edit. If that's true, this is something else.

Brian

Also this. I was gonna mention that. But if they see the shift in fcp for final edit I guess it does matter. They can't just gamma shift it back?

On Oct 4, 2012 7:46 PM, "Brian Maffitt" <brian@totaltraining.com> wrote:
Before you completely panic, I think you may be seeing a fairly well-know Quicktime-on-Windows display bug. It only affects how the movie looks when played in Quicktime, not when used in another application. Take a look at the same clip in VLC and see if it looks OK.

> Hey all,
>
> I'm running into some gamma issues or something, which I've never seen before.
>
> I've previously had issue with the H.264 bug, where renders would come out lighter, almost looking like their gamma was bumped up. I know what that looks like and how to alleviate it.
>
> This however, is a completely different ball of yarn.
>
> Basically.. I can take a ProRes 422 HQ file from my client (who wo

--Apple-Mail-AE0193F3-23C0-4E25-B0D6-CC476CCB1EBA--