| ||||||||||
| That's a great solution, I've not noticed that in default folder. Thanks for the tip! On Sep 18, 2012, at 9:10, Jim Curtis <jpcurtis@me.com> wrote: > On Sep 18, 2012, at 11:05 AM, rik bogusz wrote: > >> This might sound weird, but are you creating new . Mov files or writing over a previous render? I've found if a file is selected in the finder, its seen as an open file, and bgrenderer will not write and fail with an error > > > Like you, I've discovered that BG Renderer doesn't like over-writing a previous render. That almost always produces a failed render. > > I've found Ae to be very hit and miss about over-writing a previous render as well. Some times it works, others it gives an error message. > > So, now I use Default Folder's Send to Trash feature (very handy) in the Export dialog box before I re-render with the same file name. It's an extra step, but it eliminates that type of error. > > > >> On Sep 18, 2012, at 8:57, Jim Curtis <jpcurtis@me.com> wrote: >> >>> On Sep 18, 2012, at 10:44 AM, Rendernyc wrote: >>> >>>> Is it failin in same spot every time? >>> >>> Since it's been failing on every Comp in every project, no. >>> >>> But since I subscribe to the definition of insanity as doing the same thing over and expecting different results, I usually switch to Ae rendering after BG Renderer fails once. >>> >>> But, for the sake of trying to find a solution, I'll try a second or third render on the next project, and see if there's a pattern. >>> >>> I usually expect renders to fail on the first frame of a layer, when a plug-in or source media corruption is encountered. But, I'm getting the fails in the middle of layers. >>> >>> >>>> Are you rendering to a network volume? >>> >>> No. >>> >>> >>>> When rendering from in AE are you rendering exactly the same way and same destination as when BG? >>> >>> >>> Yes. >>> >>> >>> I neglected to supply my system spec: MacPro3,1, 32G RAM, Quadro 4000, RAID5, 10.7.4, Ae CS6 >>> >>> Thanks! >>> >>> Jim >>> >>> >>> >>>> On Sep 18, 2012, at 11:33 AM, Jim Curtis <jpcurtis@me.com> wrote: >>>> >>>>> 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. >>>>> >>>>> >>>>> >>>>> +---End of message---+ >>>>> To unsubscribe send any message to <ae-list-off@media-motion.tv> >>>> >>>> +---End of message---+ >>>> To unsubscribe send any message to <ae-list-off@media-motion.tv> >>> >>> >>> +---End of message---+ >>> To unsubscribe send any message to <ae-list-off@media-motion.tv> >> >> +---End of message---+ >> To unsubscribe send any message to <ae-list-off@media-motion.tv> > > > +---End of message---+ > To unsubscribe send any message to <ae-list-off@media-motion.tv> |
