Importing Tracks

The Library imports from the local filesystem. You can choose an external folder, drop supported items into the workspace inboxes, or run Manual Sync.

Pipeline

1. Items are classified as bounces, stems, or projects.
2. The inbox router places them in the matching flat local inbox.
3. Filename normalisation and matching group likely versions of the same song.
4. High-confidence items are organised under tracks/<song>/... and catalog metadata is synced.
5. Files owns correction for unassigned or wrongly assigned items.

External imports copy by default. Project organisation uses copy-plus-symlink where required so an open DAW project keeps its original path.

Duplicate identity

Exact duplicates require a same-category name-and-size candidate followed by matching SHA-256 content. Created and modified dates are descriptive only. Folder projects use a deterministic recursive manifest digest.

An exact duplicate is skipped. A different-content collision is preserved under a collision-safe version path. Hash or read failure preserves both items and continues safely.

Dropbox boundary

Dropbox supports collaboration, links, and delivery. It does not own local scanning, grouping, or the tracks/ hierarchy.