Extract Dynamic Metadata from DCS Box CSV Files

This article covers features which are only available in Silverstack XT and Silverstack Lab.

DCS boxes capture dynamic metadata from camera lenses and can write them to CSV files. Silverstack XT and Lab (version 8.6.5 and newer) allow you to match these files with clips in the library and parse their information to make it available for further use in the application.

This feature builds upon the basic concepts of dynamic metadata in Silverstack XT and Lab; however, the separate CSV file is parsed instead of directly extracting the information from the clip files. If you are still getting familiar with the basic concepts, please read the article Dynamic Metadata first.

How To Match and Parse CSV Files From DCS Boxes

  1. Ingest Clips in Silverstack
  2. Create a folder named DCSBOX on your desktop
  3. Put the CSVs from your DCS Box into this folder (~/Desktop/DCSBOX)
    • For a correct matching of clips in the Silverstack library with the CSV files, the CSV’s filename must match the first part of the clip name
  4. Select clips in Silverstack, click on “Extract Dynamic Metadata” or “Extract for Selected Clips”


  • If Silverstack finds a matching CSV in the folder on the desktop, the CSV file is parsed (instead of the original clip file) to extract dynamic metadata
  • The metadata is sanitized (see below) and then attached to the clip in the library. After that, the data is available for
    • Checking while playing back footage in the left sidebar
    • Burn-ins in transcodes and still image exports
    • Exporting as CSV
  • If the CSV holds lens or lens serial information in the header, the data is extracted and overwrites the respective information in Silverstack’s (static) metadata fields
  • Additionally, a log file is put into the folder on the desktop that informs about the matching and sanitization process


If missing or incompatible information is found while parsing the CSV files, this is how it is handled:

  • Clip begins before CSV (missing information for first couple of frames) → Substitute missing metadata with first available Information from CSV
  • CSV ends before clip ends (missing information for last couple of frames) → Substitute missing metadata with last available information from CSV
  • CSV begins after clip ends (CSV does not hold information for matched clip / timecode does not match)  → Skip extraction
  • Missing frames in CSV (CSV does not hold information for a specific frame) → Substitute missing metadata with next available Information from CSV
  • Frame rate in CSV header does not match with clip’s fps → Skip extraction
A log file that is automatically created during the process documents these cases.