Comments on: XML, Python and the Visual Effects Pipeline http://eddieoffermann.com/blog/2008/05/16/xml-python-visual-effects-pipeline/ The reel, resume and contact resource for Eddie Offermann, Pipeline TD, Visual Effects Scripter, CG VFX and Integration Artist Tue, 09 Mar 2010 22:39:41 +0000 http://wordpress.org/?v=2.9.1 hourly 1 By: Cameron O'Rourke http://eddieoffermann.com/blog/2008/05/16/xml-python-visual-effects-pipeline/comment-page-1/#comment-73 Cameron O'Rourke Mon, 15 Dec 2008 01:36:52 +0000 http://eddieoffermann.com/blog/2008/05/16/xml-python-visual-effects-pipeline/#comment-73 Yeah, I guess that makes sense. As long as a human is involved in kicking off the process that says "this asset is ready", it would be very natural to update the project tracker. We are in the beginning stages, but we have an industrial-strength workflow system running under the covers along with email notifications. We could totally mark one task as 'complete', mark the next task as 'in-progress', start putting the assets into position, and put a notification up on the next artists' dashboard. Something that I just realized is that these steps could be driven by workflow, or by the Python script. Hmmm. I had been assuming that we needed a user-configurable workflow system all this time. Do you already have a project tracker, or are you building one? I would be very interested to know what you would like to see in such a tool. Yeah, I guess that makes sense. As long as a human is involved in kicking off the process that says “this asset is ready”, it would be very natural to update the project tracker.

We are in the beginning stages, but we have an industrial-strength workflow system running under the covers along with email notifications. We could totally mark one task as ‘complete’, mark the next task as ‘in-progress’, start putting the assets into position, and put a notification up on the next artists’ dashboard.

Something that I just realized is that these steps could be driven by workflow, or by the Python script. Hmmm. I had been assuming that we needed a user-configurable workflow system all this time.

Do you already have a project tracker, or are you building one? I would be very interested to know what you would like to see in such a tool.

]]> By: Eddie http://eddieoffermann.com/blog/2008/05/16/xml-python-visual-effects-pipeline/comment-page-1/#comment-72 Eddie Sun, 14 Dec 2008 07:58:05 +0000 http://eddieoffermann.com/blog/2008/05/16/xml-python-visual-effects-pipeline/#comment-72 I see absolutely no reason to not introduce this sort of interaction. I think it's a natural! One of the features I'm planning to implement relatively soon is the ability for artists to register their interest in data for a particular shot. For instance, if a lighter is waiting on a camera to be published, the lighter would be able to access an interface (web or inside of Maya) and indicate that they would like to receive notification when a camera or revised animation is available. When an animator or tracker releases the needed asset, the lighter receives an instant message or an email to indicate that their asset is ready. These notifications could even be set up by production coordinators or producers to help speed things along. If there's anything I personally hate, it's having to call/IM/email someone just to say "Hey, that animation data is ready!" Since my pipeline tools are extending to encompass model and texture publishing and eventually even lighting and rendering setups (they already include limited functionality for compositors - and that'll grow soon as well), it's possible for the system to report when an artist has picked up a shot to work on, when they complete it and when it has moved on (or is ready to move on) to the next stage. Reporting this data to a project tracking system is handy. I see absolutely no reason to not introduce this sort of interaction. I think it’s a natural!

One of the features I’m planning to implement relatively soon is the ability for artists to register their interest in data for a particular shot. For instance, if a lighter is waiting on a camera to be published, the lighter would be able to access an interface (web or inside of Maya) and indicate that they would like to receive notification when a camera or revised animation is available. When an animator or tracker releases the needed asset, the lighter receives an instant message or an email to indicate that their asset is ready. These notifications could even be set up by production coordinators or producers to help speed things along. If there’s anything I personally hate, it’s having to call/IM/email someone just to say “Hey, that animation data is ready!”

Since my pipeline tools are extending to encompass model and texture publishing and eventually even lighting and rendering setups (they already include limited functionality for compositors – and that’ll grow soon as well), it’s possible for the system to report when an artist has picked up a shot to work on, when they complete it and when it has moved on (or is ready to move on) to the next stage.

Reporting this data to a project tracking system is handy.

]]> By: Cameron O'Rourke http://eddieoffermann.com/blog/2008/05/16/xml-python-visual-effects-pipeline/comment-page-1/#comment-71 Cameron O'Rourke Sun, 14 Dec 2008 06:24:55 +0000 http://eddieoffermann.com/blog/2008/05/16/xml-python-visual-effects-pipeline/#comment-71 Hi Eddie. I've been working hard on an online collaboration and project tracking tool for VFX (think mashup between Basecamp and VFX Showrunner.) Someone suggested that I should offer Python bindings into the system for ease of integration with pipelines. Do you think this would be useful? Or are pipeline automation and project tracking operating at totally different levels of granularity to be integrated? I'm having trouble coming up with a scenario where this would be useful. Since you are knee-deep in this aspect of the industry which I am not, any insights would be very helpful. Cheers, Cameron Hi Eddie. I’ve been working hard on an online collaboration and project tracking tool for VFX (think mashup between Basecamp and VFX Showrunner.) Someone suggested that I should offer Python bindings into the system for ease of integration with pipelines.

Do you think this would be useful? Or are pipeline automation and project tracking operating at totally different levels of granularity to be integrated? I’m having trouble coming up with a scenario where this would be useful.

Since you are knee-deep in this aspect of the industry which I am not, any insights would be very helpful.

Cheers,
Cameron

]]>