Please read that post and let us know here on this forum thread if you have any questions or comments.
Also, please let us know if the proposed solution works for you.
Alas, getting rid of the mentioned quicktime component does not solve the problem for me. This has been extremely bad news for me, as I have a couple animation deadlines coming very soon.
Hope this gets fixed really soon.
This is a major problem.
Thank you for the quick reply.
The problem never occured before moving to CC.
• Quicktime is installed. All software on my machine is current. (Mac, btw)
• Conflict with DVCPRO. The component is removed from the Library
• Blockage of TCP. This, I have no clue how to troubleshoot this one.
• Failure of QT component. No 3rd party components installed. Only the Pro codecs from Apple
• AJA / Blackmagic. No 3rd party components installed
• Permission problem. All permissions have been reset
• Corrupt prefs. All Adobe prefs have been deleted and rebuild.
• Audio conflict. No special audio drivers installed.
• Failure because of inability to work with large nr. of processes. NA
This, potentially, leaves the TCP problem.
The problem is really QT related. Rendering a sequence works fine. It also occurs on variable moments. Sometimes before even the first frame. Sometimes about halfway. Sometimes, on a rare few occasions, the render succeeds.
Thanks for looking into this, and for your help
Mark - The new document that we published is meant to address a specific issue. You can confirm you have the issue by the following:
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0 ??? 0x04981f90 0 + 77078416
1 com.apple.audio.CoreAudio 0x949d05c1 __Call_block_invoke_03 + 56
2 libdispatch.dylib 0x94a90f8f _dispatch_call_block_and_release + 15
If this is not the issue you're having, please start a new thread and provide the usual data. If your problem does match this issue, please double-check that you've followed the steps in the new document and post back here.
Thank you, Tim,
the Crash report says nothing about CoreAudio. Can I maybe send you the crash report?
Feel free to post it so anyone can look at it. Again, please start a new thread to troubleshoot your specific issue. If the forum community and the troubleshooting documents are not leading you to a solution, or you need urgent one-on-one assistance, you can contact Adobe technical support.
Installing the Apple ProApps QuickTime Codecs 1.0.2 update (http://support.apple.com/kb/DL1396) fixed the problem for me.
Update: Not sure if it is related, but Adobe Media Encoder seems to be running much slower after running the update. My CPU used to almost max out and now it is only using about 35%. Also Adobe QT32 Server seems to be doing the heavy lifting. I think Adobe Media Encoder CC used to be the one using the majority of the processing power. I have a Cuda card and I assume Adobe QT32 Server is only 32 bit, hence the slowdown.
Didn't fix it for me, I'm sorry to say.
Still need to render out a sequence, and get that sequence in a Quicktime movie via a render module on another machine. With heavy projects, an extremely frustrating process.
Hi, i am running After Effects CC 12.1, on windows 8.1.
Up until few days ago no problem occured, until last night when i got this beautifull sucker. Nothing was installed or updated that could interfere with Quick Time
“file ‘[file name].mov’ cannot be imported – this ‘MooV’ file is damaged or unsupported."
And here we go with the list. Disabled my firewal, cleaned the preferences, checked the sound drivers. Still nothing.
The same problem i am getting while importing the file in Premiere CC and Media Encoder CC
Has anybody experienced that on Windows? Because i see many of you guys have these problems on Macs.
Thank you in advance
The thing that shocks me most is that this thing is not top on the priority list at Adobe. Because of this Quicktime incompatibility thing, I have to render out sequences and soundfiles for everything, and put them together in QT7. Very annoying deroute I have been forced to take a couple of months now.
> The thing that shocks me most is that this thing is not top on the priority list at Adobe.
Why do you say that?
We released an update three weeks ago that addressed this issue:
> the issues between QT and AE have not changed for me
Then it's a different issue than the one being discussed on this thread. Please submit a detailed bug report here:
If you want to troubleshoot here on this forum, then please start a new thread and give as much detail as possible, including answering all of the questions here: