night renders

[Gyuri]

Hi,

Unfortunately I have no burn available, but some of my setups took too long to render recently. Is there any way I process several action and batch setups after each other at night?

Thanks.

pH.

[pixelmonk]

You can load as many batch/action setups as you want into Batch, just be sure you are on Append not Replace when you load them, then hit render. They will render one after the other.

Paul

[Saran Sirikasamsap]

and use “robot” mode to render, so flame will startup, go to the project, render the specified setup, save on desktop and exit

@paul_round 31409 wrote:

You can load as many batch/action setups as you want into Batch, just be sure you are on Append not Replace when you load them, then hit render. They will render one after the other.

Paul

[shannones riders]

Thanks Paul. I actually use this every day, I just didn’t think…:)
I have no clue about the “robot” mode. What is it actually?

[Anonymous]

what on earth are you rendering? what hardware are you on? nothing these days should really take more than 10-15 minutes.

[Anonymous]

what on earth are you rendering? what hardware are you on? nothing these days should really take more than 10-15 minutes.

[Saran Sirikasamsap]

flame -J -U -b

@pixelHussar 31419 wrote:

Thanks Paul. I actually use this every day, I just didn’t think…:)
I have no clue about the “robot” mode. What is it actually?

[shannones riders]

Thanks rohit.

@jayrandall 31426 wrote:

what on earth are you rendering? what hardware are you on? nothing these days should really take more than 10-15 minutes.

One year old HP here. I agree and as you can see I’m not get used to it at all either.:)
These renders took 15-25mins long since I used few sparks on 3K footage. Normally this wouldn’t be that much, but I had to do it on many shots. So I left it running at night.

[Anonymous]

sounds like proxies could be your friend during the day, and full-rez render at night.

[Romeo Reidl]

Proxies are dangerous! Every time I build up my confidence by using a bunch of simple stuff, I’ll try them again on a really heavy comp and get completely hosed. On my last big project, I had an Action node that would insta-crash Flame whenever I clicked on it unless I un-hooked and re-hooked all its connections beforehand. Also, proxies still occasionally rescale my garbage masks.

[Nicholas Fox]

@jayrandall 31425 wrote:

what on earth are you rendering? what hardware are you on? nothing these days should really take more than 10-15 minutes.

when I turn on motion blur and up the anti-aliasing north of 1, I routinely get long renders
on an HP… two weeks ago I had a 30 second animation that took 9 hours to bake. It’s not
hard to hit those time-suckers at all…

[Saran Sirikasamsap]

on a Z800 ? do u switch off Mblur for layers that dont need it ?

[Anonymous]

Proxies are dangerous? So its coffee if you spill it on yourself, but, we all drink coffee, right?

It’s all about the right application? Proxies cut your renders in half, even less, and that means more revisions.

[cyril conforti]

since Burn is now free, why not just get a license for that machine. create an empty Burn group in Backburner, and in DLCFG make that group the Default Burn group for your flame. Sumbit your jobs and they will sit there in the queue waiting. At night assign your machine to that group, and BOOOMM… they start rendering. In the morning, take your machine out of that group.

[Doug Meyer]

don’t forget motion blur is keyframable as well, this has saved me heaps of render time.

[Author]

Posts