Comments on: BG Renderer

By: Lloyd Alvarez

Lloyd Alvarez — Tue, 10 Apr 2012 13:56:22 +0000

Please contact support and include your AE and OS version and if possible let us know the full path of your AE project.

By: Ricky Carter

Ricky Carter — Tue, 10 Apr 2012 00:40:34 +0000

That doesn’t fix it either.

By: Lloyd Alvarez

Lloyd Alvarez — Mon, 09 Apr 2012 19:02:29 +0000

Besides firewall and virus software another thing to check is to make sure you don’t have any unusual characters in your file path or project name.

By: Ricky Carter

Ricky Carter — Mon, 09 Apr 2012 18:59:52 +0000

I’m having the same problem.

By: Lloyd Alvarez

Lloyd Alvarez — Wed, 04 Apr 2012 18:11:28 +0000

Sounds like an issue with your comp. Can you try a simple test comp to see if you successfully launch a multi-item-queue render?

By: yann

yann — Wed, 04 Apr 2012 18:06:22 +0000

>>> another interesting development in analyzing the problem.

> having 3 project in the queue > at the end of the first one. about 5000 frames. when the next one kick in > Each process ( 4 ) try to render > and crash/freeze on the first image. 0 k image is written in the folder. but the render is stopped.

>>> since the background render start with a RED IMPORTER error. but is okay to render the images of the first queue project…. well… who knows right ?!…

>> the thing is >> bg render stop to be awesome and kickass !

anyhow >>> thanks for reading and taking the time to have a look at it when you can.

Cheerz!
yann

By: yann

yann — Tue, 03 Apr 2012 18:51:55 +0000

>> update on my problem > >> if i wait for 30 seconds the render start.
> yesterday night was a hurry moment kind of post prod moment )) where this error message was not welcome and 30 seconds to wait … hum… not good ))
any way >> still have this adboe after effect new “situation” where >>

> load project. with render setup already done .

Launch BG render.
Activate again the comp I want to BG render

Bg Render ask if I want to save the project.

SAY/clic YES.

After effect crash. ALL THE TIME.

… >> painfull solution for now >>> load project > launch Bg render. kill Ae. start Ae. and re do the operation each time I want another Bg render process.

ANY IDEA ? memory ? hard drive not being cooperatives ?
(brand new SSD 6g !

anyway >> THANK YOU FOR ALL YOUR GOOD WORK !!!
yann

By: Kiran

Kiran — Tue, 03 Apr 2012 17:43:23 +0000

Thanks Alvarez ,

By: yann

yann — Tue, 03 Apr 2012 02:37:37 +0000

hello,

big crash with bg render 2.o and red import pluggin involve in the comps i am working with.

any idea ?

thanks.

Sorry > system is PC. windows 7 64bits. all last update done. including the latest adobe ones.
after effect 10.5.0.253
system has 48 GiG of ram.
and SSD 6g drives.

By: Lloyd Alvarez

Lloyd Alvarez — Mon, 02 Apr 2012 19:35:02 +0000

Correct, BG Renderer renders using aerender which is the command-line GUI less render engine so it renders on the CPU only.

By: kiran

kiran — Mon, 02 Apr 2012 19:24:42 +0000

Hello

When simply render to avi file output , AE does uses the GPU (i can activity in GPU gadget).
If I render same project with same setup using BG-renderer then GPU is not being used(no activity in GPU gadget.

is this expected behavior with BG-renderer ?

thanks
Kiran

By: Reuben Armstrong

Reuben Armstrong — Fri, 23 Mar 2012 15:15:55 +0000

I deleted all my adobe preferences and it solved the issue, no idea what was causing the problem specifically though.

By: Allan Thrush

Allan Thrush — Fri, 23 Mar 2012 15:08:07 +0000

That was my thought as well… we’re running AVG here, so I tried shutting it down and trying it, but still with the same results. Maybe there’s some other process that’s running that I don’t know about.

By: Lloyd Alvarez

Lloyd Alvarez — Thu, 22 Mar 2012 21:26:55 +0000

Are you running any firewall or virus protection software that might be killing the process?

By: Allan Thrush

Allan Thrush — Thu, 22 Mar 2012 21:23:43 +0000

We have Mac and PC in our edit facilities… I’m trying to run the trial version of BG renderer on our PC’s. When I set up the render to go, everything goes smoothly until the script tries to launch the msdos window. The window appears for a fraction of a second, and then disappears. Do you have any ideas as to what would be killing the window?

I tried the script on the Mac and it works fine.