Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Adobe After Effects Render fails every single time at the same frame (HD res)

  • Render fails every single time at the same frame (HD res)

    Posted by Michal Poniedzielski on October 14, 2008 at 9:26 pm

    Hi!
    I’m working on HD project (1920×1080). PC platform, AE CS3. My render fails at the end of the project (300 frames from end) on one specific frame – the one where a Videocopilot Twitch Effect (https://www.videocopilot.net/products/twitch/) becomes enabled. The weird thing is in some other places in the project Twitch effect is also used together with other memory-hungry effects and tons of layers beneth and above… and gains no trouble. Here, on the end of the project it is enabled in endtitles almost on single layer on black background! So there’s no reason for AE to fail everytime this frame is rendered…

    Help me please – I don’t know what to do… This 300 frames left on the end of the project are like in prison 🙂 And for not being guilty.

    Is there any way to avoid AE rendering and use some outside software? I have tried Nucleo but it fails to.

    Or maybe some codecs would do the trick. In Adobe Premiere I can choose which codec is used to render my stuff. Can I do that in AE?

    Thanks in advance – micz

    Intel Core 2 Duo E6600 | Asus P5B Deluxe | 4GB RAM | GeForce7200 | Windows XP Pro SP3

    Michal Poniedzielski replied 17 years, 6 months ago 24,827 Members · 3 Replies
  • 3 Replies
  • Michal Poniedzielski

    October 14, 2008 at 11:46 pm

    Here is a screenshot of this problematic composition:

    https://www.fotosik.pl/pokaz_obrazek/c316c6afeee035be.html

    The layer above is the one which I suspect is the fun-killer, but the one beneth (don’t be afraid – end stuff) is however in fact huge images sequence (4000×2500)… so maybe here we have a problem, like You said. I’ll try to reduce the size. BUT I have a question – does it mean that AE simply CAN’T render compositions with huge objects? That should be mentioned in user’s manual, shouldn’t it?

    And this is a screenshot of composition nested in the problematic one:

    https://www.fotosik.pl/pokaz_obrazek/2183ff2fc2e40fee.html

    But I have discovered that it’s not the guilty one – I have rendered it alone as a singular file PSD with alpha (there is no animation on this one) and placed it to the 03. gadzety dla tytusa composition and render fails so on. So it looks like source of the problem is “located” in 03. gadzety dla tytusa composition

    And NO it’s not happening when I’m using RAM preview

    Intel Core 2 Duo E6600 | Asus P5B Deluxe | 4GB RAM | GeForce7200 | Windows XP Pro SP3

  • Michal Poniedzielski

    October 16, 2008 at 4:28 pm

    I have tried both about OpenGL – to turn it on and off, and there was no difference in case of render. It simply fails while rendering frame #6115. Is there any other solution? Maybe someone had troubles with Twitch and can help me here?

    Intel Core 2 Duo E6600 | Asus P5B Deluxe | 4GB RAM | GeForce7200 | Windows XP Pro SP3

  • Michal Poniedzielski

    November 2, 2008 at 10:01 pm

    I did some magical stressfull calculations and tried to “decompose” this whole project. Everything in this needed timeline period I rendered separetely – every subcomposition. Every. And I hunted down a bug I think. It was – like You mentioned fiew posts earlier – a very big piece of bitmap. It was something like 4000×5000 pix psd file containing only a small layer (abot 400×400 pix) on the middle. It was made by me to avoid situation when Twitch filer applied to a AE layer with this psd, reveal edges of that psd, when this AE layer is moved. I know it sounds weird – I’m sorry but my english skills seems insufficent here.

    So – problem solved: too big file to handle by AE renderer… .. I supose… 🙂

    Thanks for suggestions

    Intel Core 2 Duo E6600 | Asus P5B Deluxe | 4GB RAM | GeForce7200 | Windows XP Pro SP3

We use anonymous cookies to give you the best experience we can.
Our Privacy policy | GDPR Policy