Just wondering where you guys enter your plates? We have a couple shots that have 14 layer's of different plates, all of which need different in and out times. We did log the plates as tasks on the last show, but there was only one layer needed.
Thanks
ed
We put them under elements -> versions.
Project -> [Opt. Scene] -> Sequence -> Shot -> Element -> version -> link to frame
Our view is all footage is an element whether that be 3D renderings or live action. Assets only keeps track of scene files and compositing workspaces. So assets may or may not create elements.
I'm finishing up our Nuke Gizmo right now (Alchemy) which handles all the file pathing for elements based on version. You define a read node as an element and then choose from a list of versions.
So the artist chooses:
Project 01 -> Seq_010 -> Shot_050 -> ShadowPass
and then it lets you choose from a list of versions of that element whose pathing is in the version "path_to_frames" field. If a new version shows up then it's easy to alert you that a read node is out of date. Just choose the latest version and hit update.
Thanks for the tip, I didn't even have the elements active on our site...
Now that I have this working, is there are way to do calculations? I see there are summaries, basically I want to be able to automatically get the total frame count of a plate based off in and out frame #'s.
Time code arithmetic I think was just added in the 1.9.4 patch on Sunday. Haven't tried it out yet though.
Yep, Elements is where many of our clients enter in their Plates info. Often it would be an Element where the 'type' is 'plate'. Some studios also choose to track these as Assets though. Seems like Gavin's got a good method for using Versions to keep track of the iterative work on these as well.
Calculated fields (like you mentioned you'd like to create for frame count on your plates) haven't surfaced yet. They are on the roadmap for later this year. We will be releasing query fields in 1.13 which is the ability to create a field that summarizes data on other linked entities. So for example, you could create a field on Shot called 'number of smoke elements' that is a query that simply counts the number of Elements linked to the current Shot that have category = 'smoke'. These fields are only able to provide summary data for this first pass, but we'll be expanding on the idea over the course of the year.