| ||||||||||
| Thank you for that link, Todd. I skimmed the thread. Oy. This is majorly bad news. 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. I zipped then trashed the DVCPROHDVideoOutput.component, and that worked for about five minutes, too. Then… kablooey. 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? 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. 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. 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. Thanks again, Jim On Aug 5, 2013, at 2:50 PM, Todd Kopriva <toddkopriva@gmail.com> wrote: > 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> |
