Studio 21.1.1
Module 16 · Workflow
LESSON 16.01 · 40 MIN PRACTICE

Collaboration, project libraries, and media paths

A shared project is not the same as shared media. Collaborators need compatible project access, consistent versions, and a reliable way to reach the source files.

What you’ll be able to do

Plan a collaboration that accounts for both project state and its dependencies.

ACTUAL RESOLVE INTERFACEView full size ↗
Project Manager: projects in the local library
Project Manager: projects in the local library Reference example from the DaVinci Resolve 21.1 manual, page 15. Software screenshot © Blackmagic Design. The demonstration media and selected settings may differ from your project.

Work through it

  1. Define responsibilities for editor, colorist, and sound work. Agree on Resolve versions and project naming before exchanging active work.
  2. Compare a local project library with a shared Project Server or Blackmagic Cloud workflow. Understand where the project lives and separately where the media lives.
  3. Test a short shared project with two workstations if available. Verify media paths, proxies, audio, fonts, and plugins, then observe locking and update behavior.
  4. Set a revision and communication convention. Before a major change, create a recoverable version and record what another collaborator must refresh or review.

A mistake to avoid

Cloud project access does not guarantee the other person has the media, fonts, effects, or licenses needed to reproduce your timeline.

Your turn

Create a handoff checklist for a second workstation. If working alone, simulate the handoff by opening a copied project with a separate media folder.

QUICK KNOWLEDGE CHECK

What must be shared or made accessible in addition to project data?

Your notes

Write down what worked, what surprised you, and what to try next. Saved on this device.

Original practical lesson · Open the in-house resource shelf for practice files and definitions. Completion records your self-assessment, not certification.