Action render slower in batch

[ddinisco]

I realize that this been like this for a while, but perhaps some can explain why rendering an multi-layer setup in action (not in batch) is so much faster that rendering that exact same action setup in batch…assuming that the action node is the only element in the batch setup.

On average the relatively simple setup that takes 2:00 in action will take 7:00-8:00 with that same action loaded into batch.

I have tried this on flint and flame and on every version since 2007. 2010 ext1 is no different.

Just curious if anyone has any insight on this.

Thanks
David

[Anonymous]

Exactly same action setup ? number of layers, resolution, sampling, z-buffer … ? if you save your action setup and you load that into the batch, you don’t find the same rendering time, that’s correct ? and are you make a difference between your two different process ? you saw a difference (with burst the gain of the difference).

I try this today on flame ’09…

[cmb lit]

can you post your action-setup?

i also have the feeling that rendering in batch is slower.

[claudio antonelli]

I haven’t experienced that personally (it’s a long time since I used action alone), but it could be GPU related… Isn’t that the reason why Action’s transfer modes can’t do transparency?

[Anonymous]

I make a test concerning your problem and this is my result : I create a simple action with five layers and I save it, the processing time is 14 second, then I load my action in the batch mode,
the processing time is 19 sec. So there was a big difference of processing between action in the batch mode, I think this come from Ui, the batch mode need more ressources than action on desk mode.

Tested on Flame 2009.

[Anonymous]

It is not specific to any one setup, so any action setup will do. The time difference becomes exponentially greater as the complexity of the render increases.

[cyril conforti]

you really need to do a test with a more complex setup. the difference between 14 and 19 seconds is 25%, but that could easy be accounted for by slight discrepancies in your timing methods. imagine a setup that took 2minute 14 seconds compared to 2 min 19 seconds, thats not much. but 2 minutes compared to 3 minutes is significant.

[Anonymous]

Yes but I juste did a quick test.
You right, if we calculate that in “%”, it’s not insubstantial for a 5 minutes processing time that’s right, but in a action we can just make a color correction, make a blur, use keyer in other words … it’s not very heavy effect like defocus or complexe batch with many nodes, whatever , I think you need a huge compositing with lot of layers to compare that, by the way, like andy_dill say I don”t now if lot of people use only action right now.

( I apologized for my english, I need more training 🙂 )

[claudio antonelli]

60 frames of monochromatic noise – 12 bit HD 1920×1080
one layer, matte off, one displacement – z=600
resolution to all: 1
AA: 8 sameples

time in action (from hitting “process” to the fish turning back into the cursor): 2 min, 15 sec.
time in batch: 2 min, 15 sec
(timed on my iphone stopwatch–flame’s time estimates were dead-on as well)

for whatever it’s worth.

[Anonymous]

Interesting, I don’t understand why I had this difference.

[Roger Koller]

@ddinisco 28859 wrote:

I realize that this been like this for a while, but perhaps some can explain why rendering an multi-layer setup in action (not in batch) is so much faster that rendering that exact same action setup in batch…assuming that the action node is the only element in the batch setup.

On average the relatively simple setup that takes 2:00 in action will take 7:00-8:00 with that same action loaded into batch.

I have tried this on flint and flame and on every version since 2007. 2010 ext1 is no different.

Just curious if anyone has any insight on this.

Thanks
David

Lets try to put the layers outside of action into batch. This operation usually works better with me. The time of render usually reduce.

Good luck!!!

[Martin Furness]

I have done several tests as well and found that Action is faster in certain situations!

[Saran Sirikasamsap]

100 frames of monochromatic noise – 10 bit HD 1920×1080
one layer, matte off, one displacement – z=200
resolution to all: 1

time in action (from hitting “process” to the fish turning back into the cursor):18secs.
time in batch: 20secs

a few guesses :
u might wanna check your clip history settings that might make batch slower ? and also check batch caching > if the “fill with intermediates” button is on that might slow things down a bit ?

[Margaux Durand-Rival]

hello guys, i think reason is Batch has 12bit processing even if action is 8bit, so it’s reason .. try it with 12bit action from desktop and same setup in batch and you’ll see..

Cheers,
V.

[Scott Balkcom]

actually, with a friend we were working on this project, it was a small batch, but we had like 3 action, right, at proxy from HD it was taking about 40.
we deleted 2 actions that we could replace directly with a color corrector and logic ops, and ther render full resolution only took 20 mins.

sincerely what i think, is that the inferno goes through all of the stuff in the node, and analizes them even if they´re doing nothing, just like maya would.

it really sucks, and then i understood why you have all of the stuff in the action separated by nodes.
anyhow.

cheers!

[Author]

Posts