Welcome to our community

Be a part of something great, join today!

Log in
  • Hey all, just changed over the backend after 15 years I figured time to give it a bit of an update, its probably gonna be a bit weird for most of you and i am sure there is a few bugs to work out but it should kinda work the same as before... hopefully :)

Error reading frame from file - AE problem

K

Kenn Michael

Well-known member
Joined
Dec 28, 2006
Messages
708
Reaction score
0
Points
0
The R3D/Adobe/CS4 workflow was working beautifully for me up until yesterday.

When trying to render out of AE, it'll get through the first 6 or 7 frames, and then either start rendering black frames or pop up an error:

After Effects error: Error (4) reading frame from file........ (86 :: 2)

At which point the render will stop.

I'm on a Mac Pro 8 core with 16GB RAM. Latest version of AE CS4. Haven't changed anything in my system between it working perfectly, and now falling apart.

The other thing that sucks is that in Premiere, when playing R3Ds, ever 40 frames or so, the playback skips back a few frames then continues playing.

What's going on here???!!!! There's nothing wrong with my disks - permissions repaired, etc...

Anybody else experience this?
 
update....

deleted all adobe prefs and RED plugins, then reinstalled - seems to work fine now.
 
I'm getting the same error when trying to load any r3d files.
After Effects error: Error (4) reading frame from file........ (86 :: 2)
I've tried deleting prefs and reinstalling plugins and still get the same thing.
I've tried numerous complete re-installs still nothing.
I've also tried installing on different machines.
Anyone have any idea??

Running AE 9.01
Windows XP sp2 4gig ram
HP wx8600
 
try deleting your cache directory in AE and create a new one this will force it to re-conform your files...especially audio (it's under preferences). This fixed my issue in the past.
 
Thanks 3xm,
I tried it and got the same result.
However, I imported an older r3d file shot at 23.98 (the files i've been trying to work with are shot 29.97) and it worked fine. Hmmmm.
Are there only certain camera builds, frame rates, or aspects that you can import to AE??
THanks again for your help.
Andrew
 
I have tried 16:9, 2:1 and HD at multiple resolution (2,3and 4K) am have tried build 15,16 and 17 and they all work fine.....but...I never shot anything at 29.97 so i will try it today and see if I can import and render.
 
It's happening to me again. Seems to be pretty random. Rendered out an entire 4 minute comp with 169 shots in it with no problems. Rendered out a second time and half way thru, it stopped with the error. It's definitely not the footage, but something within AE.

Anyone from Adobe around? Who are the best people to talk to about nailing down this bug? It's completely stopping me from using this workflow at the moment .
 
Try changing my caching directory to a different drive all together ...also what are your multiprocessors/RAM settings in AE? Are they optimized for longer preview or faster rendering?...and do you have OLFP turned on or off in your RED preferences?
 
Changed the cache directory. Tried with both multiprocessing on and off. OLPF is off in the RED prefs.

16GB installed RAM
Total AE memory usage 10.00GB
RAM to leave for other applications 6GB

It's definitely some kind of memory/buffer issue. It's AE is pretty happy when it's only having to pull 1/4 resolution from 4K, but when you have to display at 2K or even 4K full res, it starts complaining and throwing up the 'error reading frame from file'.
 
IMHO, 4K from RED in AE is not yet ready for prime-time. I had similar problems when trying to denoise original footage, and they went away after I first converted them to 16 bit TIFF before going into AE.
 
one more thing....what video card do you have and how much RAM on it? Also, when you render out try actually closing your preview window (so you don't see what is being rendered)...after that I maybe out of ideas..... :-/
 
I have this same issue... works fine when rendering at half-resolution, but this intermittent issue pops up when rendering at full-resoution. OLPF is in play, rendering to TGA sequences, using multiprocessing. Noticed it during one full res ram preview attempt as well.

Error message pre-empts render failure notification email, which is less than useful.
 
this is the memory issue in AE CS5 ,because its natively 32 bit.i think this problem solve in Adobe After Effects CS5 .
 
This issue makes working in CS4 with .R3D files almost useless... perhaps worse than, since my tests showed it worked, but rendering out a 5 minute piece at 1080 has taken me over a week due to all the crashing.

Is this happening to anyone else but with non-.R3D sources? I usually work in CS3 but decided to use CS4 on this job to eliminating a lot of pre-transcoding to 4k dpx files.
 
I have had no problems using Premiere CS4 or AE CS4 with footage in HDV from Sony Z1 or footage from the Sony EX-3.

But trying to use R3D footage, anything more complex than a few cuts and I get "low on memory" errors in Premiere and the "Error reading frame from file" error in AE.

So I agree, CS4 is practically useless for R3Ds at present.
 
Don´t know if this will help, but have you tried "secret preferences"?
hold shift (pc) before selecting preferences, in pull down menu click on secret and set purge every 1 frame during make movie. This clears each rendered frame from your memory

bg
alex
 
It helps to some degree, but CS4 is not ready for RED prime-tim yet. Let' hope for CS5, 64 bit will/should help with memory management.
 
I realize this is an old thread - but this worked for me regarding CS4 - Make certain the Adobe cache folders are on internal or eSATA connected drives. Do *not* put caches on external firewire (or USB) drives. This seems to substantially reduce or eliminate the errors.
 
Last edited:
You must log in or register to reply here.
Back
Top