From: "Phil Spitler" Received: from mail-pd0-f178.google.com ([209.85.192.178] verified) by media-motion.tv (CommuniGate Pro SMTP 4.2.10) with ESMTP-TLS id 5511924 for AE-List@media-motion.tv; Fri, 27 Jun 2014 05:56:09 +0200 Received: by mail-pd0-f178.google.com with SMTP id r10so3862713pdi.23 for ; Thu, 26 Jun 2014 20:56:07 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:mime-version:content-type:subject:date :in-reply-to:to:references:message-id; bh=3eU+S/twmFRolkX200+Kj/O+AIrez4WjmAM6wbhuURA=; b=LIB5ArjdDhF+QZVYXR7LV3hQ6ajqTY/OBl9Qo6eQxe58Ecy0ql+pGKaalcRgmuIoO0 29y0aWnGe0vp/HU9ieQxwWjTXUM30KgfP/7huW6tByjJN2U6YUXipmGo2g4RNkG2TZnv ENLi54hp7r8mbRg6jnYNaEEJ0MgDDw14GCZBABRF5zyNQSdi1VrwT/AhMM72FD2+eI5F PpQzaiWdhNtT8owBBBl7Xudm4FgWDNJ3vL3X4hX/HTR7efJPWiJrJ+P7kWkOvvZ5SP77 lTIq3vcNddBCgtxKS5Tt+Q8O5NiYgnGUYBG1oBnM1ogXs9JcaacSTJpsZDx3TzN+5+Tx 8Y1w== X-Gm-Message-State: ALoCoQkgyOnrufe/0WnxkLdyXtxlfm1coLEgB7AwkWIn5g5LW5gaI00Pi/bB1pIMHnJ79EFiKqUC X-Received: by 10.68.202.194 with SMTP id kk2mr26879460pbc.156.1403841367756; Thu, 26 Jun 2014 20:56:07 -0700 (PDT) Return-Path: Received: from [10.0.1.25] ([12.252.143.102]) by mx.google.com with ESMTPSA id rm9sm44455576pab.4.2014.06.26.20.56.06 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 26 Jun 2014 20:56:07 -0700 (PDT) Mime-Version: 1.0 (Apple Message framework v1283) Content-Type: multipart/alternative; boundary="Apple-Mail=_C52789E3-A2B9-4146-96AD-7ADC0D1F300B" Subject: Re: [AE] QT Weirdness Date: Thu, 26 Jun 2014 20:56:05 -0700 In-Reply-To: To: "After Effects Mail List" References: Message-Id: X-Mailer: Apple Mail (2.1283) --Apple-Mail=_C52789E3-A2B9-4146-96AD-7ADC0D1F300B Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii I copied the codec from 1 machine to the other and still had the same = issue. I also verified they were running the same version of both QT7 = and QTX. Also, for more confusion if I open a "non optimized" render in QT7 on = the same box that rendered it then export it back as ProResHQ it is = suddenly ok and imports without error. Phil Phil Spitler | Creative Technologist | Bonfire Labs | t : = 415.394.8200 m : 415.571.3139 Website | Facebook | LinkedIn On Jun 26, 2014, at 8:36 PM, Warren Heaton wrote: > Ohhh... So, on the same FCP machine you will get the message on an = Apple ProRes file rendered on AE box 1 and then not on an Apple ProRes = file rendered on AE box 2 (at the same setting as box 1). >=20 > Okay, that just clicked.=20 >=20 > This is a wild guess: know the Apple Pro codecs updates that show up = in Software Update now and again? Has that been updated on some = machines but not others? =20 >=20 > Or, have you been able to compare the QuickTime components of each AE = machine? =20 >=20 > I'd suspect that it is something on the QuickTime side. >=20 >=20 >=20 > -Warren >=20 >=20 >=20 >=20 > Sent from my iPhone >=20 > On Jun 26, 2014, at 1:43 PM, Phil Spitler = wrote: >=20 >> Yup, I can get rid of the warning but would love to know why I get = warnings when rendering from one box but not the other. >>=20 >> Thanks >>=20 >> Phil >>=20 >> Phil Spitler | Creative Technologist | Bonfire Labs | t : = 415.394.8200 m : 415.571.3139 >>=20 >> Website | Facebook | LinkedIn >>=20 >> On Jun 26, 2014, at 1:41 PM, Warren Heaton = wrote: >>=20 >>> Hi Phil: >>>=20 >>> It's probably just the preferences setting for "Warn when importing = non-optimized media". >>>=20 >>> You'll find it under Final Cut Pro > User Preferences > General (2nd = row, 8th item down). >>>=20 >>>=20 >>>=20 >>> -Warren >>>=20 >>>=20 >>>=20 >>>=20 >>>=20 >>>=20 >>> On Jun 25, 2014, at 3:53 PM, Phil Spitler = wrote: >>>=20 >>>> The problem is that I get a warning when importing into FCP that = the file isn't optimized. >>>>=20 >>>> It still looks fine but I just don't like seeing this warning and = I'm curious...=20 >>>>=20 >>>>=20 >>>> Phil >>>>=20 >>>> Phil Spitler | Creative Technologist | Bonfire Labs | t : = 415.394.8200 m : 415.571.3139 >>>>=20 >>>> Website | Facebook | LinkedIn >>>>=20 >>>> On Jun 25, 2014, at 3:48 PM, Dirk de Jong = wrote: >>>>=20 >>>>> On Wed, Jun 25, 2014 at 3:40 PM, Phil Spitler = wrote: >>>>>=20 >>>>> If I bring the 2 different QT files into AE they are identical = (compared using difference mode). >>>>>=20 >>>>> then what exactly is the "problem" ? seems like more of a = curiosity than a problem... you think you got problems ? : ) >>>>=20 >>>=20 >>=20 --Apple-Mail=_C52789E3-A2B9-4146-96AD-7ADC0D1F300B Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii I = copied the codec from 1 machine to the other and still had the same = issue. I also verified they were running the same version of both QT7 = and QTX.

Also, for more confusion if I open a "non = optimized" render in QT7 on the same box that rendered it then export it = back as ProResHQ it is suddenly ok and imports without = error.

Phil


Phil Spitler  |  Creative = Technologist   |  Bonfire Labs  |  t : = 415.394.8200  m : 415.571.3139

Website | Facebook | 
=


On Jun 26, 2014, at 8:36 PM, Warren Heaton wrote:

Ohhh... So, on the same FCP machine you will get the = message on an Apple ProRes file rendered on AE box 1 and then not on an = Apple ProRes file rendered on AE box 2 (at the same setting as box = 1).

Okay, that just = clicked. 

This is a wild guess: know the = Apple Pro codecs updates that show up in Software Update now and again? =  Has that been updated on some machines but not others? =  

Or, have you been able to compare the = QuickTime components of each AE machine? =  

I'd suspect that it is something on the = QuickTime = side.



-Warren
=




Sent from my = iPhone
Yup, = I can get rid of the warning but would love to know why I get warnings = when rendering from one box but not the = other.

Thanks

Phil
<= br>
signature1 Phil = Spitler  |  Creative Technologist   |  Bonfire Labs  |  t : 415.394.8200  m : = 415.571.3139

Website | Facebook | LinkedIn

On Jun 26, 2014, at 1:41 PM, Warren Heaton <AE-List@media-motion.tv> = wrote:


You'll find it under Final Cut Pro > = User Preferences > General (2nd row, 8th item = down).



-Warren






On Jun 25, 2014, at 3:53 PM, Phil Spitler <AE-List@media-motion.tv> = wrote:

The = problem is that I get a warning when importing into FCP that the file = isn't optimized.

It still looks fine but I just don't = like seeing this warning and I'm = curious... 


Phil
signature1 Phil = Spitler  |  Creative Technologist   |  Bonfire Labs  |  t : 415.394.8200  m : = 415.571.3139

Website | Facebook | LinkedIn

On Jun 25, 2014, at 3:48 PM, Dirk de Jong <AE-List@media-motion.tv> = wrote:

On Wed, Jun 25, = 2014 at 3:40 PM, Phil Spitler <AE-List@media-motion.tv> wrote:

If I bring the 2 = different QT files into AE they are identical (compared using difference = mode).

then what exactly = is the "problem" ? seems like more of a curiosity than a problem... you = think you got problems ? : )
=




<= /div>= --Apple-Mail=_C52789E3-A2B9-4146-96AD-7ADC0D1F300B--