-
Opening an Older Project Corrupts the Project
I worked in Adbobe After Effects 2020 for years and therefore have dozens upon dozens of projects from that version.
I now have upgraded to AE 2025 and I am finding very consistently that when I open a project that was created in AE 2020, when I try to render the project through Media Encoder, there is always an error (“Unable to produce frame”) at the exact same spot in the project. I can replace every audio and video file (as an experiment) and it will still fail at this same point.
This is a simple project cosisting of text, images, audio and video files. No 3D, no motion blur, no depth of field, no adjutment layers … nothing. The only effect in the project is a blur map on the text.
I have tried replacing all the media files, precomposing, refreshing, reloading, purging, and even uninstalling and re-installing. I also tried rendering to ProRes in case my chosen codec had anything to do with it and it still happened.
To recap: I am working with AEP projects created in AE 2020, opened in AE 2025 and rendering out to Media Encoder 2025. I have a modern multi-thread PC with 64GB Ram and running Windows 11 with the latest updates. I have a GeForce RTX 3060 with 12GB video memory with the latest updates.
Any ideas would be appreciated. I know I could go back and work in AE 2020 but I really like the new features in the latest version.
Here is the error from the log:
Export Error
Error compiling movie.
Accelerated Renderer Error
Unable to produce frame.
Writing with exporter: HEVC (H.265)
Writing to file: F:\VIDEO.mp4
Writing file type: HEVC
Around timecode: 00;02;00;05
Rendering at offset: 120.053 seconds
Component: HEVC (H.265) of type Exporter
Selector: 9
Error code: -1609629695
replied 9 months, 2 weeks ago 4 Members · 8 Replies
-
8 Replies
-
Change the render engine in AME and see if that works.
-
Unless I am missing something, the ability to change or choose a render engine has been removed. The renderer box is there, but it is greyed-out and clicking it produces no drop down options like it did in the past. I had looked this up and found the following:
“In recent versions of Adobe Media Encoder, the ability to directly change the render engine within the application has been removed”
-
Hey Daniel,
Having similar, if not worse problems with Premiere Pro 2025.
As I have given up on AE, I’ve not used it much.
But in PPro, which may be the same insice AE, trash all of your renders and preferences.
Roll back to AE v25.0 and see how that behaves.
If possible, avoid the Media Encoder and export straight from AE, if you can use that as an interim export format?Hope that this helps?
Atb
Mads -
Thanks for the response. I will give it a go.
-
PS:
Should add that in one of my biggest crashes it turned out that alledgedly Adobe PPro was interfering with the kernel on the Geeforce card (I had a Nvidia 4090 A.I. chip in laptop).
This was found on one of the Adobe forums…Atb
Mads -
yo Daniel! it’s time to solve this once and for all, first of all, try exporting from After Effects 2024, if that works, it means it’s an issue of our beloved 2025. Lemme know and then i tell you the next step, don’t worry, we’ll figure it out!
-
Thank you.
I did have a breakthrough yesterday as I literally scrolled frame-by-frame through the general part of the converted project identified in the error log, and found a single frame that just appeared gray. I eliminated this frame and the project rendered as it should.
The question now becomes, why does AE, upon conversion, consistently corrupt a single frame that has to be hunted down and removed?
The work continues…..
-
Hey Daniel,
Well done!
On PPro, it was Long-GOP that killed my project.
I suspect that the Adobe A.I. transcription and picture identifyng tools are tied into the timecode, and if that shifts, as it can do with Long-GOP footage then your project is toast.If long-form Long-GOP, with many edit points. Your footage on loading could at any given point be one frame short, or worse one frame long – which should not be a big issue in A.E., but in PPro, where a neat edit has everyhing, or most, in the same Video Track, it is a dissaster…
Don’t know where your frame originated from, but it could be “rogue” video file.
Thank you for sharing your findings on that frame, just shows that it is worth reading the error logs – in my case, it was often Windows Blue Screen, so no logs.
Atb
Mads
Reply to this Discussion! Login or Sign Up