HOW TO UPLOAD:

​

• Name your file with the correct naming convention as listed here:​​

  • Naming Conventions​

​

• Upload into the correct folder on BOX. Folder structures should always include the following:

  • [Project Title] - Continuities

  • [Project Title] -STP

  • [Project Title] - ETP

  • [Project Title] - Live Sessions

  • [Project Title] - Logic

  • [Project Title] - Music Searches

  • [Project Title] -Supervision

  • [Project Title] - Themes

  • [Project Title] - Zoom

  • [Project Title] - Videos​

​​

• Once the files are uploaded correctly on BOX, open your CueDB project and select “Cue Details”

  • On the left, select the cue you are uploading to

  • Add a new version using the small “+” button

  • Under “Media” on the right hand side, you will paste links to the video, music, and dialogue reference.

    • These links need to be copied through “Link Settings”

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

 

​

​

​​

​

• Paste this Direct Link onto CueDB under Media

  • Once each link has been copy and pasted, rename to “VIDEO”, “MUSIC”, or “DIA REF”

    • 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!

​

• 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”.

  • Update statuses as each cue version is being worked on and posted:

    • [ ] “In Progress” for when a cue is being worked on

    • [ ] “Composed” when a cue is ready for review

    • [ ] “Revisions” when a cue needs to be revised

• TASKS:

  • 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

• Posting new versions of Cues:

  • Always send as an email to everyone necessary - director, producer, editor, Konsonant team, etc.

  • Version Numbers need to be consistent across logic files, BOX, and CueDB

• Comments

  • 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.”

  • As comments are made:

    • [ ] any new to-do’s should be assigned as tasks on CueDB

    • [ ] any addressed comments should be checked off

​​

​

View the CueDB How To on NOTION