Try removing the DVCPROHD QT component. This looks very similar to an error I was getting in AE 12.0.
See this thread:
(Sorry, can't post a hyperlink for some reason)
Thanks for your response Graham. Seems I've stumped everyone else that's read it the post. I had seen that thread as well and tried removing all DVCPROHD components (and others listed above). I've also recently tried what I read in another thread, and used a time machine backup to restore only the components that were in the Quicktime folder before the errors started. Doing that did restore my XDCAM codecs that were messed up in Final Cut from removing too many components though. The errors mentioned in my post still persist.
The studio I work for is having this same issue and have not been able to solve for 3 months or sense we started subscribing. Support could not repair either taking me through all the same steps as listed in the documents. I am paying for something that simply is not working on our system(s). Also does not function or will not launch on our utitlity MBP. This is a professional studio doing work on feature films and we will classify our subscription to CC as a loss on our taxes since we are unalble to get many of the apps, the ones we use the most, to function in any usable manner. Have not yet canceled but preparing to op for other compositing and editing tools due to these ongoing issues. We have a business to run. I have made calls and sent emails to no resolution. We feel very much like an steady and high level customer being completely ignored. Please post again if you come across any solutions to these issues. Thank you.
Side note: We haven't as of yet taken the system to scratch and done fresh installs with EVERYTHING. This will be our next attempt to resolve this issue. Optimistic none the less. Will report back (after the holidays) just in case others have had the same or similar issues.
Jon and DropFrame:
When you get these errors, open Activity Monitor to check if Adobe QT32 Server is running. If it's not, that is why AE is failing to read or write QT files.
Why is QT32 Server not running? There's a variety of reasons, which our blog posts attempt to address. The most recent wrinkle was the issue with QuickTime video out components, but it's not the only reason. In particular, we've also seen audio drivers bring down QT32 Server in the same way. A good troubleshooting step is to uninstall any audio drivers present (which may belong to applications you didn't think installed audio drivers, like certain screen sharing packages, so uninstall those).
If the troubleshooting steps we've posted aren't helping, it's time to dig deeper. Look at the most recent crash logs (instructions here: http://forums.adobe.com/message/5507834#5507834) for QT32 Server. Post them so we can look at them.
It's also possible QT32 Server may be running but not able to communicate with AE. Some of our troubleshooting steps target that possibility.
Thanks for your response. QT32 Server is dissappearing from Activity monitor as the errors start. Checking the error log, I noticed that Flip4Mac was causing an error. (I had restored the QT folder from a time machine backup to get Final Cut working again). However removing it again, only helped clean up the QT32 log, didn't help with the AE errors.
I'm not sure how to check for audio drivers.
I've looked through the links and where they lead as well (many at this point lead to the ones I've listed above). Much of that I had read already several times. I've been in business for 12 years and this is the most time I've spent trying to fix software problems.
Here's the error log
Thanks for the file but I'm afraid it's not helpful. What would be useful is the log from Adobe QT32 Server, as that's the application which is crashing. You should be able to find the crash logs in:
The System Information app will show you a list of installed audio devices/drivers. You can also view the same thing in the Audio Midi Setup app. Both are located in Applications/Utilities. If there are any odd devices, such as SoundFlower (used by iShowU and other applications), try uninstalling those.
I'm not seeing a Adobe QT32 Server file in /Library/Logs/DiagnosticReports. Also I don't appear to have any audio device drivers installed...
System Information app under Hardware / Audio (Built In) is just "Intel High Definition Audio," under which it names my various ports in the computer, headphone, line input ect.
Audio Midi Setup has built-in in & outputs as well as a number of Adobe Encore, AE, and Premiere device lists, one per version of software ever installed by the look of it. Clicking on the Adobe lists just bring up the built in's.
Make sure that you're looking at the Library folder in your user folder, not the Library folder on the drive root.
Keep in mind that by default, Mac OS hides the user Library folder.
Thanks for the file. QT32 Server is crashing on a call to com.apple.QuickTimeComponents.component, and if I'm reading this correctly it fails while enumerating a QuickTime component.
Empty your Library/QuickTime components folder completely. Drag all of the files out to a folder on the desktop to back them up, and then delete them from the original folder. Maybe take a screenshot for us first so we can see what you've got.
If this works, start putting the components back one by one until the problem recurs. Keep in mind that there could be more than one bad component, so keep putting them back one by one even if you find a culprit.
This log is nearly identical to the last.
Please provide screenshots of the following folders:
Try deleting any QuickTime-related files in Users/username/Preferences.
And just to see what happens, create a new user account and test the problem there.
A closer look at the log with one of our developers shows that the crash occurs when trying to read the timecode from one of the files.
I re-read your original post and want to clarify a few things:
- Does this only happen when you open the specific project in question?
- Can you import the QuickTime files from that project into a new project?
- Can you import the problem project into a new project?
If this problem is truly only a single project, it may the project itself that is feeding bad information back to QT32 Server. We should troubleshoot the project in that case.
I didn't know about the System/Library/Quicktime folder, here's everything from both folders... even those that I've tried removing. I didn't see any QT files in the User/Username/Preferences folder, perhaps I'm not looking correctly. I have yet to create a new User acct.
I'm able to bring in two that are on the error list in my project, currently the rest of them that are ProRes 4444 I'm not able to bring into new projects either. And I get more errors when I tried to bring the project into another project. I thought at one point that I was able to bring the ProRes files into a different project, but not now.
Would you be willing to share one of the problematic files with me so I can take a look at it? If you don't want to share it with the world, send a link directly to me. My e-mail address is formatted as: myLastName-at-adobe-dot-com
I've setup a new user acct, and the errors are present there as well. Test file is coming...
I've got the file. Looking at it now, but it's not causing failures for me.
What is different between the files that are working and the files that aren't? Codec? Presence of alpha channel? Drive or file location?
The crash in QT32 Server is when it reads timecode. I note that the timecode on the file you sent starts at 1;00;00;00. That isn't a problem, but is that the expected timecode? Is that different than the files that are working?
Also, the file you sent me did not have the .mov extension. I had to add that, otherwise AE won't recognize the file you sent me. Even if I force AE to try to read the file, it fails, though it does not crash QT32 Server. Does the file lack the extension on your machine? Does the problem go away if you add the extension?
Also also, if you import this file into Premiere Pro do you experience the same problem?
When I open the project and others with the same files in it, there's 13 files that it said are missing (I get that many missing or damaged errors as well). But I'm able to find and play them from the Finder. I at one point ran new versions of the files incase they were corrupt, which had no effect. That was when I had cloned the drive and replaced it incase that was the problem.
In a new project I'm currently able to bring in the same file type, also with alpha channel, even from the same same hard drive folder, created at the same time. I can even play the files in AE. But when I add to a comp, I get the (86:2) error. As far as bringing the 13 files mentioned above, they are not importable. The file I sent is one of the 13.
All time-codes would start with 1 hr, because they're all output in Compressor from FCPX.
I was able to finish 12 videos using these same files, even the ones giving import errors currently. Adding a file extension does not reduce the errors for me. Maybe that's a mac thing? Are you on a PC?
I'm able to successfully import the file you gave me on Mac 10.8.5 and 10.7.5. Haven't yet tried it on Windows.
Does Premiere Pro give you errors with these files?
No problems in Premiere. That's weird that you got errors only until you added the .mov since that's not been a factor here.
Sorry for the slow reply. We were busy releasing the After Effects CC (12.2) update.
I am a bit stumped with your problem right now. I recommend uninstalling and reinstalling After Effects CC. (Uninstall by going to Applications/Utilities/Adobe Installers. Reinstall by quitting and restarting the Adobe Creative Cloud manager application, or reboot.)
I uninstalled, shut down the computer. Opened Adobe Creative Cloud manager and installed AE v 12.2. Exactly the same errors.
I received your additional crash logs. Thank you.
All of your crash logs for QT32 Server are the same: the crash occurs when it tries to read the timecode of a file.
I would like to know what application you used to generate these files, and what settings you use. I'd also like to see more of the files, if you wouldn't mind sending them to me.
At this point the situation is unclear, because the one QuickTime file you sent me works on multiple machines in my office.
However, because I have to take the extra step of adding the file extension, something you don't have to do on your machine to make the file work, I remain suspicious of these files.
In order to be of additional help, I need to very specifically know:
- Does the problem occur with ANY QuickTime file? For example, if you create a new comp in AE with nothing but a text layer, and render that out to QuickTime, does the problem occur with it?
- Or does the problem only occur with certain QuickTime files? If so, what is common about these files? Where did they come from?
Here's what I'm thinking: we're looking at one of two different troubleshooting paths. Either there is something about your files that is causing QT32 Server to crash, or something in QuickTime on your system has broken and is causing the crash. Since you're experiencing the problem on more than one computer, I suspect the former but can't rule out the latter (especially if you tend to configure both computers in the same way).
If you are stuck in your work, my recommendation is to transcode these files to a different format. That may mean QuickTime with a different codec, or to a different format entirely like a TIFF sequence with alpha.
All files for the project are batch encoded to ProRes 4444 from Final Cut 7. They worked long enough to finish 5 videos completely in the spring, then get another 6 built for client review. At that point, they all stopped working. Old projects with these files have the problem now. It seems that many of the files work fine in a new project in AE, but when one file has the error the rest start having it too. Possibly because QTServer is crashing?
1. In the last couple months that these projects have had problems, I've successfully modified VideoBlocks.com templates and output them.
2. As far as differences between what's working and not working, I've not determined any differences. They are the same format, made at same time, and often same batch. I've put a couple more files and a crash log up and sent you a link. I thought if I moved the first files that had the error, that it would help but that didn't appear to be the case. Maybe the error reads differently now though. It's somewhat of a break through that at this point all the video files are going offline, and the errors don't keep coming. The possibility of going through and replacing all the files is now an option. And for the videos I haven't started yet, I can try the tiff sequence.
At the moment the project is working! I guess by moving the first 3 files to a different folder that were having the error, and restarting... QT32Server can stay running. The problem is I thought I tried all that last night, and it didn't work. For now I'm going to enjoy the moment.
Glad to hear that it's working. Post back if it fails again.
Yes, the fact that QT32 Server is crashing will cause all QuickTime files to fail in AE. This is why I've been trying to understand whether only specific files, or a specific class of files, are causing you the problem.
The latest crash log you sent shows exactly the same failure, a divide-by-zero error when reading timecode from the file. The movie files you sent are working for me, in the same way as the last file: I have to add the .mov extension in order for AE to even recognize them, and then they work without problem. (One of our developers told me that this means the files lack the resource fork, which is an old but still-valid remnant of Apple's pre-OSX file system. That's fairly odd, especially if the files came from Final Cut.)
From where did you move the files, and where did you move them to? If this makes a difference, combined with the oddness of me having to add an extension when you don't, my concern would be that something in your file system is to blame.
I am also curious if new files, or re-exporting these same clips, from Final Cut will exhibit the problem.
There has been no apparent difference between the files that cause the problem and don't. I believe that the first file that I sent is the main culprit. We just don't know why. I'm fine with replacing one file with a different codec, it's just the 100 files that I didn't want to have to replace in the work that was already done. All 3 files I sent are ProRes created by FCP 7. One of the first things that I had tried replacing all 13 that I thought were not importing right. (turns out it only takes one to make the rest fail.)
All the files I'm using are on the client drive in a Footage folder, with all the clips in folders separated by Product. Within this product folder, for this test that became the ultimate fix, I made another folder called "hide" and put the first three files that brought up the "Moov file is damaged or unsupported". My theory was that it would start with the next 10 errors, but instead everything started working. My guess now is that it's the first file I sent which was the first file to give an error every time I opened the project.
Interesting; this would point to that single file being bad.
Just remember that any time you get that error, check to see if Adobe QT32 Server is active in Activity Monitor. Presuming not, since it is crashing in this case, you need to quit and restart AE in order to perform a valid test on the next file.