From: Todd Kopriva <kopriva@adobe.com>
To: After Effects Mail List <AE-List@media-motion.tv>
Date: Mon, 5 Aug 2013 15:11:07 -0700
Subject: RE: [AE] Ae 12.0 Mac getting import error again
Thread-Topic: [AE] Ae 12.0 Mac getting import error again
Thread-Index: Ac6SKCKJhBWmvgn6Q8eBvCczW/rw/AAADH8g
Message-ID: <B006868B2420FA4F88AB29E127AA783D4A588305E4@nambx09.corp.adobe.com>
References: <list-5167068@media-motion.tv>
In-Reply-To: <list-5167068@media-motion.tv>
Accept-Language: en-US
Content-Language: en-US
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

Yes, Tim Kurkoski is digging into this on the Adobe user-to-user forum. Ple=
ase share your details with him.

We do have a set of fixes in the works for our releases that we're targetin=
g for later this year.

> -----Original Message-----
> From: After Effects Mail List [mailto:AE-List@media-motion.tv] On Behalf =
Of
> Jim Curtis
> Sent: Monday, 05 August 2013 15:07
> To: After Effects Mail List
> Subject: Re: [AE] Ae 12.0 Mac getting import error again
>=20
> Thank you for that link, Todd.  I skimmed the thread.  Oy.  This is major=
ly bad
> news.
>=20
> On the advice on the forum, I reinstalled the Apple codecs, which similar=
ly to
> the experience of others, fixed the problem for about five minutes, then =
the
> footage started getting rejected again.
>=20
> I zipped then trashed the DVCPROHDVideoOutput.component, and that
> worked for about five minutes, too.  Then... 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
> 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've 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.
> >
> > See this thread:
> > http://forums.adobe.com/message/5559730#5559730
> >
> > +---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>