Export Module failure

[Christopher Baron]

I was recently getting the same error message every time I tried to render:

After effects error: Rendering error while writing to file “volume/” An output module failed. The file may be damaged or corrupted. (-1610153464)

I tried all the solutions recommended on this site and others to no avail.

What worked for me was changing the Output Device in the Video Preview Preferences to ‘Computer Monitor Only’. Back rendering again with out a problem.

I hope this helps!

[Chaz Newman]

I know this is an old post, but I wanted to add my experience considering we are still getting this error in CC 2014. After much headache and cursing, it appeared to be an effect only supported in 8bpc (Motion Tile, I was in 16). I do believe the error can stem from an array of variables, but in this case killing off that effect cured the error. Just something to consider!

[Boris Bab]

Try converting the wavs to aifs

[Nestor Yanani]

don’t brake you head any more
gate the upgrade here and you will be fine

https://www.videocopilot.net/support/updates/

Twitch Version 1.3 For Mac AE CS6 & CC
August 22nd, 2012
Mac OS
This is a compatibility update for AE CS6 & CC on Mac
For AE CS6 & CC Only

AF CC 2014 is working fine too

work fine for me

[Eric Shawn]

I’m going to explore this. I get the Output Module Fail error message too. But it seems to be only when I have Audio selected in the output module settings in render queue. If I keep it off, I have no issues with rendering. My project has audio, and requires it turned on. So I’m at an impasse.

MacPro3,1 OSX 10.8.5 10GB ram 4x 2TB HDD 256MB ATI Radeon HD 2600

[Ken Olson]

I just thought about it and I had downgraded to an older version of Quicktime pro, so I updated it then went back tried to render same comp in quicktime format and no errors worked perfectly. hope this helps.

[Kevin Mckeever]

Some fixes are easier than others. I was getting the error message for every comp I tested, even a simple text-only comp. Turned off computer, turned it back on. Everything works now. Nice to have an easy solution once in a while.

Kevin McKeever | Director of Photography and Editor | http://www.image-generation.com
Sony FS7, Canon L lenses, full lighting and audio packages

[Pedro Romero]

I found the solution:
Before exporting do the following:
1- Click on “composition / Pre-render / output module”
2 – Select format QuickTime, etc.etc.
3- Do not export the video. Save the project and close After Effects.
4- Now, open After again and open your project.
5- Open “Render Queue” / export in .mov or H-264.
Yeeeeesssssss!!!!

[Bryan Root]

I struggled for hours with AE cc2017 trying to render a sequence at 3840 X 2160. I have a mid-2012 MacPro with 48GB ram and my GPU is an NVIDEA Quadro. I could render the sequence out at 1920X1080 just fine. I could render other sequences out at 3840 X 2160. It was just this one sequence that had a lot of large still images in it and nested sequences for which I’d created 1/2 res proxies.

I thought, silly me, that if I just selected “use all proxies” or “use current settings” in the render settings tab of the AE render cue that I would be taking the strain off my machine for rendering all those complex effects in the nested sequences. I created lots of half rez proxies (which I could live with) and I made sure they were all enabled in the project window, but there just was no getting the sequence to render to 3840.

What finally solved my problem was finding the proxy files I’d created (right click on the proxied comp in the project window and select “reveal in finder”) and import the proxies and replace the nested comps with these proxies physically in the final comp. A sort of “ignoramus’ prerender” workaround, but it worked and I was finally able to render out at my desired resolution.

I suppose PRERENDERING that which you were using PROXIES for is the answer. Proxies seemed to muck up my render cue. Once I did that I was also able to render using Adobe Media Encoder which is much prefered.