Volume 3 — Session Management

PART III — SESSION MANAGEMENT

Chapter 8 — Creating and Organizing Projects

The Session As The Studio

Everything inside Qtractor begins with a session.

A session is not merely a project file.

A session is the complete description of:

• timeline structure
• track layout
• clip placement
• routing
• plugins
• automation
• tempo information
• markers

A useful mental model is to regard a session as a virtual studio.

Opening a session reconstructs the studio exactly as it existed when saved.

Creating A New Session

Creating a session involves more than naming a file.

Several decisions made at creation time affect the entire production.

Typical information includes:

• session name
• session directory
• sample rate
• tempo
• time signature

Although some values can later be changed, establishing them correctly at the beginning reduces complications.

Session Naming

Good naming practices become increasingly important as project count grows.

Poor:

song
song2
song-final
song-final-final

Better:

2026-06-16_MySong
2026-06-16_MySong_v01

Best:

Artist_TrackName_20260616

Consistent naming simplifies:

• backups
• collaboration
• archival retrieval

Session Directories

Every session should have its own dedicated directory.

Typical structure:

MySong/

 ├── MySong.qtr
 ├── audio/
 ├── midi/
 ├── exports/
 ├── backups/
 └── notes/

A dedicated directory prevents:

• missing files
• accidental overwrites
• organizational chaos

Why Separate Sessions Matter

Mixing multiple projects inside one directory often causes:

• duplicate filenames
• lost recordings
• broken references

One project equals one directory.

This principle remains useful regardless of project size.

Planning Before Recording

Many editing problems originate before recording begins.

Before creating tracks, establish:

Song Structure

Example:

Intro
Verse
Chorus
Verse
Chorus
Solo
Outro

Expected Track Count

Example:

Lead Vocal
Backing Vocal
Guitar L
Guitar R
Bass
Kick
Snare
OH L
OH R

Routing Requirements

Example:

Drum Bus
Vocal Bus
FX Bus
Master Bus

Instrument Requirements

Example:

Piano
Strings
Synth Pad

Planning reduces future reorganization.

Session Templates

Templates eliminate repetitive setup.

Instead of rebuilding the same studio repeatedly, a prepared configuration becomes the starting point.

Example Podcast Template

Host
Guest
Music
FX

Master

Example Singer-Songwriter Template

Vocal
Acoustic Guitar
Room Mic

Reverb Bus
Master

Example MIDI Production Template

Drums
Bass
Piano
Strings
Brass

Master

Templates improve:

• consistency
• efficiency
• organization

Track Naming Conventions

Track names should immediately communicate purpose.

Poor:

Audio 1
Audio 2
Audio 3

Good:

Lead Vocal
Backing Vocal
Ac Guitar
Bass DI

The larger the project becomes, the more valuable clear naming becomes.

Color Organization

Color assignment helps identify track categories.

Example:

Red      Vocals
Blue     Drums
Green    Guitars
Purple   Keyboards
Yellow   FX

The objective is rapid visual identification.

Organizing Large Sessions

As track count increases:

10 tracks
20 tracks
50 tracks
100+ tracks

organization becomes increasingly important.

Common strategies include grouping by:

Instrument Family

Drums
Bass
Guitars
Keys
Vocals

Signal Flow

Sources
Groups
FX
Masters

Recording Order

Rhythm
Harmony
Lead
Effects

Any consistent strategy is preferable to none.

Chapter 9 — Session Files And Data Structures

Understanding The .qtr File

The primary Qtractor session file uses:

.qtr

extension.

Internally it is XML.

The file contains instructions rather than media.

What The .qtr File Stores

Examples:

Tracks
Plugins
Routing
Markers
Automation
Clip Locations

What The .qtr File Does Not Store

Examples:

Audio recordings
Large WAV files
FLAC files

The media remains separate.

Why This Matters

A session file may be:

300 KB

while referenced audio consumes:

3 GB

Copying only the .qtr file does not copy the project.

Understanding References

Suppose:

vocals.wav

exists.

The session records:

Use vocals.wav

Start:
00:01:05

End:
00:01:12

The session references the file.

It does not contain the file.

Relative Paths

Relative paths are generally preferable.

Example:

audio/vocals.wav

instead of:

/home/user/projects/song/audio/vocals.wav

Relative paths improve portability.

Why Absolute Paths Cause Problems

Moving the project directory may produce:

Missing File

errors.

The session still expects the old location.

Understanding Session Saves

Saving stores:

• current arrangement
• current routing
• current plugins
• current automation

Saving does not necessarily rewrite media files.

Save Versus Save As

Save

Updates current session.

Save As

Creates new session version.

Useful for:

Song_v01
Song_v02
Song_v03

Version-Based Workflow

Professional projects often use incremental versions.

Example:

MySong_v01.qtr
MySong_v02.qtr
MySong_v03.qtr

Advantages:

• experimentation
• rollback
• protection against mistakes

Milestone Saving

A useful habit is saving before major operations.

Examples:

Before Editing

v05

Before Mixing

v10

Before Mastering

v20

This creates recovery points.

The .qtz Archive Format

Qtractor supports:

.qtz

archives.

A qtz archive packages session information together.

Purpose Of QTZ

Designed for:

• portability
• backup
• transfer

The archive acts as a bundled project package.

When To Use QTZ

Useful before:

• moving projects
• sharing projects
• long-term storage

When Not To Rely Solely On QTZ

Working projects generally benefit from ordinary directory structures.

The archive serves best as:

• snapshot
• backup
• delivery package

Chapter 10 — Asset Management

What Is An Asset?

Assets include:

• recordings
• imported audio
• MIDI files
• stems
• loops

Everything used by the session becomes an asset.

The Files Panel

The Files panel functions as the project's asset inventory.

Many users focus exclusively on the timeline and ignore the Files panel.

Doing so often creates organizational problems later.

Audio Tab

Displays available audio resources.

Examples:

vocals.wav
guitar.wav
drums.wav

MIDI Tab

Displays MIDI resources.

Examples:

strings.mid
piano.mid
drums.mid

Importing Assets

Assets may be imported from external sources.

Examples:

Loop libraries
Field recordings
Sample packs
External sessions

After import, they become available for placement on tracks.

Asset Reuse

One asset may appear many times.

Example:

Chorus.wav

used at:

01:00
02:00
03:00

No duplication occurs.

Only references are added.

Benefits Of Reuse

Advantages:

• reduced disk usage
• simplified editing
• efficient arrangement building

Orphaned Assets

An orphaned asset exists within the project but is no longer used.

Example:

old_vocal_take.wav

remaining after editing.

Why Orphaned Assets Matter

Large projects accumulate:

• unused takes
• abandoned recordings
• obsolete stems

Storage consumption gradually increases.

Session Cleanup

Periodic cleanup improves:

• organization
• portability
• backup efficiency

Common cleanup activities:

Remove Unused Takes

Remove Test Recordings

Remove Temporary Exports

Consolidate Naming

Verify Asset Locations

Naming Assets

Poor:

audio0001.wav
audio0002.wav

Better:

LeadVocal_Take01.wav
LeadVocal_Take02.wav

Clear naming reduces confusion during editing and recovery.

Chapter 11 — Backup, Versioning & Archival

Why Backup Matters

Projects often represent:

• days
• weeks
• months

of work.

A backup strategy should exist before significant production begins.

Three Types Of Protection

A complete protection strategy includes:

Session Protection

Protects arrangement data.

Asset Protection

Protects recordings.

Archive Protection

Protects completed projects.

Versioning

Versioning provides insurance against mistakes.

Rather than overwriting endlessly:

song.qtr

maintain:

song_v01.qtr
song_v02.qtr
song_v03.qtr

Major Revision Strategy

Increment versions when:

Editing Completed

Mixing Started

Routing Redesigned

New Recordings Added

Plugins Replaced

This creates meaningful checkpoints.

Backup Directory Structure

Example:

Project

 ├── Current
 ├── Backups
 ├── Exports
 └── Archives

Keeping backups separate improves safety.

Portable Project Verification

Before moving a project:

Verify:

Audio Present

MIDI Present

Plugins Available

Missing Files Resolved

Exports Completed

Session Loads Correctly

Long-Term Archival

The goal of archival is future accessibility.

Future systems may not possess:

• identical plugins
• identical operating systems
• identical instruments

For this reason archival should include:

Session Files

Raw Audio

MIDI Files

Final Mixes

Stem Exports

Documentation

Recommended Archive Package

Project/

 ├── Session
 ├── Audio
 ├── MIDI
 ├── Stems
 ├── Final Mix
 └── Notes

This structure maximizes the probability of successful future recovery.

Session Management Checklist

Before serious production begins:

✓ Dedicated project directory

✓ Consistent naming

✓ Template selected

✓ Backup strategy established

✓ Versioning strategy established

✓ Asset organization planned

✓ Marker strategy planned

✓ Routing structure planned

A well-managed session reduces editing mistakes, accelerates production, simplifies collaboration, and significantly improves the long-term survivability of a project.

Volume 3 Complete

Next Volume: Audio Recording
(Track creation, input assignment, mono/stereo recording, monitoring, takes, overdubbing, punch recording, loop recording, gain staging, clipping prevention, comping workflows, and recording best practices.)