Preparing dailies in Silverstack

This is for the DIT or data manager delivering dailies to an Oropod project from Pomfort Silverstack. Oropod reads the clip report you already produce, so most of the work is filling in two custom fields consistently and exporting once per shooting day.

Until metadata arrives, Oropod still lists and plays the files, but browsing by day, scene, shot or tag finds nothing, so it is worth getting this right before the first shooting day rather than after.

Filling in the slate and custom fields

Scene, shot, take and camera come from Silverstack’s slate info, and drive most of Oropod’s navigation
Custom 1 carries the shooting day and date, written as D12 2026-08-13. Both parts are needed: without the day number Oropod ignores the date and falls back to the camera clock, which is often wrong.
Custom 3 carries tags, separated by commas. They are free-form, so agree a short list up front, for example vfx, plate, 2nd unit or pickup, and readers can then filter by them.
Custom 2 is not read
A clip tagged ignore is skipped, so tests and false starts never reach the day, scene and shot lists

Flagging circled takes

Flag the circled take of each setup in Silverstack, or tag it circled in Custom 3
Oropod builds the Circled takes in scene order playlist from this, giving an automatic rough cut of the whole project, and uses it to pick the poster frames behind each day, scene and shot
The circles usually start with the script supervisor, so agree early on how they reach Silverstack each day

Exporting the clip report

Export as an XML clip report. Oropod reads Silverstack’s XML clip report, not its PDF or CSV reports.
One report per shooting day is a good default, keeping each file small and easy to replace later
Give it a predictable name, such as D012.xml, so a corrected export can replace it exactly

Uploading the report

Upload the report to the project’s storage together with the clips. A Frame.io project, an Oropod Storage workspace and a network disk all work the same way.
It can go in any folder, and does not have to sit beside the clips it describes
Entries are matched to clips by clip name, from the start of the file name, so dailies that keep the camera’s clip name (A024C002_161101_R11M) still match with a suffix added, while renamed files do not
Oropod imports the report on the next sync

Correcting a report

Re-export and replace the file, keeping the same name and the same folder, and Oropod discards everything the old report said
Uploading the correction under a new name instead leaves both reports in place, and Oropod merges them rather than choosing between them

Checking it worked

Open the project in Oropod. Days, Scenes and Shots stop being greyed out once the first report has been imported.
Spot-check a clip’s metadata view: the lens, T-stop, shutter and EI shown there all came through the report, which makes it a quick daily check that camera metadata survived the transcode