Activity › Forums › Adobe After Effects › Export Module failure
-
Jeremy Mayhew
January 5, 2011 at 3:49 pmHello Kai,
I’ve just returned from holiday travels and will be testing again soon. I never did find a solution to this problem. Have you? Has anyone else?
-
Ran Ben avraham
January 11, 2011 at 11:02 amI have head the same problem.
In my compositions i used Video copilot’s “VC-Reflect”. once i disabled the effect everything worked like a charm.
Disabling the effect is a work-around and not a solution, so if someone will find a real solution i would love to hear about it.
Best regards,
Ran Ben Avraham. -
Eric Litwin
January 30, 2011 at 3:33 amDownloading Quicktime 7.6 from Apples site and reinstalling it seemed to clear up the issue for me.
-
Patrick Manning
January 30, 2011 at 3:58 pmHaving this same issue. It also cropped up out of nowhere. Rendered fine. Went to re-render and got the error. I installed Quicktime 7.6.6 for snow leopard and now instead of getting the error on the first frame, I get it on the last. Running Mac Pro Quad Core (Q6600) with 8 GB ram AE CS5. I am using the render que to create Tiff sequences as a work around, but would like a solution if anyone finds one.
-
Joel Dubin
February 10, 2011 at 1:56 amHaving the same exact problem.
Been working on the same file (AE CS5 on an 8 core mac, OSX 10.6.6, 10gb ram) for several months without a problem. Now at the crucial end of project stage, getting a render failure from the render queue about halfway through. Same error message as posted above. Havent changed anything on my rig since the last time it rendered successfully.
VC optical flares, RSMB, Frischluft Lenscare are the only 3rd party plugs Im using.
Tried saving alrternate copies of the ae file to, and render to alternate drives, same result.
Anyone have any new info?
thx -
Joel Dubin
February 14, 2011 at 3:08 amFigured it out. In my case, it turned out to be reelsmart motion blur applied to a scaled layer–which is always a no-no. It was on a layer that was not immediately obvious to me–not on a layer that was actually visible onscreen or would have caught it sooner.
I’ve had this issue in the past so should have known better.
-
Ayako Minatodani
February 20, 2011 at 8:04 pmHi! I’ve been having a same problem. Did you ever get to figure it out? If so, please let me know how to solve this issue.
Thanks,
Aya -
Ayako Minatodani
February 21, 2011 at 1:05 amI’ve been having a problem trying to render a file on CS5 AE. I just installed
CS5… I could render it as TIFF sequence but not in other format. I could render
the same file in my CS 3 AE, though. I made a new comp with one solid layer and
it still gives me a same error. Please let me know if you know any solution.
Thanks!
aya -
Eric Litwin
February 22, 2011 at 2:59 pmI’m on a Mac. After the problem returned for me I launched Activity Monitor and Console which revealed one of the multiprocessing threads was bloating up and hogging RAM. With the system starved of memory I was having aeselflnk crashes, BG renderer connection problems, and the 1610153464 error. Eventually the problem was traced back to an odd bug that a script (Load Project or Template from AEScripts) was causing on my machine if it was setup in a particular way.
Removal of the script fixed the situation.
Perhaps try launching the Activity Monitor, or the Windows equivalent if you are on that platform, to see if one of your multiprocessing threads is going out of control. Maybe it’s a similar issue.
-
Robin Souter
February 25, 2011 at 12:49 pmI am having the same problems trying to render from AE CS5 on a iMac (OSX 10.6.6). It seems to be user specific. I another user on the same machine I can render fine??? Weird. Does anyone have any advice on what to do?
Reply to this Discussion! Login or Sign Up