Import a Cubase Track Archive
Bring an existing Cubase project's track structure into DawForge as a reusable, annotatable template.
A Track Archive is Cubase's native project-tree export — folders, tracks, MIDI routing, embedded expression maps. DawForge reads it whole and stores it as an immutable reference: the structure is frozen, but you can layer annotations on top (per-track library links, tags) and use it to drive Flow.
This video is hosted on YouTube
Loading it lets YouTube set cookies and receive your IP address. Accept external media to watch it here — see our Cookie Policy.
Before you start
- A Cubase project whose track structure is worth re-using — a starting template, a finished cue, anything with the routing you like.
- Cubase Pro — Track Archive export isn't available in Artist or Elements.
Steps
Export the Track Archive from Cubase
- In Cubase, open the project you want to capture.
- Select the tracks (or folders) you want to include. To capture the whole project, select all tracks.
- File → Export → Selected Tracks (or Track Archive, depending on Cubase version).
- Save the resulting
.xmlfile somewhere you can find it.
Upload it to DawForge
- In the DawForge app, go to
/templates/import. - Drop the
.xmlonto the upload area, or pick it with the file picker. - DawForge shows a preview: the folder hierarchy, the number of tracks, and any expression maps it found embedded in the archive.
Track Archives can be large. DawForge handles big uploads fine, but a slow connection may take a moment for large templates. Wait for the preview to appear before clicking save.
Review the preview
The preview tells you exactly what DawForge captured:
- Folder tree — the same hierarchy you'll see in Cubase. Folders, sub-folders, tracks.
- Embedded maps — expression maps attached to tracks in the archive are pulled in verbatim and stored alongside the template. Flow uses these copies directly — even if you later promote one to your library, playback still resolves from the embedded copy.
- Track count — DawForge caps templates at the active plan's per-template track limit (Solo 32 / Chamber 128 / Orchestra 512). If you're over, trim tracks in Cubase and re-export.
Save the template
Click Save template. You'll land on the inspector page (/templates/[id]) where you can:
- Rename the template (top-level name only).
- Add library-instrument links per track (so DawForge knows which knowledge-base patch each track corresponds to).
- Add free-form tags per track.
The track structure itself is frozen — to change folders or routing, re-export from Cubase and re-import. See Annotating tracks for the annotation surface.
Verify it worked
The template appears under /templates with the name you gave it, and opening it shows the same folder structure as your Cubase project. Any expression maps that were embedded in the archive are listed under Embedded maps on the inspector.
If something went wrong
- "Validation failed" on save → the archive references something DawForge can't parse (often a third-party plugin's custom block). The parser only extracts what it actually uses, so most validation failures are misformed XML. Re-export from Cubase.
- Tracks missing in the preview → Track Archive only exports what you selected before File → Export. Re-select and re-export.
- Cap reached → drop or rename a template you don't need, or upgrade.