HOW TO UPLOAD:

  1. Name your file with the correct naming convention as listed here:

Naming Conventions

  1. Upload into the correct folder on BOX. Folder structures should always include the following:
    1. [Project Title] - Continuities
    2. [Project Title] -STP
    3. [Project Title] - ETP
    4. [Project Title] - Live Sessions
    5. [Project Title] - Logic
    6. [Project Title] - Music Searches
    7. [Project Title] -Supervision
    8. [Project Title] - Themes
    9. [Project Title] - Zoom
    10. [Project Title] - Videos
  2. Once the files are uploaded correctly on BOX, open your CueDB project and select “Cue Details”
    1. On the left, select the cue you are uploading to
    2. Add a new version using the small “+” button
    3. Under “Media” on the right hand side, you will paste links to the video, music, and dialogue reference.

      1. These links need to be copied through “Link Settings”

        1. click the link icon as seen below, then “Link Settings”, then copy the Direct Link

          Screenshot 2024-04-10 at 11.58.10 AM.png

      2. Paste this Direct Link onto CueDB under Media

    4. Once each link has been copy and pasted, rename to “VIDEO”, “MUSIC”, or “DIA REF”
      1. ALWAYS include a DIA REF to ensure that the filmmaker can correctly import (and double check) our files into their projects!

CHECKLIST

Consistency here is KEY. Always make sure that everything stays updated arorss BOX, Notion, and CueDB, so that we save valuable time!

  1. STATUSES: Listed as “To Write”, “KON”, “In Progress”, “Rewrite”, “Small Revisions”, “Revisions”, “Big Revisions”, ”Composed”, “Approved”, “Orchestrate”, “Record”, “Mix”, “Stems”, “Completed”, “On Hold”, “Omit”, “Song”, and “License”.
    1. Update statuses as each cue version is being worked on and posted:
  2. TASKS:
    1. Add a “tasks” column with assignable tasks and checkboxes
      • after spotting, extract tasks from notes and add here
      • keep these as updated as possible throughout the course of each project
  3. Posting new versions of Cues:
    1. Always send as an email to everyone necessary - director, producer, editor, Konsonant team, etc.
    2. Version Numbers need to be consistent across logic files, BOX, and CueDB
  4. Comments
    1. When posting a cue, include a comment that
      • [ ] reiterates what was said in the spotting session
      • [ ] makes it clear what the music is trying to accomplish
        • [ ] For example: “We addressed the concerns about this temp in the spotting session, especially in regards to anything distracting, but made sure to keep the same feel by using the same tempo and a similar instrumentation. We also fixed the lack of harmony mentioned in the spotting session, while ensuring the music stayed simple and out of the way for the backstory to shine.”
    2. As comments are made:
      • [ ] any new to-do’s should be assigned as tasks on CueDB
      • [ ] any addressed comments should be checked off