Multiple output modules cause render to fail?

Is anybody else having trouble with using multiple output modules in after effects? Let me elaborate: so I'm working on a 3d film, and my worflow is to simply work with the footage side by side in a single comp (we're at HD, so the comp size is 3840x1080). Very often, I need to fire off a quick render to show to the director. Most of the time, I just do the left eye by cropping to that 1920x1080 area in the output module. Other times I need to deliver both eyes, so instead of cropping to 1920x1080, I resize the frame in the output module to 1920x1080. Yea, we lose half of our horizontal resolution, but that's not such a big deal for us when just working on approvals.
Here's the thing: sometimes I like to export multiple variations of this at once (ie one output module for the left eye, one for the right eye, and another for the squished side-by-side left-right video). Whenever I try to output multiple modules with quicktime, it fails. Every time.
When it fails, I get two messages: the first (a warning) says "After Effects warning: last frame was written to one or more output modules, but not all! ( 26 :: 153 )"
The second message (an error) shows up once for each output module: "After Effects error: Rendering error while writing to file "C:\blahh blah blah\whereIputmyfiles\the_render.mov". An output module failed. The file may be damaged or corrupted. (-1610153464)." Once it fails, I cannot output to quicktime AT ALL (multiple output modules, or not) without restarting After Effects.
I tried outputting multiple modules as a PNG sequence... and that worked just fine (if "slow as hell" can ever be called "fine" .... but it worked! )
I tried outputting to the multiple formats I wanted with one output module per render item (rather than having one render item with multiple modules) as quicktime, and that worked just fine (of course... it takes N times as long though... for N number of outputs).
I am on Windows 7 64-bit... running After Effects CC 2014... I never had this trouble back when I was working on the CC version (the not 2014 cc version... that is too confusing...). However, I just went back and tried it with the older version, and it no longer works there either! What gives?
When outputting quicktime, I'm using the h.264 codec.
And before anybody suggests it, no I can't just use AME because that can't resize video (it forces you to keep the aspect ratio through letterboxing) or crop video.

>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.

Similar Messages

After Effects CC Output Modules on Render Only Machines

Hi there, I'm having an issue with custom Output Module Templates and my renderfarm:
After Effects CC 12.0.0.404 (showing as up to date in Creative Cloud)
Mac OS X 10.8.4 (Latest Mountain Lion version)
Mac Pro 2.93 GHz 8-Core, Radeon 5870, 32GB RAM and with Blackmagic Decklink Extreme 3D+
Remote Machines (there are four) are Mac Pros as well (Quad-core, running 10.7.2 with 16GB RAM), using the ae_render_only_node.txt file in their user Documents folder.
The exact error:
aerender ERROR: No output module template was found with the given name.
I am trying to get a renderfarm working with After Effects CC (see exact version above). Unfortunately, I need custom output modules and I can't seem to get the render slaves to recognize them. I found older threads on this exact issue, but no solution was found.
I am using commandline aerender in OS X terminal to start a render with a basic test scene.
To simplify things, I have tried testing this on one render slave machine at a time... Same result everywhere.
Here's what I've tried:
I exported a .aom file from my main machine (where I have my desired custom Output Modules) and attempted to bring it in on the render slaves. However, because the render slaves are render only, (they have ae_render_only_node.txt in their Documents folder), the ability to import Output Modules is disabled in After Effects (it opens as the After Effects Render Engine, and the Edit>Templates menu is greyed out).
Next, I thought I'd try copying the main machine's /Users/(user)/Library/Preferences/Adobe/After Effects/12.0 folder over to the render slaves, thinking that would get whatever preference file to them that's needed to define the output modules. No luck. Launched After Effects (which loads as After Effects Render Engine) and reset my disk cache preferences (so they weren't still the main machine's). Tried aerender again... no luck. Same error:
aerender ERROR: No output module template was found with the given name.
After that, I thought it would be a good idea to sign out of Adobe Creative Cloud on the main machine, and try logging into the render slave machine with my full UserID and Password and temporarily remove the ae_render_only_node.txt file. Then, I'd import the .aom file in the full version of AE... I tried this and success! The renders work... they find the Output Modules no problem. Only issue is, as soon as I sign out, and switch to using the ae_render_only_node.txt file, the Output Modules are not found. Not sure what's going on-- if the Output Modules are being disabled by the ae_render_only_node.txt file? Or maybe signing out of my Adobe ID is removing the preferences that determine Output Modules? Don't know where the Output Module preferences are stored to be able to tell.
Next attempt: I thought I'd try syncing my preferences with Creative Cloud. I made sure to check After Effects Sync Preferences to ensure that Output Modules are set to sync. I did a sync where I uploaded my preferences from the main machine. Then, on the render slaves, I ran Sync Preferences, and chose to download preferences. Works when signed in, but not when used as a render only node. When it's a render only node, it still prompts me to Download the Sync Preferences and Quit the Application, which I do, but nothing seems to happen. I try aerender again, and still the same error:
aerender ERROR: No output module template was found with the given name.
I can't seem to find any info on where Output Modules are actually stored (apparently they're not anywhere in the User/Library/Preferences/Adobe/After Effects/ folder?). Are render only nodes not allowed to have custom Output Modules? Not even for something as simple as the Multi-Machine Sequence with a post-render action of Set Proxy enabled?
Any help is greatly appreciated!
Thank You.

I've verified this problem and filed a bug. Sorry about the hiccup.
I've trying to pin down why this happens, and while I don't have a full explanation yet I think I've stumbled onto a workaround:
Trash the prefs on the render machine.
Enable the ae_render_only_node.txt file.
Launch AE and then quit. <- This is a critical step. More on this later.
Disable ae_render_only_node.txt file.
Launch AE.
Add your Output Module template.
Quit AE.
Enable the ae_render_only_node.txt file.
After you do this, I highly recommend making a backup copy of the Adobe After Effects 12.0 Prefs-indep-output.txt file. Just in case. I've had the failure reappear.
Now test with aerender and let me know if that works. It has on my machine.
Why does this matter? When you run AE with the ae_render_only_node.txt file enabled, it appears to add a new section to the preferences: "Output Module Preference Section v28-TRIAL". It's the TRIAL part that is important. Without it, AE doesn't seem to be able to keep track of the OM's when in render_only_node mode. And if you disable the ae_render_only_node.txt file, AE has a tendency to destroy the TRIAL section (I'm still tracing why that happens).
Now, should this not work for you, I recommend you work around the problem by adding your comps to the render queue in each project. When you do that, and change your aerender flags appropriately, you can render to your desired settings without specifying OMtemplate parameter.
> I can't seem to find any info on where Output Modules are actually stored (apparently they're not anywhere in the User/Library/Preferences/Adobe/After Effects/ folder?).
You probably already discovered this. In After Effects CC the OM data is stored in the Adobe After Effects 12.0 Prefs-indep-output.txt file. In older versions of AE, a single pref file such as Adobe After Effects 11.0-x64 Prefs.txt holds all of this data.
Let me know if that workaround does the trick for you. If I get more information on the cause of the problem I'll update you.

Import Output Modules to render slaves with expired trial

Hello, I intend to launch network render jobs through the command line in Windows 7, ie., not with Watch Folder feature but by passing command lines directly to aerender.exe.
The problem is that I need to create new Output Module settings for the render job and pass it on to my render slaves. The slaves are installed in trial mode which now have expired, so I am not able to open up full After Effects and import an .aom file. And I have not figured out a way to do the same thing with just the Render Engine as the menu option is disabled no matter what I do.
I thought that copying the preference files from my workstation to the render slaves would give them the new Output Modules as I read that these settings are stored in the preference files somehow, but the render still complains about missing modules if I try.
I have 'almost' solved the whole thing by temporarily register the expired versions with my serial, import the .aom (or recreate the template from scratch), and then deactivate AE into trial mode again.
However I noticed a strange behaviour when doing this which I cannot figure out. I had previously put a ae_render_only_node.txt into \Users\Public\Documents\Adobe to force it into Render Engine mode, but it seems like the aerender.exe can no longer find the new Output Module I just created when ae_render_only_node.txt is present in that folder.
As soon as i remove ae_render_only_node.txt the aerender.exe renders fine, but with the file present it just won't find the new module on any of the slaves. I guess it works for as long as the "new" trial period is active (by registering and deactivating I got 30 days trial mode again.) But once this trial is over I am forced to use ae_render_only_node.txt to make the slaves render, no?
It is perhaps so that using the standard way of network rendering through Watch Folder will avoid this issue, but the reason is that we are designing custom network render tools that use aerender.exe because of simplicity, speed and reliability compare to Watch Folder.
In this case it would have been so much easier if Render Settings and Output Modules would have been stored as an ordinary XML or INI file which could be transfered between systems and edited with simple external text editing tools.
Right now it seems like this won't be a problem for me during these next 30 days, but after that I fear that my custom Output Module settings will no longer be recognized.
Is there any solution to this?

>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.

Missing H.264 Output Module in Render Queue

I've reinstalled AECS4 and still have no H.264 in the output format dropbox. I am missing quite a few compared to CS3. Any ideas why?

What operating system? What other Adobe CS4 applications are on your system? The modules not showing up may also be caused by the licensing system thinking that some pieces are trial versions. In such cases, removing and re-installing the other apps may also be required, especially Encore and Premiere who share these components.
Mylenium

After Effects Audio Output Causes Render To Hang Then "Output Module Failed"

So I have been working on this video for a few weeks now, no special effects just 3D layers and text.
I had set it to render Thursday afternoon and it finished Friday night after I left work.
So today I came into work played the video and I realized I didn't render the audio. (NICE!)
So I reset the render que (didnt change anything but render audio settings) and the render
doesn't even start, it just stays at "Stage: Compressing and Writing" for a few minutes then gives me
the good ole' output module has failed.
Ive already restarted AE, and my comp, I also purged the memory.
Im running windows 7 (64 bit) with 8gb RAM and Intel Core i7-3770S CPU @ 3.10ghz
It is definitely the audio output, I tried rendering without it and it started up just fine.
Any help is greatly appreciated.

just updated to 11.0.2 and still nothing
I click Render and it just says rendering but nothing changes
not even time elapsed or est. remaining
just stays on compressing and writing and my ram used doesnt even start going up

AE CC Render error output module failed

Hi, I tried my best to find this answer on the forums but couldn't find anything current.
I have isolated two issues in AE CC where I can duplicate a failed render with this message:
After Effects error: Rendering error while writing file "xxx". An output module failed. The file may be damaged or corrupted. (-1610153464)
This happens when opening an AE CS6 project and trying to render a simple comp with only one text layer and a moving mask. It also just happened after my first round trip test with Cinema 4D. I could RAM preview the c4d layer but the output to Quicktime h.264 failed.
I have even tried a full reinstall of AE CC. I have the basic FxFactory Pro plugins and MagicBullet Looks installed, but neither are being used since this is a single 1280x720 comp with a single C4D layer. Plus like I said it failed with the same error in past CS6 files.
I don't know how to force disable a plugin to test that, but I can't see how an unused plugin could cause a render to fail like this.
I'm on a new (late 2012) 27" iMac
3.4 GHz Intel Core i7
8GB RAM
NVIDIA GeForce GTX 680MX with 2GB VRAM
OS X 10.8.4
AE CC 12.0.0.404
CUDA driver 5.0.59
Thanks for any suggestions!
Matt

Olaf, did you read my reply where I explained my solution? First you should try the steps outlined in the article Todd references:
http://blogs.adobe.com/aftereffects/2011/02/troubleshooting-quicktime- errors-with-after-effects.html
There seems to be a good way to isolate if it's the same issue I had, though. Let me go into a bit of depth for you.
The trick was to launch the OS X app called Console, located in Applications > Utilities. It is a program that compiles and displays the system logs in real time. It's great to see the little things happening in the system that don't make it into the user interface. When I had my Console up and generated that same error you're having, I noticed this error in the log:
The key here is the Adobe QT32 Server, which is mentioned in the TCP part of the article I linked to above from Todd. In my case at least, what was happening was that a third party app called AirServer was talking to the system's QuickTime over the same TCP ports the QT32 Server engine was trying, and it resulted in Adobe QT32 Server crashing, and that alert being thrown up in AfterEffects.
If you're in the same boat, it means you have some sort of app or system extension that is also talking to QuickTime over TCP. That may not make any sense, but the easy thing to do is quit ALL third party apps, then quit AE, then restart AE.
In my situation if AE gave me the error and then I quit AirServer, the error still happened because Adobe QT32 had already crashed. You have to relaunch AE after closing the offending third party app.
To be sure you've quit all third party apps, open Activity Monitor (Applications > Utilities), chose "My Processes" from the dropdown menu, and scan through the list to make sure. You don't have to recognize all the processes there, but you should be able to recognize any third party ones you put there.
Hope that helps!
Matt

An output module failed. The file may be damaged or corrupted.

Whenever I try to render something in After Effects CC 13.1.1, an error message pops up, saying "After Effects error: Rendering error while writing to file '[not going to disclose]' An output module failed. The file may be damaged or corrupted (-1610153464)."
Screenshot of the error message:
I tried reinstalling QuickTime (7), repaired it, updated After Effects to the latest version(as I am writing this), checked firewall software, and used other formats such as AVI.
Adobe Media Encoder (CC 2014-latest version) won't work with me, either.
I sent the composition to Adobe Media Encoder, and this is what I got, no progress here.
Screenshot:
It took a while to connect to the dynamic link server, and failed.
This is a log of what has happened in Adobe Media Encoder.
- Source File: C:\Users\Default.BronyGue\Documents\not done\pinkcoverart_AME\tmpAEtoAMEProject-Pink Intro1.aep
- Output File: C:\Users\Default.BronyGue\Documents\not done\pinkcoverart_AME\Pink Intro.mp4
- Preset Used: YouTube HD 720p 29.97
- Video: 1280x720 (1.0), 29.97 fps, Progressive
- Audio: AAC, 320 kbps, 48 kHz, Stereo
- Bitrate: VBR, 2 pass, Target 5.00 Mbps, Max 5.00 Mbps
- Encoding Time: 00:00:12
06/29/2014 02:29:14 PM : Encoding Failed
The Operation was interrupted by user
(no need to worry about the above part)
- Source File: C:\Users\Default.BronyGue\Documents\not done\moddedchill_AME\tmpAEtoAMEProject-montage1.aep
- Output File: C:\Users\Default.BronyGue\Videos\chilledup.wmv
- Preset Used: Custom
- Video: 1280x720 (1.0), 29.97 fps, Progressive
- Audio: Windows Media Audio 10 Professional, 96000 Hz, Stereo, 24 bit
- Bitrate: CBR, 2 pass, Max 10000.00 kbps
- Encoding Time: 00:01:42
11/22/2014 12:24:39 AM : Encoding Failed
The Operation was interrupted by user
- Source File: C:\Users\Default.BronyGue\Documents\not done\moddedchill_AME\tmpAEtoAMEProject-montage1.aep
- Output File: C:\Users\Default.BronyGue\Videos\chilledup.mpg
- Preset Used: Custom
- Video: 1280x720, 29.97 fps, Progressive, Quality 75
- Audio: MPEG Audio, 384 kbps, 48 kHz, Stereo, 16 bit
- Bitrate: VBR, 1 Pass, Min 4.00, Target 15.00, Max 18.50 Mbps
- Encoding Time: 00:00:11
11/22/2014 12:52:11 AM : Encoding Failed
The Operation was interrupted by user
- Encoding Time: 00:00:51
11/22/2014 12:53:51 AM : Encoding Failed
Export Error
Error compiling movie.
Unknown error.
- Encoding Time: 00:00:46
11/22/2014 08:39:46 AM : Encoding Failed
Export Error
Error compiling movie.
Unknown error.
- Source File: C:\Users\Default.BronyGue\Documents\not done\moddedchill_AME\tmpAEtoAMEProject-montage4.aep
- Output File: C:\Users\Default.BronyGue\Documents\not done\moddedchill_AME\montage.mpg
- Preset Used: Match Source - High bitrate
- Video:
- Audio:
- Bitrate:
- Encoding Time: 00:00:00
11/22/2014 10:06:45 AM : Encoding Failed
Could not read from the source. Please check if it has moved or been deleted.
I need some help! Any solutions?.
Computer Specs:
AMD FX-6300
8GB 1600MHz DDR3 RAM
NVIDIA GeForce GTX 650 Ti BOOST
1TB 7200RPM Hard Drive
Windows 8.1 Update 1(with latest updates)
EDIT(11/23/2014 8:31PM PST): For some reason, other projects work for me just fine. I am not sure why it is not working on one project.
Screenshot of a new project other than this I am rendering at the time of writing this edit:

Can other projects can output to the same output location? Yes
Can other projects render with the same render settings (codec, format, etc.)? Yes.
If you create a new composition and just add a solid layer to it with no effects in the same project does it render? No. I still get the error.
Can you render that brand new comp with the same render settings, output settings, output location etc.? Yes.
If so, what effects are present in the offending comp? Twixtor Pro in all the cinematics/clips, Motion Tile and Transform for pan/crop & wiggle, Magic Bullet Looks and Bad TV Warping preset with just Wave Warp & Venetian Blinds for color correction, Gradient Ramp for text, Bad TV Warping preset with everything for effect, Transform for fade in/out, and ReelSmart Motion Blur v4.1.2 for motion blur.
Also, what scripts are you using? Just the Move Anchor Point script I found from one of Mt. Mograph's videos, Summit 16 - 2.5D Minecraft Steve - After Effects - YouTube.
Have you ever installed any third-party codec packs? (I've heard of some codec packs causing weird issues like this.) Yes, (not everything I have, just everything I can think of and find) I have K-Lite codec pack, Fraps, x264vfw, and Xvid MPEG-4 codec.

Output module failed

I know there are more posted about this problem bust still havent found a solution.
I can only render out one movie from AE (CC 12.2.1.5). If I want to render a second movie I get ""[file path and name].mov”. An output module failed. The file may be damaged or corrupted. (-1610153464)"
I've deleted DVCPROHDVideoOutput.component as read on a help file (http://blogs.adobe.com/aftereffects/2013/08/solutions-for-problems-with-quicktime-files-in -after-effects-cc-12-0-because-of-conflict-with-dvcprohdvideoout-quicktime-component.html) but dit didn't fix it.
A restart of OSX (10.9.2) fix it for one render and then I got the same problem again. I render to DXV codec (rgb+alpha) (http://resolume.com/software/codec)
What do I do to fix this? Because rebooting is taking to much time
thx Joost

Have you installed any third-party codec packs (such as K-lite)? I've seen them cause this sort of issue in the past.
Have you tried it in AE 13.1 or 13.0?

Output module failed 1610153464

I am running CS5 on a Mac 10.6.6. I have both QTX and QT 7.6.6 installed
Every time I render, it gives the following error message:
An output module failed. The file may be damaged or corrupted. (-1610153464)
I've tested the files on a different machine and they open and render out fine.
I'm having these issues and I don't have any plugins installed.
Re-Installed everything multiple times, trashed preferences, removed plugins from the Application support and still no luck.
The only thing that works for me is outputting to a PNG or JPEG sequence.
If I try to render using the Animation preset, It gives the error message.
I also have been getting a weird "MooV" error message when I try to import certain types of quicktime files. Not all just a few random ones.
All of this leads me to believe it is a Quicktime issue.
Please can you help. Other than doing a complete clean operating install, which i am doubting will work.
Robin Souter

hey todd,
good thinking, I was just trying the very same thing. alas when I try to open my AE project in Media Encoder I get the message
"Could not connect to Adobe After Effects. Please verify that Adobe After Effects and Adobe Dynamic Link components are installed."
I'm scratching my head, this also worked yesterday.
Could it be anything to do with de-activation? I have cs5 installed on my workstation in my studio.
I also have it installed on my laptop at home. do I need to contact Adobe each time I want to use 1 machine or the other?
Also ever since installing cs5 on my laptop I get the following message each time I launch After Effects (dont know if its connected as I normally just click ok and use AE as normal)
"Runtime Error! This application has requested the runtime to terminate it in an unusual way.
Please contact the application's support team for more information"
or maybe I didn't run the adobe uninstaller cleaner utility to get rid of traces of old versions, before installing cs5 to my laptop
thanks
ste

After Effects "Output Module" render error & rendering advice

Hi all,
I've been working on an AfterEffects project for a few weeks and never had a problem with rendering it before, but in the past few days it has started giving me error messages every time I start a render.
After rendering about 48 - 60 frames of a 2 minute long composition (it doesn't seem to hang in the same place every time), the render freezes and I get this error message:
After Effects error: An output module stopped responding. The file may be damaged or corrupted. You may need to restart After Effects.
The project is really huge -- about 1022 3D layers, mostly all created in Photoshop, as well as some Quicktime movies. Motion blur is turned on for everything. Although the project is big, I have a 3D camera that animates through the scene, so not all the layers are onscreen at all times.
I haven't added anything significant to the composition lately, I've just been adjusting keyframes, so that would lead me to believe the render isn't failing because of a corrupted element.
I'm using Adobe After Effects CS5, Version 10.0.2.4. I have some 3rd party plug-ins installed (Trapcode, Magic Bullet Looks, Optical Flares), but I'm not using any 3rd party effects on this project, though I plan to in the future.
I'm running the project on a 2 x 2.66 Ghz 6-Core Intel Xeon Mac Pro with 14 GB 1333 MHz DDR3 RAM, using OS X version 10.6.8.
Here is some information about my project:
1280 X 720, Square Pixels, 23.976 Frame Rate, Rendering Plug-in: Advanced 3D. For my preferences, I don't have "render multiple frames simultaneously" checked, and I keep 4 GBs of RAM reserved for other applications. I also have OpenGL disabled.
And finally, here are some screenshots of my Render Settings and Output Module for this project:
I'd really appreciate any feedback or advice on how to troubleshoot this error. And I'd also love to hear if the experts on this board have render settings tips or advice on how to set up my render preferences for my particular machine.
Thanks and hope all is well,
Dan

Hey Dan,
Really nice post in regards to info provided initially. It's rare to see that these days.
The weird thing in your screen shots that I see, is that in your Output Module Settings, the audio bit-depth settings seem to be grayed out for some reason. Are you using some sort of audio hardware that is customized, or perhaps some compressed audio in your project? Here's what I mean:
Thoughts? Aside from that, your project does sound as if it is pretty intensive, so I'm sure the problem could be occuring elsewhere...

"...an Output Module failed" error screen...

Greetings AE Peeps!!
Long time - no see - been stupid busy. My Studio has just ponied up and upgraded our 5 Edit Stations to AE CS5. I personally am a huge advocate of not upgrading software while in the middle of a project, but this was out of my control. I am having a lot of crashing (app just quits for no reason while scrubbing) and other weirdness...like today. I am rendering a 3 minute piece in ProRes 4:2:2 (1280x720p) to my RAID (no special plug-ins or anything) and I get the following error at the very end of every render:
After Effects Error: Rendering error while writing to file (insert my RAID path here). An output module failed. The file may be damaged or corrupted (-1610153464)
I have never in 11 years got a "failed Output Module error". Can anyone speak to this and tell me how to get rid of it short of reinstalling AE?
Grazie! Ciao!
Joey

First, make sure that you've installed the After Effects CS5 (10.0.1) update.
Regarding the output module failure: It may be that this is because you have an output module created in a previous version of After Effects that refers to a codec or set of settings that isn't working in After Effects CS5. The best thing to do is to remove the output modules from the render items and then rebuild them in After Effects CS5. That may sound tedious, but you only need to do it once, and then you can save output module templates that you know work with After Effects CS5.
As Mylenium suggested, there are some challenges associated with the fact that there is no 64-bit QuickTime, so we had to create our own 32-bit-to-64-bit QuickTime conversion layer (QT32 Server). QuickTime does work with After Effects CS5, but there are some hiccups in some cases on first use.
If this doesn't help, answer back and we'll help you through.
Oh, this might be useful, too:
http://blogs.adobe.com/toddkopriva/2011/02/troubleshooting-quicktime-errors-with-after-eff ects.html

Rendering error whilst writing to file /filename etc./ An output module failed

I'm trying to render my composition in the latest AE CC 2014. I get the following error with all composition sizes and with different codecs: Rendering error whilst writing to file /filename etc./ An output module failed. The file may be damaged or corrupted (-1610153464). Can anyone help me sort this problem?

AE build number? Codec used? System OS?

2 error messages - failed to install extention 2.1 and output module 2.1

I just tried to update my Encore CS4 from the Master Suite. I have two error messages " failed to install extention Mgr. CS4 2.1 and failed to install output module update 2.1
Encore will load a new project and save but I can't do anything else like add files before it crashes. Any help please. - Art

This might not apply with En CS4, but there were some issues on install, and on updates in Photoshop. It seems that MS had a bum MSI (Installer) version, and it caused a lot of PS installs and updates to fail. Do not recall any specific error messages. The cure there was to download and install the revised MSI module from the MS site. I would imagine that any MSI module would be heavily Windows version-specific. Take that as a warning to check any very carefully, before downloading and installing. MS is pretty good at having a ReadMe with installation instructions for each such download. It almost always contains the exact versions of Windows, that the file is for. Please read any installation instructions carefully.
This might be worth a look. I do not have a link to the exact page, but a search of the MS site should yield something. I'd search for "MSI," to start.
I just do not recall any issues with En and either installation (on proper systems with updated OS's) or with any updates.
Good luck, and please report your success.
Hunt

After Effects Error: rendering error while writing to file...Output Module failed - 1610153646

Hi – I’m currently working with someone who is running After Effects 5.5v10.5.0.253 on a PC which is running Windows 7 Ultimate. The computer has just recently been built and the software is newly installed. (ie. a couple of weeks old, max). Up until now, we have been using After Effects with no real issues. But tonight, we started to see the following error message, when trying to render something out:
“After Effects Error: rendering error while writing to file xxxxx. Output Module failed, the file may be damaged or corrupted -1610153646” – displayed during render, which meant the render failed.”
We started to review forums to see if we could come up with a fix and tried a few of the more common suggested solutions, including:
Make sure there are no third-party plug-ins or Windows incompatible elements installed - as it’s a pretty new install, we haven’t added anything except out-of-the box elements.
Clear the render queue – did this, no change.
Reinstall Quicktime – did this, no change.
Reinstall Creative Suite – also no change.
Check the default program to open .mov files is Quicktime – Quicktime was already the default.
A bit more detail about the machine...
Ram is 32gb
GPU is GeForce GTX 660ti
250gb soild states
2tb raid drive
Any help would be much appreciated. This is now happening on all AE files, even files that worked fine earlier in the week. Other than the AE and QT reinstalls mentioned above, nothing new has been added to the machine this week. On a deadline – so a quick response would be amazing, right about now. Thanks.

Hi Mylenium- thx for the quick response. We have have tried a bunch of different settings. AVIs work and we can do image sequences too. The only major problem seems to be with Quicktime files. While I appreciate your suggetion to convert with AME - this is only a workaround. Was really hoping for a solution that will fix the problem in After Effects? Heard rumor from a few friends in the biz, that this is a major bug... if possible, some feedback from Adobe product devs or someone with a technical background would be great! Thx.

After Effects CS6 render-only: Custom output modules?

With After Effects CS5.5, we've been able to include custom output module templates (so, aside from the default Lossless, TIFF Sequence with Alpha, etc.). We're having trouble doing the same with CS6. Is there any way to make this work?

this explains what we are trying to use, non-royalty-bearing mode.
http://blogs.adobe.com/aftereffects/2012/06/codecs-and-the-render-engine-in-after-effects- cs6.html
please understand we are using a render queue to remotely execute aerender from the commandline.
http://help.adobe.com/en_US/aftereffects/cs/using/WS3878526689cb91655866c1103a4f2dff7-79a3 a.html
this is the command that is entered:
"C:\Program Files\Adobe\Adobe After Effects CS6\Support Files\aerender.exe" -project "\\nas3\graphics\jobs\13912_SHIELD\cmp\BB\BB_CS6_Test2\BB_CS6_Test2.aep" -comp "HeroComp" -output "\\nas3\graphics\jobs\13912_SHIELD\images\BB\BB_CS6_Test2\BB_CS6_Test2.[####].sgi" -v "ERRORS_AND_PROGRESS" -RStemplate "Full" -OMtemplate "SGI_Premultiplied" -s 11 -e 20
if we place ae_render_only_node.txt into the appropriate folder this is the error that is generated:
has video RAM(MB): 0
aerender version 11.0x378
PROGRESS: Adding specified comp to Render Queue
aerender ERROR: No output module template was found with the given name.
LoadLibrary "n" failed!
LoadLibrary "n" failed!
if we register the software aerender correctly renders the frames.
note: the sgi file format does not have codec licensing restrictions such as mpeg2.

Multiple output modules cause render to fail?

Similar Messages

Maybe you are looking for