[Bf-cycles] Network Rendering

[Vincent Olivier]

Hi Brecht,

“up4” would be my first choice as a username for the wiki.

I will look at the code and be back with questions/comments.

Is there anything else beside "cycles/src/device/device_network.*” I should be looking at?

Regards,

Vincent


> On Jan 1, 2017, at 10:41 AM, Brecht Van Lommel <brechtvanlommel at pandora.be> wrote:
> 
> Hi Vincent,
> 
> I can create a wiki account for you, just me know the username you want.
> 
> Have you looked at the existing network rendering code? It's
> unfinished but does some things you propose, in particular
> cycles_server is somewhat similar to your cyclesd. Ideally you could
> help with that so that we're all working on the same thing.
> 
> It doesn't have all the features you mention, and is not based on
> streaming XML but rather device buffers. Discovery is using a simple
> broadcast, and the device info is limited, both could be improved. The
> advantage of the device buffers over XML is that it more easily works
> works for viewport or animation rendering with incremental updates.
> Further it can work as if there was just another device like a CPU or
> GPU from the point of view of Cycles integration in various
> applications, whereas if the scene has to be encoded in XML and
> decoded again on the server that adds extra code complexity.
> 
> Also see some ideas on network rendering here:
> https://wiki.blender.org/index.php/Dev:Source/Render/Cycles/Network_Render
> https://wiki.blender.org/index.php/Dev:Source/Render/Cycles/Devices
> 
> Regards,
> Brecht.
> 
> 
> On Sat, Dec 31, 2016 at 8:37 PM, Vincent Olivier <vincent at up4.com> wrote:
>> Hi,
>> 
>> I’m just posting here my intention to work on a network rendering feature for Cycles for your consideration. Comments are more than welcome. Maybe if someone could give me a Wiki account I could post my ideas and the discussions I will have with people interested in those features.
>> 
>> I’m still struggling to have the “blender_dependencies” build for Linux, Windows and macOS so I can test my code on all of those platforms. I’m writing this as it’s compiling.
>> 
>> My plan is to start with the Cycles command line standalone to create a new “cyclesd” binary that would be a POSIX daemon and Windows service, with all it’s dependencies statically linked for portability.
>> 
>> This service would advertise itself via Bonjour/zeroconf/avahi and publish it capabilities, versions, benchmark/core count for OpenCL, Native and CUDA and be discoverable by yet another command line utility client that would be able to stream the XML scene with all textures, geometry and other dependencies to the remote deamon. The command line is responsible for decoding (FFMPEG, OpenImageIO, OpenVDB, etc.) everything on the file system and sending only XML scene description with in-line (base64?) textures, maps, meshes, volumes to the deamon. Maybe it would be better to use something like msgpack instead of XML between server & clients, I’m not sure…
>> 
>> The server would send back RAW film (with Cryptomatte data, etc.) to the command line client who would then serialize the render back onto disk according to the user wishes.
>> 
>> I am sure there has already had lots of brainpower invested in this so I’m still looking to gather it all in one place (wiki most probably).
>> 
>> Regards,
>> 
>> Vincent
>> _______________________________________________
>> Bf-cycles mailing list
>> Bf-cycles at blender.org
>> https://lists.blender.org/mailman/listinfo/bf-cycles
> _______________________________________________
> Bf-cycles mailing list
> Bf-cycles at blender.org
> https://lists.blender.org/mailman/listinfo/bf-cycles