MIDI and the DAW
A DAW turns a MIDI file into tracks, then routes them by port and channel; a track is only a view.
Related
The same file can import with different track counts, and parts can land in the wrong place. Treating one track as one channel breaks on export.
The problem
A track is an organising unit, while a channel is an address inside a message. Confusing them sends drums to a piano, shares one curve across two parts, and shifts the tempo map.
Protocol or message
SMF 0 puts every event in one track; SMF 1 splits by track and shares a timeline. A DAW builds tracks on import, then maps them to ports and channels. Tempo changes live in the tempo map, and continuous controllers need chase so a mid-file start still has the right state. With several ports, each track must remember its destination.
Settings and practice
Check the track and channel table after import. Keep drums on channel 10. Label the output port when several are in use. Choose format 0 or 1 before export, 1 for exchange and 0 for old gear. Never treat a track name as the only channel clue.
What to listen for
A wrong map sends piano to the drums, or makes two parts share one expression curve. A misplaced tempo map moves the whole passage earlier or later.
Common misunderstandings
Track count is not channel count. An instrument track is not a MIDI track. Colours and order in the DAW carry no musical data.
Listen in the library
All tracks from midicn-lib — inline badge is the license tier (C1 commercial / C2 non-commercial / C3 study only).
Sources
- SMF 规范对格式 0 与格式 1 的区分，依 MMA 公开规范核查，未抄文本
- DAW 导入导出时的轨与通道路由规则，依通行软件文档核查，未抄文本
Used for fact-checking only; all prose is original.