Activity › Forums › Adobe After Effects › Export Module failure
-
Henry Garrou
May 3, 2011 at 11:12 amSUCCESS!
I have had the same error this morning and my only resource for fixing it was this thread. I was only recompressing an image sequence of tiffs with one wave under, and go the same error as everyone else.
I prepared my render queue. Shut down AE and then restarted AE. Problem solved.
Hope this helps shed some light on this for everyone else.
On a Dell StudioXPS
ATI FireGL 8750
8GB RAM
1.0 TB HD space avail. -
Ethan Benninger
May 5, 2011 at 5:07 pmSuccess! I was finally able to export ProRes 4444 by setting up the render queue, saving, quitting, restarting AE CS5 and then rendering. Working like a champ!
Ethan Benninger
Video Post-production
People Productions
Intelligently Integrated Media
::::::::::::::::::::::::::::::::::::::::::::::::::::
http://www.peopleproductions.com
1737 15th Street, Suite 200
Boulder CO 80302
(303) 449-6086 -
Michael Rocha
June 6, 2011 at 2:23 amI just had this start happening! Driving me crazy. I have using my new machine for 2 weeks now, and today the quicktime output stopped working.
I am on Windows 7 Pro with ae cs5.5.
The only change I know about between yesterday and today was flash updated, but I think it stopped working before.
-
Brian Deviteri
June 8, 2011 at 2:22 pmAdd another person to the growing list…
Mac OSX 10.6.7
2 x 2.93GHz 6-core Intel Xeon
64GB 1333 MHz DDR3
After Effects CS5.5 (10.5.0.253)As some others have similarly noted, I also have Video CoPilot Optical Flares effects installed.
I have updated to the newest version from this page:
https://www.videocopilot.net/support/updates/It is listed (text-wise) as Optical Flares Version 1.2.134 For Mac 64-bit, however the download is opticalflares_mac_x64_1.3.134.zip, so I’m not sure if this is really version 1.2.134 or version 1.3.134. Either way, it is the newest one they are offering, last updated in January 2011.
Support email to Video CoPilot has been sent – not sure if they are aware of any issues, but it can’t hurt to find out…
I am attempting to render to Apple Animation without Alpha – have done this numerous times last week using the same output modules without any issues, however those sequences probably were not using Optical Flares plugin.
I have deleted and manually rebuilt all output modules.
I have deleted the system cache and rebuilt it.
I have turned multiprocessing on and off.
I have adjusted the amount of RAM and CPUs being used.
…and the issue is still happening when attempting to go to Apple Animation.worth noting, I did observe a difference in the CS5.5 Apple Animation files in this thread: https://forums.creativecow.net/thread/2/1000716
This current sequence I am rendering is 1920×1080, 29.97 (using a standard sequence preset) and about 4 minutes long.
I can successfully restart the render several frames prior to the failure (to reassemble later) and it will render successfully beyond the failure point, but I will get another failure message later on. I can repeat this “start again” method as a work-around, but this requires babysitting the renders.
(EDIT: changed this newest render to a TIFF sequence and the render times are much closer to the Animation piecemeal render. 55 minutes left to find out if it fails…)
-
Brian Deviteri
June 8, 2011 at 2:43 pmWalter – Doubt this is related to the thread I posted awhile back about the smaller Animation files from CS5.5 vs CS4, but I am also experiencing this same issue.
Support emails have been sent to Video CoPilot and Adobe, so we’ll see what they say, if anything.
It does appear that the TIFF sequence render option is a successful workaround, so far. Unfortunate for those of us that need to deliver .MOV files (with audio) as it adds an extra step to assemble, but that’s much better than having to babysit and restart renders several times, especially for those renders that are being left overnight.
-
Brian Deviteri
June 8, 2011 at 6:51 pmThe TIFF sequence successfully rendered without an issue. So at least there’s a workaround.
Video CoPilot support suggested I disable GPU rendering, which I already had done.
They also had me download a new build of the Optical Flares plugin (build 1.3.140) that failed when “Render Multiple Frames Simultaneously” was selected, rendering to an Apple Animation.
However, when disabling “Render Multiple Frames Simultaneously” it seems to be chugging through the sequence without an issue… it’s past numerous points that it had failed at previously. Unfortunately, the render is almost twice as long with the option disabled (and live preview disabled as well).
-
Michael Rocha
June 11, 2011 at 1:28 amI got min fixed!!!!!
It turns out that After effects did not have permission to access any other part of the C drive except the user folders. I verified this by trying to save the project to C: and it was denied. I think with quicktime renders, it tries to update something in system folder and was being denied.
I turned off UAC and ran AE as an administrator and that seems to have done the trick.
(2 hours with adobe on the phone and 1 with HP and they could not figure it out!!!)
-
Simon Dayton
October 5, 2011 at 6:30 amHi guys, this is my first post as I’ve just joined.
I’ve also been having the same problem and discovered that VC Reflect from Video Copilot was the issue. An easy work around was to place the effect at the bottom of the effects control, the comp should then render out fine.
Hope this helps, cheers.
Using OS X 10.7.1 on an iMac 27″ 3.4GHz Intel Core i7 + 16Gb 1333Mhz DDR3
Reply to this Discussion! Login or Sign Up