Indigo Renderer Forum

Hey Guys,

I just noticed that Indigo nowadays does stop rendering if its saving a file and slaves stop to render during File transfer.

This can't be on purpose, so I write it as a bug.

With this behavior rendering big rez for print with LightLayers and Supersampling @ 3 does slow down the whole rendering performance a lot.
Transfering a multiGB file for 30sec on a slave is 30sec of rendertime lost, this time should be used!
Same for saving big IGI and EXR for the master... this is done by default very often and can take quite some time!

Please fix this, since it seems to be a ugly bug or a very disputable design decision...

It's by design. The alternative is to copy then buffer, then send it over the network, but in that case it will require more RAM. Can't have it both ways

Bucket Rendering would help here
http://www.indigorenderer.com/forum/vie ... f=5&t=9961

Its quite some time ago that I did Network rendering this intense like now, but I can't remember that this issue was there back in the days.... maybe simply the stuff I do for work become bigger and now its impossible to miss the CPU idling...

The behaviour did change at the time that we added integrated alpha rendering.
I could change it back, but it would require a duplicated render buffer on the slaves.

Or dividing the buffer/image into two parts, rendering on one, and switching to other while uploading the first?!
Best would be to render every second pixel creating a checkbord pattern.
Would also reduce network traffic by 50%

How about bringing back the "-frame_upload_period" command?!
By that I could be back in controle of the upload times and adjust it to my needs.

Even sweeter would be a button next to each slave in the master GUI that forces the slave to send over the renderprogress

After a bit of thought, I think I'll change the slave behaviour back to making a copy of the buffer, then sending the copy. This will allow it to render while transferring the frame over the network.

Zom-B wrote:How about bringing back the "-frame_upload_period" command?!
By that I could be back in controle of the upload times and adjust it to my needs.

Even sweeter would be a button next to each slave in the master GUI that forces the slave to send over the renderprogress

As mentioned in the chat, we will look into adding 'min_frame_upload_period' and 'max_frame_upload_period' settings. Also I'll look into a 'send frame' button at some point.

OnoSendai wrote:After a bit of thought, I think I'll change the slave behaviour back to making a copy of the buffer, then sending the copy. This will allow it to render while transferring the frame over the network.

This methode could maybe whipe out some user systems regarding RAM. Some Supersampling a few LightLayers and boom!
(some smart detection of availible RAM and deciding if its possible or not would be a godd solution, or do you refer by buffer the saving to HDD?)

BTW: MatID and other Renderpasses also have LightLayers if scene defines them... maybe they shoul be disabeled here to save availible RAM

OnoSendai wrote:As mentioned in the chat, we will look into adding 'min_frame_upload_period' and 'max_frame_upload_period' settings. Also I'll look into a 'send frame' button at some point.

A mentioned in the chat: great news!!!
(I wrote in this thread earlier before we met in irc)