I am more familiar with Arnold and render man but I feel like the benefits of this would be minimal since often you need to evaluate the entire scene anyway (for gi etc), so you would have to do this 4 times per frame instead of once. It would save you time if you had an extreme amount of disposable cores, but usually that isn't the case. On Mar 7, 2016 7:45 AM, "Brian Savery" <[email protected]> wrote:
> Well this of course is dependent on the renderer design and the original > idea didn't mention if he was using cycles or another renderer. > > But yes what Campbell said is basically the case for the most studio > render farms. 1 frame per machine. Especially for animation. Only people > I've seen that split them usually if you're trying to get iterative renders > out, i.e. Tweaking lighting and you don't have an interactive preview > render or you want to see the final render. Or like he said with large > resolution non animating print renders like 10k or something > > Also not sure this is the case with cycles but some renderers embed the > "border" feature window area in the metadata of the image so you don't have > to save the crop coordinates in the file name. > > Shameless plug we do the above with RenderMan and actually include a > command line tool called "tiffjoin" which stitches them all back together > (if they're tiffs) automagically. > > > This is possible via border rendering, >> http://blender.stackexchange.com/questions/47274 >> >> However for animation its almost always best to render an entire frame at >> once, >> since loading the geometry, textures and creating the BVH-tree would >> need to be done for each tile. >> >> The only time this could give you some gain is if you had more >> computers then you have frames to render. >> Or when the frames are high enough resolution, the frame needs to be >> split up because of memory restrictions. >> >> On Fri, Mar 4, 2016 at 8:38 AM, ArM <[email protected]> wrote: >> > I started thinking about render farms and I realized that it would be >> good >> > feature for Blender, if you could split your frames to multiple >> servers. The >> > method would be similar as what we do when we create panoramas with irl >> > cameras. >> > >> > It (maybe) has to have a "hidden timeline" that splits every frame to >> chosen >> > amount of frames and turns the camera automatically so you get every >> frame >> > as a panorama composition. >> > >> > For example if I'm creating an image or an animation with size >> 1920*1080, I >> > would like to split it to 4 frames, that are every single one as >> 480*270. >> > Then with compositor or Photoshop or what ever I could join them back >> > together as one single frame. The idea came to my mind when I was >> thinking >> > of one specific renderfarm: https://www.sheepit-renderfarm.com >> > >> > If you could split your animation to smaller tasks to multiple servers >> at >> > once, it could make the rendering little faster since slower computers >> > cannot slow the rendering process that much as they could do if they >> had to >> > render whole frame at once. Or am I wrong? >> > >> > I'm not a programmer myself, so I just ask if someone understands the >> > benefits of this and how this could be done, or is even interested to >> > develop this idea further. >> > >> > >> http://blenderartists.org/forum/showthread.php?393876-Is-there-a-script-to-create-panoramas >> > >> > >> > _______________________________________________ >> > Bf-python mailing list >> > [email protected] >> > http://lists.blender.org/mailman/listinfo/bf-python >> > >> >> >> >> -- >> - Campbell >> >> >> ------------------------------ >> >> _______________________________________________ >> Bf-python mailing list >> [email protected] >> http://lists.blender.org/mailman/listinfo/bf-python >> >> >> End of Bf-python Digest, Vol 130, Issue 4 >> ***************************************** >> > > > -- > [email protected] > 508-274-8700 > > _______________________________________________ > Bf-python mailing list > [email protected] > http://lists.blender.org/mailman/listinfo/bf-python > >
_______________________________________________ Bf-python mailing list [email protected] http://lists.blender.org/mailman/listinfo/bf-python
