Hasta La Motion!

Thanks,
Lou

Since opening its doors in 1998 with 30 staff, Double Negative has grown to 800 staff, making it Europe’s largest provider of visual effects for Film.

Double Negative is held in high regard globally for its commitment to creative excellence and for its work on projects including Inception, Iron Man II, Quantum of Solace and Prince of Persia. They have also received two VES Awards for their work on The Dark Knight and Sherlock Holmes. Current projects include, John Carter of Mars, Paul, Harry Potter and the Deathly Hallows Parts 1 & 2 and Captain America: The First Avenger.

Matt Holben, CEO at Double Negative, said:

“NUKE has continued to consolidate its position as the dominant software on the market for high-end compositing. The freelance pool of artists with NUKE experience has grown significantly and The Foundry’s on-going commitment to invest in research and development is impressive. These factors have led us to commit to NUKE for the future.

Double Negative and The Foundry have worked together for a long time, and share a common ethos of close collaboration with customers. We look forward to progressing further with NUKE.”

Bill Collis, CEO at The Foundry, said,

“We are delighted that Double Negative has embraced NUKE. When we’re out and about in the industry they are often held up as an example of a facility doing fantastic work and we are proud that NUKE is now contributing to that.”

Double Negative also recently invested in MARI, The Foundry’s brand new creative 3D texture painting application.

http://www.thefoundry.co.uk/articles…-site-licence/

Here’s the issue:

Currently the sup sets up the various writeout settings for the show and the artist imports that script into theirs and just attaches it to the end. The problem is if there are any changes to that writeout portion, the artists are responsible for updating any scripts that need to be rerendered with the new writeout nodes. If they go back a couple versions chances are that eariler version doesn’t have the latest writeout nodes and they often forget to update it, ets.

I’d like to have a centrally located writeout script that is called at the time of rendering (assuming they render using a custom render command rather than interactive). If the sup updates it then all work, even past scripts, would automatically get the changes, no extra effort on the part of the artists.

It seems like the way to go is to treat the artists scripts like a precomp with an output node at the bottom (below a precomp write node) and to then have a precomp node at the top of the writeout script tree. The custom render command would actually fire off the Writeout script and environment variables and runtime arguments would tell it what shot and script to reference. The issue is that the precomp node doesn’t appear to like environment variables or commandline passed arguments. It only works with a hard code line.

My question is, is there either a) anyway around this to be able to feed the File field of the precomp node variables at run time, or b) a better way to acomplish what I want to do, i.e., have a centrally called Writeout script?

Thanks for any help you guys might be able to give me,

Dan

I´d like to ask the experts how I could have a gizmo that runs a function when the gizmo is loaded. I need that to happen not only when I execute a command to launch the gizmo for the first time but also when I save the file and reload again.

The idea is that I have a select box, whose values need to be filled with the names of the files on certain directory. I know how to do that by pressing a button, but I don´t want the user to press the button whenever he/she opens the nuke script.

Is there any solution to this?

Thank you in advance!