Activity › Forums › Adobe After Effects › Export Module failure
-
Jeremy Allen
January 25, 2013 at 4:29 pmDid you transcode that 7D footage to something other than H264? I can’t guarantee that will fix your problem, and I haven’t used CS6 yet, but AE doesn’t usually like H264.
———————————————
8core MacPro, 3.0 GHZ, 18GB RAM, OSX 10.5.8C4D 12
AE CS5 (10.0.2.4)
FCP 7.0.3
QT 7.6.4 -
Zita Jett
January 28, 2013 at 7:47 amthanks for getting back to me, how exactly do i transcode the footage?
My composition preset is currently in “hdtv 1080 29.97”. im not too sure about the settings when it comes to rendering or importing. I still have not figured out the problem. -
Tùng Khỉ
April 22, 2013 at 9:53 amGuys! I logging in Creative Cow just for this post. The problem will solved perfectly if you update your plugin to the latest one. Simplicity click on” about” tab in your plugin/effect panel to see what’s its version. Then Google and download the latest one while AE is shutdown. Then install/replace the plug in and open AE and render again!!!!! SEE? IT”S WORK!!!!
— Crazy Monkey
– https://www.facebook.com/crazy.monkey.box -
Scott Douglas
June 6, 2013 at 6:25 pmI had a similar problem, one easy work around is to utilize dynamic link between AE and Premiere, if you’re familiar with Premiere. Simply open premiere create a timeline appropriate for what you want to render out of AE, then drop a pic or anything into that timieline, stretch it to the desired time, and send it to your AE project, then drop your comp into that new comp that AE just created, go back into PPro and export out of there.
I had an issue that AE wouldn’t render out the quicktime, the render bar didn’t even start, but I dynamic linked it in PPro, and it exported just fine.
Brand New Website UP! – scottkdouglas.com
-
Mike Woeppel
June 27, 2013 at 3:02 pmThis worked for me. I Updated my Magic Bullet Suite to 11.4.2. an it seemed to fix the rendering issue.
-
Jm Chadillon
July 25, 2013 at 12:43 amMight be raising a thread back from the Dead but I just had this problem. AE was saying failed at whatever time. When I looked at that specific frame there was actually nothing happening. Just background precomp with solids inside and thats it. The error was failing out one frame before another precomp kicked in with some pretty heavy effects. So my first conclusion was AE doesn’t always give you the exact frame error. I only thought this because maybe AE was pre calculating it.
Turns out I had RSMB in that precomp and RSMB applied to my root composition. RSMB + RSMB = fail.
It was hard for me to pinpoint the problem because prior to the time above I was rendering out 15fps so the time that it errors out isn’t the same as the actual frame causing the problem.
I hope this helps someone.
-
Steve Lucin
October 10, 2013 at 12:56 pmWhat solved it for me was making sure that the audio (which was a WAV file) being rendered was set to something else other than uncompressed. I switched it to AAC and it worked! I am working with After Effects CC.
Good luck!
Steve Lucin
CEO, Creative ProfessionalHalucinated Design, Inc.
Halucinated.com | @Halucinated -
Pryce Duncalf
November 11, 2013 at 12:28 pmHi. I honestly can’t believe how long this thread has gone on for. I have had this error message come up:
After effects error: Rendering error while writing to file “volume/” An output module failed. The file may be damaged or corrupted. (-1610153464)
I am using CC and I have just updated to osx mavericks. The problem started happening, but occasionally on restarting the application, it worked, but not if I set up a new render. The problem has become more and more frequent, till I can’t render anything. Even a comp with a black solid in it.
Things I have tried:
clearing Disk cache
cleaning database and cache
restarting everything
Switching off all plugins
Changing audio format
Changing output formats. This works as image sequences, but its not a solution. I have to reopen and export from quicktime every time I render.I attempted to open it in a previous CS, but previous versions don’t open in osx mavericks. Another reason to move to PC.
Anyone had any other ideas?
The problem must lie within quicktime? Has anyone brought it up with apple? I am going to send them this thread and see if I can get anything back.
Thanks Everyone. P.
-
Will Giuliani
January 23, 2014 at 4:18 pmFor what it’s worth…
I was having this exact problem with After Effects CC at render time. Running the Console app on my mac (applications- utilities- console) I noticed a crash report. According to that crash report- something had caused the Adobe QT32 Server to crash. A google search showed that blackmagic drivers could be a culprit- I had some blackmagic software on my machine. I downloaded their utility from the Blackmagic website (under support) in order to properly uninstall all of their drivers from my mac, and now AE renders beautifully again!
Long story short- there is more than likely something on your machine causing this type of crash- if you go into your activity monitor (applications-utilities-activity monitor) and select “My Processes” from the drop down menu at the top of the window- look for any 3rd party programs in the list. In my case- the culprit was titled “Desktop video driver updater” or something like that. I didn’t recognize it at first- but Desktop Video was the name of the Blackmagic software that was on my machine.
Note- I had been running Aftereffects cs5.5 with the blackmagic software on my computer with no issues- it wasn’t until I upgraded to AfterEffects CC that I started having issues at render time.
Good luck!
Will
-
Abdelouahed Jabbar
February 25, 2014 at 3:21 pmI think it has something to do with missing or duplicated text fonts in the machine…
everything was back to normal when i deleted and reinstalled a some fonts.
Hope that helps 🙂
Reply to this Discussion! Login or Sign Up