Copy link to clipboard
Copied
I'm getting these "after effects warning: Error reading past end of file" while rotoscoping. There doesnt seem to be any rhyme or reason to it. As a result this part of my file wont render/export in premiere. I check the file in After effect and I dont see any reason to be getting the error. I even went as far as replacing the clip footage with the same footage and I still get that error.
Hey, i had the same problem and all i had to do was unfreezed a rotoscopy and make the program freeze it again
Copy link to clipboard
Copied
Hi @JohnnyRocket ,
This type of behavior usually occurs if there was some sort of crash.
Attempt a render from After Effects.
If that is successful, replace the footage on the Pr timeline.
Let us know how you go
mj
Copy link to clipboard
Copied
Whey I attempt a render that message pops up over and over again, then a message does show saying something crashed and send s one of those 'send to adobe' things.
It eventually 'renders', but when I go to premiere and try to export that clip I get a 'cannot render' message and Premiere crashes.
Copy link to clipboard
Copied
To be clear, does the render work without that footage in Premiere?
I found this resource for you for Premiere render errors. https://helpx.adobe.com/ie/premiere-pro/kb/error-compiling-movie-rendering-or.html
Can you try placing the Ae comp into the Pr timeline without rendering?
Keep us posted
mj
Copy link to clipboard
Copied
Not sure I get your exact question.
First, in premiere pro, when I would try to render or export media, I would get an error saying it couldnt render around time XX:XX:XX. I eventually figured out its the after effects linked comp. When I opened that linked comp, I would get that " "after effects warning: Error reading past end of file"" message. Nothing I did seemed to fix that error. Even replacing the footage of that comp. I ended up just removed/deleting that comp and redid it.
Copy link to clipboard
Copied
Hey, i had the same problem and all i had to do was unfreezed a rotoscopy and make the program freeze it again
Copy link to clipboard
Copied
This works! Seems like an issue with freezing the rotobrush files in linked comps
Copy link to clipboard
Copied
Thank you!! Absolute legend. Had this same issue and was driving me nuts.
Copy link to clipboard
Copied
3 years later and this is still an annoying, unexplainable issue. Using 2024 with Roto Brush 3.0 and this error has constantly killed my workflow on many projects.
Copy link to clipboard
Copied
When I use Rotobrush, I always pre-compose the trimmed footage layer, moving all attributes to the new comp and trimming the comp to the layer length. Then, the pre-comp, the now nested comp, is opened in the Layer Panel, and Rotobrush is applied. This keeps the extra frames at the head and tail of the shot from showing up in the Layer panel. If Rotobrush takes more than a couple of minutes to complete, I always pre-compose the Rotobrtushed comp again, open the comp, and then choose Composition/Pre-render to replace the Rotobrushed comp with rendered footage in the Project. When the file has been rendered, I delete the Rotobrushed comp to reduce the AEP file size and improve AE's stability. Pre-rendering also reduces the final render time of the comp. In some cases, the final render time is reduced by more time than it took to render the Rotoed footage.
Copy link to clipboard
Copied
I have the exact same problem in pr and ae for my roto video as described by @JohnnyRocket, and here is how i solved it.
step 1: remove empty frames at start and at end of your roto composition (as subtly mentioned by @Rick Gerard)
step 2: unfreeze then freeze the video (as mentioned by @laucov)
simply doing step 2 does not work for me, both doing both 1 and 2 solves both "Error reading past end of file" in ae and "accelerated renderer error" in pr.
hope it helps!
Copy link to clipboard
Copied
This bug has been reported for close to 5 years and is still present. There shouldn't be a need to still be providing possible workarounds. The whole point of subscription based software is so it can be constantly improved and bugs liked this fixed. Yet, 5 year old bugs like this aren't squashed while monthly rates increase exponentially. This is why the hate for Adobe is getting louder by the day.
Copy link to clipboard
Copied
Hi John,
Sorry for the frustration. Could you let us know more details? Is it happening on a specific project? What version of After Effects are you using? What are your system specifications (CPU, GPU, RAM, OS version)?
Let us know.
Thanks,
Nishu
Find more inspiration, events, and resources on the new Adobe Community
Explore Now