From: "Robert Kjettrup" Received: from mail-lb0-f173.google.com ([209.85.217.173] verified) by media-motion.tv (CommuniGate Pro SMTP 4.2.10) with ESMTP-TLS id 5564708 for AE-List@media-motion.tv; Thu, 04 Sep 2014 19:36:11 +0200 Received: by mail-lb0-f173.google.com with SMTP id c11so11999030lbj.32 for ; Thu, 04 Sep 2014 10:36:12 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:content-type; bh=dQGlitXbOlz9JDaUiDDQ28U0FBMgdHk9DNEZlC/H9ug=; b=bkRglI2fQaHPwiwbZPQSQ5DOKUgOVjZzfxGsMIUIFE0J0lbkUSE8nsSrfno2q+OT0n hIf7XJ6m8ilJmAlSb398TXoBaW4XQ650ejysIS6YwWB5Xxlps47fpqL8jG0OziTIL+vs 1nlZ4/7J5+cziTrB782uQes8LtaywZcJfaCShSy9ttY+KKIUZGJP4GL8sAHeIxt/4gik SUAS+/cceKq5GsWmiG47qIjIyigr07UPesrrn5IWdwGIEbKIP/NTP2QTfOxoTdOwLl6h t5TceqB/Z4TdHQUpg+Qqne0dogzCjfrm/JBo2vFZyBEPercA6PokyHJwmJ1xqpSBQQYq g4GA== X-Gm-Message-State: ALoCoQnp47/ThI3MBJMPoGAUM3KaCVftTOUrekdctFvI9umiGozPkDZqQpLrSCwWqcIOo2C1XzOV X-Received: by 10.152.2.100 with SMTP id 4mr4195145lat.48.1409852171942; Thu, 04 Sep 2014 10:36:11 -0700 (PDT) MIME-Version: 1.0 Received: by 10.25.208.135 with HTTP; Thu, 4 Sep 2014 10:35:51 -0700 (PDT) In-Reply-To: References: Date: Thu, 4 Sep 2014 19:35:51 +0200 Message-ID: Subject: Re: [AE] Compression issues article To: After Effects Mail List Content-Type: multipart/alternative; boundary=089e013c65c2e50ced050240c98e --089e013c65c2e50ced050240c98e Content-Type: text/plain; charset=UTF-8 > Interesting. One issue I would anticipate is that H.264 is typically > 4:2:0, so if you save in another YUV format, FFmpeg would have > to convert it, possibly by converting back to RGB. I would hope > there was some 4:2:0 YUV format that wouldn't involve those issues, > but I don't know. > > Brendan Doesnt an encoder need to full decode the file and get an RGB image before re-encoding it again? That is what i was thinking and caused the colorshift i was seeing, that FFmpeg did a "wrong" YUV -> RGB conversion. Maybe it is possible to keep it in keep it in YUV space without the color conversion, it should be when i think about it. It has been a while since i tested this, and some things might have been improved with newer versions of FFmpeg. But i did test Uncompressed YUV, ProRes HQ and DNxHD 185, and they are all in YUV 4:2:2 and all showed colorshifts. FFmpeg wouldnt read DNxHD 444 or ProRes 444 so i couln't check those, but it might be able to now, dont know. I think DNxHD444 is RGB, but ProRes444 is still YUV??? So it could be interesting to test those again if they are read now. Robert --089e013c65c2e50ced050240c98e Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
> Interesting.=C2=A0 One issue I would anticipate is that H.264 is typi= cally=C2=A0
> 4:2:0, so if you save in another YUV format,= FFmpeg would have=C2=A0
> to convert it, possibly by converting back to RGB.=C2=A0 I would = hope=C2=A0
> there was some 4:2:0 YUV format that wouldn't= involve those issues,=C2=A0
> but I don't know.
=
>
>=C2=A0Brendan
=
Doesnt an encoder = need to full decode the file and get an RGB image before re-encoding it aga= in? That is what i was thinking and caused the colorshift i was seeing, tha= t FFmpeg did a "wrong" YUV -> RGB conversion. Maybe it is poss= ible to keep it in keep it in YUV space without the color conversion, it sh= ould be when i think about it.

It has been a while since i tested this, and some thing= s might have been improved with newer versions of FFmpeg. But i did test Un= compressed YUV, ProRes HQ and DNxHD 185, and they are all in YUV 4:2:2 and = all showed colorshifts. FFmpeg wouldnt read DNxHD 444 or ProRes 444 so i co= uln't check those, but it might be able to now, dont know.
I think DNxHD444 is RGB, but ProRes444 is still YUV??? So it could be = interesting to test those again if they are read now.

<= div>Robert



--089e013c65c2e50ced050240c98e--