nuke and render manager – ideal file management workflow

Hi, i’m doing some test using Primefocus Deadline as Nuke’s render manager. If any of you have any experiences on this matter , pls share with me 🙂 , well this is not specific to Deadline but about general file manegement when doing distributed rendering +Nuke .This is my first trial using renderfarm with nuke.

So using deadline, it’s recommended to place the render output into a server. i got a case where i have a very complex script, ussually i will ‘precomp’ at certain ‘checkpoint’ by rendering it out then read it back in and i’ll repeat this steps couple more times. Now, if i submit the project to rendermanager , the render output will be in server side. To deal with my precomp scenario, i need to copy back all the render result locally, so i can get the ‘speed’. This is a bit different compare to 3d animation, where the texture/map etc is not to critical when they have to be in the server, They’ll be needed when rendering. But in Nuke, all the read proccess is very intense, so frame by frame got read successively. So did u do copy all the render output from server back to local ? or u grab the clips directly from network which means you have a bloody fast server + lightning fast cabling.

Also how to deal with the relative path thing? do u convert all the path from all ‘read’ node into relative path or any other method ? so the render slave can get the correct path for all the media/clip etc??

Any suggestion will be great.

thanx.

No Responses to “nuke and render manager – ideal file management workflow”

Post a Comment