Efficient network workflow

Hi, I’m facing a network workflow problem with Nuke.

I’m working with a team of compositors and they need to pass the same script each other so the read nodes must be pointing at the same network place. Using local files isn’t an option cause we need to pass the scripts each other very frequently.

The problem is the speed: working in an 1GB ethernet network is like 10 times slower than do it localy. I think working this way isn’t reasonable due to low eficiency but at the same time, it’s better than having to relink all the files constantly. I’ve tried to use DiskCache after every read node but they only cache files for the script used, so if I save a new version the cache is missed and I must preche everithing again…

I’m very frustrated cause Nuke is suposedly designed with network and team work in mind and cannot see how is this possible with the actual workflow since working in a 1gb slow network (not fiber channel) isn’t practical.

Any suggestion?

Also I would like to know how are you people working with teams in network environments with Nuke.

Many thanks.

No Responses to “Efficient network workflow”

Post a Comment