Auditing a Session
Check names, routing, gain, plug-ins and backups before anyone else opens the session.
Related
A session that plays cleanly on your machine can open elsewhere with two parts missing and six decibels of extra noise. Find that on delivery day and it is already too late. An audit happens before anyone else opens the file, and it looks for what only shows up somewhere else.
Tracks and channels first
Track names, colours and order are for people. Channels and ports are for the machine. When the two disagree, sound still plays, just in the wrong place. Thirty-two tracks landing on fifteen channels means several parts share a channel, so moving one fader moves another. Name by section first, strings, brass, percussion and synths each in a group, then verify every channel's input, output and bus assignment, and only then unify colours and numbers. Names need not be elegant, but a stranger should find the cello within ten seconds.
Gain you can see
Fader position is not level. Read peak and RMS track by track and look for the outliers, usually caused by recording gain, sample normalisation or leftover automation. Then inspect plug-in order and bypass state on the buses, especially limiters. A limiter left on from a listening test flattens the whole session while every fader looks reasonable. Bypass the bus chain and hear whether the dynamics return.
Missing plug-ins and backups
When a plug-in is missing, do not let the recipient substitute something similar. Freeze or print the track, pin the sound, and write down the maker, version and preset. A backup is not a copy on an external drive either: three copies, two media, one offline, and a restore you have actually performed. A session backup includes audio files, sample library paths, plug-in presets and export settings. Copy only the project file and the next machine greets you with a wall of errors. To test, open on another machine, play, export, and compare section by section with the reference. If you cannot, you have no backup.
One audit sheet
| Item | Symptom | Action |
|---|---|---|
| Track names | Defaults such as Audio 12 | Rename by section, number consistently |
| Channels and ports | Two tracks share one channel | Split the channel or change outputs |
| Gain | One track pinned, bus very low | Fix at the source, not with faders |
| Plug-ins | Missing on open | Freeze or print, log version and preset |
| Backup | A single project file | Add audio, presets, and a restore test |
Where the audit goes too far
An audit can also waste a day. Time spent on colours and icons is better spent on channels and backups, and re-normalising every track destroys the dynamics that were already right. An audit finds structural faults; it cannot fix arrangement. Parts that fight, too much low end, sections without contrast, all belong to arranging and mixing. The point is not a perfect checklist but a session another person can open, play and continue.
Listen in the library
All tracks from midicn-lib — inline badge is the license tier (C1 commercial / C2 non-commercial / C3 study only).
Along the same line
Sources
- AES（Audio Engineering Society）关于工程交换、会话文档与归档的会议文献
- Avid Pro Tools 与 Apple Logic Pro 官方用户指南中关于 I/O 设置、冻结与工程备份的章节
- Bob Katz, Mastering Audio（Focal Press）关于增益结构与电平表的章节