Stem Naming
Three naming schemes have to map onto each other
Related
Three naming schemes in one zip
A client returns a zip containing "vocal_final2", "vocal_final2 edit" and "BASS final". The session cannot relink automatically, so the mixer auditions each file. Naming is not a matter of taste; it is what lets a DAW, a platform and a client identify the same file without asking.
Three schemes, three jobs
| Context | Field order | Example | Avoid |
|---|---|---|---|
| Inside the DAW | index_role_source_version | 03_bass_di_v04 | "bass2" alone |
| Platform upload | project_title_version_type | spring_ad_15s_v03_master | Chinese characters, spaces, brackets |
| Client delivery | project_title_version_stem_tempo_date | spring_ad_15s_v03_stems_120bpm_20261031 | Mixed case, unpadded versions |
The three do not have to look identical, but their fields must correspond. The DAW sorts by index, the platform by title and version, the client by project. Put the mapping in the delivery note; that is more reliable than making everyone memorise one scheme.
One rule that survives all three
Use lowercase ASCII and underscores, never spaces. Pad versions to two digits. Keep tempo and key in a fixed position. Between versions of one project, change only the version number, never the field order. Keep stem names identical to DAW track names. Platforms limit length and characters, so test one upload before sending a batch.
Build a map before renaming
Renaming breaks session references, plug-in automation and client templates. Export a CSV mapping old names to new ones, freeze the version first, and attach the map to the delivery note. When a client has a house style, follow it and keep a stable internal name aligned through the map.
What a name cannot fix
If the stems themselves are swapped, tidy names will not help; someone has to listen. If a client uses "instrumental" and "backing track" interchangeably, define both in writing. If a platform rejects certain characters, test the rule early. Naming makes files findable, not understandable; the delivery note does the second job.
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
- Netflix Sound Mix Specifications 与 Dolby 交付规范中关于分轨与工程命名的惯例。
- 数字音频文件命名与元数据建议,由行业组织公开。
- 平台上传的文件名限制,来自官方帮助文档。