What version of AE and what OS down to the last decimal point?
Outputting Quicktime to h.264 is buggy and should not be done. Have you considered using the Adobe Media Encoder by dragging your completed comps in a render comp? Even when using the Output Module, this is a better and faster to render option than resizing the comp in the output module.
The most likely culprit is the h.264 Quicktime. It should have never been included as an option. It doesn't even work well in Quicktime Pro or in Final Cut...
After Effects version 220.127.116.11
Windows 7 64-bit
Ah, I never knew about the h.264 in quicktime being so buggy, thanks for the heads up. And with that new knowledge, I tested multiple output modules with quicktime using ProRes 4444, and it worked perfectly! (for those wondering how to get ProRes encoding on Windows, use this: http://www.miraizon.com/products/codecsoverview.html It's the greatest thing since sliced bread!)
>The most likely culprit is the h.264 Quicktime. It should have never been included as an option. It doesn't even work well in Quicktime Pro or in Final Cut...
I'll come to Apple's (partial) defense here:
Their H.264 codec was written and released at a time when it was difficult to imagine that mainstream computers would have as many CPUs as they do now, so it's somewhat understandable that the severe failures that this codec has with large numbers of threads occurs. Of course, we may all wish that Apple hadn't decided to end development on the QuickTime platform, since this has meant that bugs like this are likely to persist.
That said, this is why we increasingly recommend that people use other H.264 codecs and not use QuickTime for such things. See the H.264 options currently in Adobe Media Encoder.
Necro-ing this old thread because I've just had a similar run-in with the 'ole "output module failed" error, but under different circumstances.
This time, I wasn't using the mov h.264 exporter, I was using MOV with the Miraizon ProRes encoder (I'm on Windows). Usually it works without a hitch, but today I just couldn't get it to work at all. I ended up rendering out a PSD sequence, but even then it STILL wouldn't let me convert that to a pro-res sequence. What's also strange is even after it failed, the silly QT32 Server held onto the file -- I couldn't delete it short of closing out of After Effects!
I don't have any repro steps... yet... but I was just wondering if anybody else has run into this problem before. I hope it's not a problem with Miraizon...
I am suddenly having a horrible time with this today using Miraizon to convert to ProRes 422.
Never had the problem before, worked for me for years, then for no reason random files just won't write to ProRes - did you find a solution for this?