-
After Effects write error (DPX files)
Hello,
I’ve been getting an odd error whenever I try to write DPX files in either AE 6.5.1 or AE CS3 8.0.1. The error reads as follows:
After Effects error: writing to file “Comp 1_00000.dpx” (1450).
( 3 :: 141 )This is only happening on one new machine, and the project renders fine on other systems. The problematic system is a Dell XPS 720 w/ 4GB ram.
Any help would be appreciated.
Thanks,
John -
11 Replies
-
Try 8.3 file format?
Try writing to a different drive? -
I’ve tried rendering to several different drives, and just tried 8.3 file naming. Neither solves the error. Thanks for the suggestion, though.
John
-
Hmph. Odd.
Can you render to Cineon, and if so, will it be accepted by whomever is receiving the files?
(sorry, I have no experience with log, so I may be way off base)
-
The machine cannot render either Cineon or DPX file sequences, although it can read and use these formats (it just fails trying to write them). By the way, the machine is running XP SP2.
-
Silly question: is the project 16-bpc or 8-bpc?
-
The project is 16 bpc, but I’ve tried 32 bpc and 8 bpc with no luck.
-
Hm. How about Quicktime version?
-
Quicktime is version 7.2 (I could upgrade to 7.3, but 7.2 is on my other machines, and they render DPX files just fine).
-
We’re running out of options here (duh). I can only suggest that you look at differences between the machines, and maybe see if there is an app running in the background that is causing trouble. Such as the evil Norton Utilities.
Other than that, I’m stumped. Sorry.
-
TikiTim on the Adobe boards has found a solution. It requires going into the After Effects preferences and turning off Asynchronous file reading and writing.
I had to change:
“Asynchronous file reading and writing” = 01
to
“Asynchronous file reading and writing” = 00I needed to do this for both AE 6.5.1 and 8.0.1.
Here’s a link to the thread with the solution:
https://www.adobeforums.com/webx/.3c054946/2This solution works, but it’s confusing since I’ve never had this problem on other machines. The problematic machine is the newest and fastest of the bunch, so it’s disconcerting that it had this error. Hopefully, I’ll get more insight into the details of this problem.
Thanks,
John
Reply to this Discussion! Login or Sign Up