Content-type: text/plain; charset=windows-1252
MIME-version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: [AE] Ae 12.0 Mac getting import error again
From: Jim Curtis <jpcurtis@me.com>
In-reply-to: <list-5167068@media-motion.tv>
Date: Tue, 06 Aug 2013 11:09:15 -0500
Content-transfer-encoding: quoted-printable
Message-id: <59E6939B-9B6A-47DC-8EAE-0404B6BAFEBA@me.com>
References: <list-5167068@media-motion.tv>
To: After Effects Mail List <AE-List@media-motion.tv>

Following up on this thread.  FIXED!

My import error was indeed related to the DVCPROHDVideoOutput.component =
in the root/Library/Quicktime folder.  Destroy that file, and issue is =
banished.

(I had reported that trashing it didn't work, but that was before I =
emptied the trash.  Taking that next step was crucial.)

Thanks again, Todd, for pointing me in the right direction.

And thanks to Ren=E9 Hedemyr, for hosting the list.   I need to thank =
him periodically, as this list is so very valuable to me.  And I thank =
all my fellow listers, too, for your valuable input, wit and company.


Jim Curtis


On Aug 5, 2013, at 5:06 PM, Jim Curtis <jpcurtis@me.com> wrote:

> Thank you for that link, Todd.  I skimmed the thread.  Oy.  This is =
majorly bad news.
>=20
> On the advice on the forum, I reinstalled the Apple codecs, which =
similarly to the experience of others, fixed the problem for about five =
minutes, then the footage started getting rejected again. =20
>=20
> I zipped then trashed the DVCPROHDVideoOutput.component, and that =
worked for about five minutes, too.  Then=85 kablooey.
>=20
> I'm stumped as to why the "now you see it; now you don't" nature of =
this bug.  Certainly that must be of some significance to your =
engineers, no?
>=20
> Luckily for me (us), I can open the project and Save As CS6.  I just =
got a new project with a new (and potentially big) client today, and =
their footage is mostly DVCProHD and ProRes, and their template was =
AeCC. =20
>=20
> I would had been in deep jeopardy of losing this client and project if =
I didn't have CS6 already.  Woe are your new customers.
>=20
> I guess I'll take my voice in the discussion to the Adobe forum, =
because it appears there are some Adobe people looking into it over =
there.
>=20
> Thanks again,
> Jim
>=20
>=20
>=20
>=20
> On Aug 5, 2013, at 2:50 PM, Todd Kopriva <toddkopriva@gmail.com> =
wrote:
>=20
>> We=92ve been tracking down this problem, and it appears to be because =
of
>> a conflict between After Effects CC (12.0) and a specific version of
>> the QuickTime DVCPRO components from Apple video applications (FCP,
>> Motion, Compressor). Just the 2009 versions of these components,
>> though, so it appears that updating them is fixing the problem for
>> folks.
>>=20
>> See this thread:
>> http://forums.adobe.com/message/5559730#5559730
>>=20
>> +---End of message---+
>> To unsubscribe send any message to <ae-list-off@media-motion.tv>
>=20
>=20
> +---End of message---+
> To unsubscribe send any message to <ae-list-off@media-motion.tv>