Skip to main content
The current version uses media hash lists to quickly scan your folders for offloaded media. This usually isn’t an issue if your footage was offloaded using software that creates MHLs.Future versions will remove the dependency of MHL files.
MHL and ASC‑MHL are checksum manifests generated by offload tools. They describe the media files in a folder and record where backups live, including hashes for integrity checks.
Offload tools: https://mediahashlist.org/tools/

​
Importing in the app

Import clips in Add Shooting Day(ta)

Import camera, sound, and proxy files in Add Shooting Day(ta)

​
Prerequisites

  • An MHL or ASC‑MHL file in the folder you are importing.
  • (Optional) camera‑specific sidecar files for additional metadata.

​
Camera‑specific metadata

For some cameras, additional sidecar files enable richer metadata extraction.
CameraSidecar file
ARRI ALEXAALE file
Sony VENICESony XML file
When these files are present, Daytalog will attempt to parse:
  • TC start
  • TC end
  • Duration
  • Camera model
  • Reel
  • FPS
  • Sensor FPS
  • Shutter
  • Lens
  • Resolution
  • Codec
  • Gamma
  • Exposure index
  • White balance
  • Tint
  • LUT

​
Sound clips

As with camera files, this requires an MHL/ASC‑MHL file for clip name, size, and copies. The app will try to parse timecode from the sound files. Sound clips with overlapping timecode are automatically matched to camera clips.

​
Proxy clips

Proxy clips do not require sidecar files. The app will try to extract metadata from proxy files that have a matching camera file. The app will try to parse the following metadata from the proxy files:
  • Size
  • Format
  • Codec
  • Resolution
If your proxy clips have a different name than the camera clips, you can manually set the number of proxy files and their total size.

​
Extending with Custom Schemas

The default schema is designed to be minimal, only holding essential data. You can extend clips with custom schemas

Custom Schemas

Extend clips with custom schemas