AE render crash 86::2 Help??

[Van Royko]

All was going so well with the premier pro /AE workflow until I tried to render- of course.

It keeps saying "After Effects error: Error (4) reading frame file "F:\DM\A025_C021_1109NH_001.R3D".

(86::2)

When I looked up this error - forums said that it had to do with the length of the path name being longer than 32 characters. I shortened it to 30 and still the same thing.

Has anybody vanquished this troll?

[Van Royko]

The troll isnt vanquished but i think i found the path to defeating it.

It appears that this is a disk speed issue. I plugged the drive in via esata in stead of usb and I am getting better results. Still crashing but much later in the render.

Ill continue this personal journal to hopefully save someone else all these troubles

[Kaku Ito]

Are you using CS4? I assume...

For CS4, if I have video hardware driver installed, it crashes more often.

[Van Royko]

Yes its CS4

And now its as bad as ever....

What do you mean by video hardware?

Thanks

[Uli Plank]

AJA, BlackMagic etc.

[Van Royko]

The Troll is dead

I did it via Adobe dynamic link and not an import of the sequence which is a bit of a bummer. It was so cool to have all the clips seperated in AE but I guess it doesnt work.

Maybe someone else had more success the import way.

P.S. I did this with a 2.2 ghz Dual Core Acer Laptop connected to an external e-sata drive.

Adobe is king of RED post prod right now

[Nate Foster]

I've had this same problem for a little while (after effects only. I don' run Premiere). Drive speed, source location or file name length have had not been a factor because I've tested every one of them. Strangely, this error only hits when I render. Most of the time though, the render fails with no error at all. better yet, since the AFX error log seems to be gone now, it took me hours to figure out that it was this error. (rendering every individual layer of a 70+ layer main comp one at a time until I got the error.)

so far, the issue arises when I have RED footage in a complicated comp. I can place the R3Ds in a comp by themselves and render it with out a problem, but when a bunch of effects and masks are placed on them, they don't want to cooperate. I rendered the R3Ds out as Open EXRs, replaced them in the timeline and the problem vanished.

It looks like the importing of R3Ds into AFX is really good for laying things out and making sure what you're going use; basically a high quality offline. It's still a much faster way to work than the previous methods, but make sure you set your comps up so it's easy to replace your footage before the big render.

[Ivan Cortazar]

I am experiencing the same problem. It is really bad and is completely F*&^& my workflow. I am doing a lot of compositing in AE and if I use the r3d keeps crashing when trying to render with multi processor. And it is pretty random. Sometimes would render out 1 second, and another times would render 35 seconds. I am trying to render now without multiprocessing. But render times rise 4 times. I'll see if this way it works.

I am glad Adobe is incorporating the 3rd workflow, but CS4 is So buggy that it is really killing my patience.

Sorry for my ignorance, but how do you render out as Open EXR? Do you do that in AE? Thanks

I rendered the R3Ds out as Open EXRs, replaced them in the timeline and the problem vanished.

[Kenn Michael]

This solved all my 86::2 problems...

http://www.reduser.net/forum/showthread.php?t=30553

Also, rendering with multiprocessing on doesn't work for me either. Muffinny, I assume you're on OSX? I find that AE doesn't handle memory that well in OSX. I have 16GB RAM, and when I use multiprocessing (even with leaving enough memory for other applications) AE starts grabbing more and more RAM, and within minutes, I'm into disk swap and everything slows down to a crawl. Using the purge after every frame and turning multiprocessing off (as well as not using 32bpc with 4K R3Ds) gets me through renders problem free.

[Ivan Cortazar]

This solved all my 86::2 problems...

http://www.reduser.net/forum/showthread.php?t=30553

Also, rendering with multiprocessing on doesn't work for me either. Muffinny, I assume you're on OSX? I find that AE doesn't handle memory that well in OSX. I have 16GB RAM, and when I use multiprocessing (even with leaving enough memory for other applications) AE starts grabbing more and more RAM, and within minutes, I'm into disk swap and everything slows down to a crawl. Using the purge after every frame and turning multiprocessing off (as well as not using 32bpc with 4K R3Ds) gets me through renders problem free.

Thanks Kenn, I also have 16Gb of RAM. I'll give a try that tip. I did the render without multiprocessing on. And it worked but what it was a an unfinished render of roughly 1 hour (with multiprocessing) became a 4 hour render. But at least it finished.

Thanks again.

Ivan C.

[David Nardini]

This solved all my 86::2 problems...

http://www.reduser.net/forum/showthread.php?t=30553

Also, rendering with multiprocessing on doesn't work for me either. Muffinny, I assume you're on OSX? I find that AE doesn't handle memory that well in OSX. I have 16GB RAM, and when I use multiprocessing (even with leaving enough memory for other applications) AE starts grabbing more and more RAM, and within minutes, I'm into disk swap and everything slows down to a crawl. Using the purge after every frame and turning multiprocessing off (as well as not using 32bpc with 4K R3Ds) gets me through renders problem free.

Exact same problem here ... had to switch off multiprocessing and used the 'secret menu' ... now no issues with rendering / shutting down AE, but render times are high ! REDAlert/REDrushes is way way faster ...

[Curtis Abbott]

I am having trouble with this issue, but the link to the thread must be messed up it keeps sending me to a thread about a red cradle for sale. Whats the secret to fixing this problem?

[JanneJansson]

Turn off multiprocessing.
Turn off open open gl.
If that don't work press shift+alt+apple and the select preferences again, now the secret menu is there and then check disable layer cache and ignore errors.