See the part on this page about the QuickTime H.264 codec failing with a large number of threads:
Why are you using H.264 in a QuickTime container, anyway?
Todd thanks for your answer! A friend of mine pointed me to that page as well and I was able to diagnose the issue. Turns out it was a third party application called AirServer that apparently had the TCP conflict mentioned in your link.
I checked the Console and was able to find a message leading me to confirm the Adobe QT32 Server was crashing. After scanning Activity Monitor for other apps using the same port my eye caught AirServer.
AirServer turns the Mac into an AirPlay receiver from an iOS device, so it makes sense that it's using QT over TCP.
So, quitting AirServer completely resolved the issue and I'll be letting their developers know. Didn't even have to uninstall, it just couldn't be running when you launch AfterEffects.
It's just strange to me that this doesn't affect AfterEffects CS6.
Todd, as you can see I found the issue. Thanks again.
I'm curious why you question h.264 in a QT container? Would you recommend something like MP4 and if so, why?
Well, for one thing, there is the issue that I mentioned regarding the codec not being able to handle large numbers of threads (and therefore failing on many modern computers).
Also, there are many reports of bad results using this codec, including color shifts and artifacting.
This isn't a general complaint about QuickTime---just about this one codec, which is not Apple's strongest work.
In general, for H.264 export, we recommend using Adobe Media Encoder and its H.264 encoding presets. (Just make sure that you've installed the latest updates.)
I'm having the same error when I use Quicktime as render output. Sometimes it helps when I restart After Effects CC, but after one or two renders, the error returns. The condec doesn't make a difference, Animation, Apple ProRes, all having problems. Rendering as images sequences or MXF do work.
After Effects CS6 works great! No errors when using the Quicktime render output.
Hope someone can help me out with this. Thanks!
Apple Mac Pro 12-core 2,66 Ghz
32 GB Ram
Ati Radeon HD 5870 1024MB
No Blackmagic or Aja card installed
Olaf, did you read my reply where I explained my solution? First you should try the steps outlined in the article Todd references:
There seems to be a good way to isolate if it's the same issue I had, though. Let me go into a bit of depth for you.
The trick was to launch the OS X app called Console, located in Applications > Utilities. It is a program that compiles and displays the system logs in real time. It's great to see the little things happening in the system that don't make it into the user interface. When I had my Console up and generated that same error you're having, I noticed this error in the log:
The key here is the Adobe QT32 Server, which is mentioned in the TCP part of the article I linked to above from Todd. In my case at least, what was happening was that a third party app called AirServer was talking to the system's QuickTime over the same TCP ports the QT32 Server engine was trying, and it resulted in Adobe QT32 Server crashing, and that alert being thrown up in AfterEffects.
If you're in the same boat, it means you have some sort of app or system extension that is also talking to QuickTime over TCP. That may not make any sense, but the easy thing to do is quit ALL third party apps, then quit AE, then restart AE.
In my situation if AE gave me the error and then I quit AirServer, the error still happened because Adobe QT32 had already crashed. You have to relaunch AE after closing the offending third party app.
To be sure you've quit all third party apps, open Activity Monitor (Applications > Utilities), chose "My Processes" from the dropdown menu, and scan through the list to make sure. You don't have to recognize all the processes there, but you should be able to recognize any third party ones you put there.
Hope that helps!
Yep, I'm having the same issue. AE CS6 works fine, but the new version gives this bogus error message. Looks like Adobe needs to fix this bug with an update ASAP!
Had a similar issue recently - all of the sudden (maybe an adobe update), everytime i tried to render something in prores - i got the "output module failed" error message. although mdworker (OSX's indexing tool) used the same port, killing that task did not solve my problem.
in the end it turned out that i hadn't installed system-updates for a while (running a hackintosh - so i lean more towards the "never-ever change a running system" - philosophy). after installing the last version of the pro codecs from apple, everything went back to normal.
This fixed the problem on windows, Thanks to Rameez of Adobe to pointing it out.
He reported that Apple's Quick time peaks out at 12 processors (cores too) to you have to go into Msconfig.exe > Boot>Advanced options > change the cores to 12. You will have to restart and this solved my issue.
This problem happened when I installed After Effects CC 2015 a few days ago, on a Mac running OS X Yosemite 10.10.5.
This post from Todd Kopriva led me to a fix that worked for me: quitting AE, removing a DVD output component completely from my system, then restarting AE.
Scroll or search to "solutions regarding DVCPROHDVideoOutput QuickTime component from Apple" on that page.
Was grateful to find that tip! Half the day lost to this issue, but thankfully now resolved.