Multiple tasks of same kind

Discussions related to all NIM connectors.
Post Reply
Posts: 62
Joined: October 4th, 2017, 3:12 pm

Multiple tasks of same kind

Post by quang.tran »

We're testing NIM connectors in Nuke. A basic question how to handle this case: you got a shot with several comp tasks to do, which are clearly different kinds of work, like a) create the splitscreen b) do the retouches for the right side. I'd like two artists to work on it in parallel, so I dropped different compositing tasks on it. Using NIM connector in Nuke (-> Open), I can just start with SHOT_comp_v01. There aren't two different compositing tasks, just one. How is the concept, if different artists are working on the same shot with the same kind of task?

User avatar
Site Admin
Posts: 292
Joined: June 24th, 2014, 8:10 am

Re: Multiple tasks of same kind

Post by andrew »


The task you see listed when you open/save a file is a task type, not an assigned task. Files are associated directly with the asset or shot, and not the specific task assigned. This was done for 2 reasons. First we didn't want to block artists from saving their work if they haven't already been assigned a task. If you so desired, you could work in a NIM project structure without the need to assign every artist a task before starting their work. Second, files can be put down and picked up by different artists without breaking the version stream into segments. All versions live under a basename which is comprised of the asset or shot name, the task type, and a tag. These tags allow users to differentiate different types of comps for example. On the same shot, one artist maybe be working on the comp of an explosion, and another on beauty cleanup. In this case they each would add a unique tag when saving their initial version... ie.

sh01_comp_exp_v01.nk or sh01_comp_btycln_v01.nk

Each successive version will be organized in the project structure and in NIM under this unique basename. Selecting "COMP" as the task when opening a file will filter all the base names that are of "COMP" types.

Now the output of these files... ie renders/dailies ARE associated with the users task. The concept here is that any individual task will have an output to be shared, and we can organize the output by the tasks so we can see successive versions for that specific assignment.

Hopefully that sheds some light on things...

Post Reply