Return-Path: Received: from nk11p03mm-asmtp005.mac.com ([17.158.232.40] verified) by media-motion.tv (CommuniGate Pro SMTP 4.2.10) with ESMTP id 4850519 for AE-List@media-motion.tv; Tue, 18 Sep 2012 17:32:17 +0200 MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; CHARSET=US-ASCII Received: from [192.168.1.68] ([99.152.153.100]) by nk11p03mm-asmtp005.mac.com (Oracle Communications Messaging Server 7u4-24.01(7.0.4.24.0) 64bit (built Jan 3 2012)) with ESMTPSA id <0MAJ0087EXW7F160@nk11p03mm-asmtp005.mac.com> for AE-List@media-motion.tv; Tue, 18 Sep 2012 15:33:44 +0000 (GMT) X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.7.7855,1.0.431,0.0.0000 definitions=2012-09-18_01:2012-09-18,2012-09-17,1970-01-01 signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 ipscore=0 suspectscore=0 phishscore=0 bulkscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=6.0.2-1203120001 definitions=main-1209180101 Subject: BG Renderer script errors From: Jim Curtis In-reply-to: Date: Tue, 18 Sep 2012 10:33:42 -0500 Message-id: <0B93DB0C-43C0-47F4-A4ED-98736CFA915B@me.com> References: To: After Effects Mail List X-Mailer: Apple Mail (2.1278) I'm consistently getting errors with the BG Renderer script. It renders part of my Comp, then fails. I already trashed Ae prefs, which wipes out the authorization, re-authorized. But, I can pretty much depend on it to fail on every render, no matter which project I'm in (meaning I have different source footage on every comp). I also re-installed the Script (overwrote the old file with a backup copy from my zip file). If I use the Ae renderer, my renders finish without errors. Here's the latest error message: aerender Error: After Effects error: Rendering error while writing to file /Volumes/E800/R2_01.mov. An output module failed. The file may be damaged or corrupted. (-1610153464) I have Digital Rebellion's Corrupt Clip Finder, and it didn't find corruption on any of my source files. Any ideas on how to get it working again? Thanks, Jim C.