Logging/Source data

[reinecke]

There should be schema to contain classic logging/source data.

Candidate items could include:

• reel/tape name
• Production Name
• scene
• take
• slate
• shoot day
• shoot date
• Circle take (true/false)

Open Questions

• Would this attach at a Media Reference or clip level?

References

• FCP 7 XML filmdata element
• FCP 7 XML timecode/reel element
• Avid Log Specification - starting page 97 of this user guide
• OpenEXR Standard Attributes - Editorial

[reinecke]

Below is a screenshot of logging metadata for an ARRI sample file from the ARRI Reference Tool:

[BrandonBussinger]

From the above I would attach the reel/tape name to both the media and the clip along with 'start' and 'end'. It is typically these parameters that establish a relationship between a clip and any media reference. =

The remaining are all values I would typically describe as 'Slate' metadata specific to various production methodologies (US Scripted Features, US Scripted Series, US Non-Fiction...) which would IMHO live at a clip level* with some level of namespacing/grouping

Additional Common 'Slate' metadata fields to consider (with no regard to methodology specific filtering)

• Setup
• Camera
• Location
• MOS
• Int/Ext
• Day/Night

Other that may or may not belong to a 'slate' metadata group (may be more appropriate under 'Production' or another category or at another level of the data model)

• Unit (often concatenated and included in Shoot Day as in MU_001 or 2U_003)
• Episode (often slated for series production)
• Director (often slated on series production)
• Director of Photography (often slated on series production)

Unlikely to be Slated but likely to be data people want attached

• Camera Metadata (Lens, Exposure, Framing..... relevant to a virtual camera/camera originated clip)
• Sound Metadata (Track/Mic labels, Microphones per track...
• Subject(s) (for non-fiction this may take the plase of 'setup' or the shot name)
• Character(s) (for scripted but rarely included in slate)

*Or even higher as 'shots' are typically made of multiple clips all of which may share a slate as in Camera A captures a clip, Camera B captures a clip, sound recorder captures a clip but the sound clip spans 3 slates, and camera A and B may not... I would like to see the model support this nested composition structure as it represents the real world but it is unlikely that you can enforce it which means you are likely to see similar 'flattening' as you see with ALE which is problematic but is probably not a problem this project should attempt to solve (likely more a best practice or something for movielabs etc...

[BrandonBussinger]

Other references.

BMD Resolve
Pomfort Silverstack
Avid Media Composer ALE spec
EBUCore metadata
ShotGrid
MovieLabs Ontology