音樂分離模式作為工作流程選擇：延長音樂前比較 2-stem 與 4-stem
Separation Mode as a Pipeline Choice: 2-Stem vs 4-Stem Before You Lengthen
這篇指南主張，短篇幅內容的音樂工作流程應先按編輯需要選定 2-stem 或 4-stem 分離模式，再處理音樂延長。2-stem 適合人聲與伴奏分離；只有明確需要分開處理鼓或低音時，才升級至 4-stem。待音軌分離通過獨奏檢查、確認延續時間點及延續內容後，才進行音樂延長。
If your short-form pipeline treats “split the mix” as a single boolean, you will over-export stems and under-learn from listens. Separation mode is a design choice: it decides which axes you can mute later and how much review tax you pay. This note frames 2-stem vs 4-stem as an API-shaped decision inside WAV AI, then shows where lengthening belongs—after the stem graph is stable.
Background: why mode exists at all
Music source separation is not one algorithm with one output shape. Research stacks differ in how they carve a stereo mixture—Deezer’s Spleeter popularized practical multi-stem demos; Meta’s Demucs line explores hybrid spectrogram/waveform models. Downstream tools expose a smaller product surface: modes like vocal/instrumental vs vocals/drums/bass/other. Your job as a pipeline author is to pick the minimum stem set that unlocks the edit, not the maximum stem set the model can emit.
Mode as an interface contract
Think of the splitter like an endpoint:
| Mode | Rough contract | Good for | Bad for |
|---|---|---|---|
| 2-stem | mixture → {vocals, instrumental} |
Karaoke beds, VO under instrumental, quick mute of lead | Moving kick vs bass independently |
| 4-stem | mixture → {vocals, drums, bass, other} |
Sample flips, DJ bootleg prep, drum replacement | Reviewers who will not solo four faders |
Same upload, different review graphs. If your checklist only says “run stem split,” reviewers will thrash.
A minimal pipeline sketch
brief → choose_mode(2|4) → split → solo_gate → export_needed
→ (optional) rebuild_in_daw
→ extend_if_duration_gap
→ ship_max_2_candidates
choose_mode
- Need only “voice off” or “voice alone”? → 2-stem.
- Need drums without bass mud, or bass without kick bleed? → 4-stem.
- Unsure? Start 2-stem. Escalate only when the solo gate fails for a layered reason.
solo_gate
Reject before export when:
- Hats smear into vocals (or the reverse) enough to hear on phone speakers.
- The instrumental still carries ghost syllables under a new VO.
- Transients on drums feel soft enough that the edit will fight the picture cuts.
The AI Stem Splitter UI’s mute/solo loop is the gate—not a folder dump of every stem “for later.”
Where lengthening sits
Lengthening is a time-axis operation. It assumes identity (key, groove, vocal tone) is already acceptable. Call an AI Music Extender only after:
- The stem graph (or original mix) passed solo_gate.
- You marked a continuation timestamp after the last good bar.
- You know whether the continuation should stay instrumental (common under VO) or carry lyrics.
Extending before mode selection just freezes a bad stem graph into a longer file. Extending after a failed solo_gate teaches the wrong lesson (“AI outro bad”) when the real bug was bleed.
Practical defaults for small teams
- Default mode: 2-stem for talk-over and social beds.
- Escalate to 4-stem: when the brief names a drum or bass problem explicitly.
- Export policy: only stems referenced by the timeline ticket.
- Candidate cap: two continuations per cut; log one-line failure reasons.
What this note is not
It is not a bake-off of model architectures, and it does not cite product marketing percentages. Use your own listens and your own picture lengths as ground truth. Mode first, length second—treat both as typed steps in the pipeline, not as interchangeable “AI music” buttons.
來源：DEV Community · dev.to