
REAPER's Move tracks to new subproject changes the project boundary. The 7.81 manual explicitly says that sends and receives between selected tracks and other tracks in the parent are removed. A track can therefore move successfully while losing the route that previously fed an external reverb or received a control signal.
Key Takeaways
- Moving tracks is not the same as preserving every route to unselected tracks.
- Include an enclosing folder in the selection when that folder belongs in the subproject.
- The parent receives the subproject's rendered output, not the original collection of track connections.
Draw the boundary before extracting tracks
In a saved copy of the film mix, list the tracks to move and the tracks that will remain. Inspect sends and receives crossing that divide. A narration track might feed a shared reverb that also serves another speaker; moving only the narration does not bring the shared return with it.
Distinguish a route contained within the selection from one leading outside it. The pre/post-fader send guide explains a separate balance relationship. Adjusting the send's pre/post position cannot restore a connection that the project extraction removes.
Use the track operation for the intended selection
The official REAPER guide documents selecting tracks in the Track Control Panel, including the folder when the tracks are enclosed in one, then choosing Track > Move tracks to new subproject.
The moved tracks are saved in the new project. Their output appears in the parent as one rendered item on a single track. Preserve the original project before this structural change so you can compare its original routing rather than reconstructing it from memory.
Decide what each lost dependency should become
For every boundary-crossing connection, choose an explicit new arrangement. Some processing may belong inside the subproject; another shared effect may appropriately stay in the parent. Do not move a common return merely because one source needs it without considering its other users.
The manual's removal rule does not promise that every original topology can be rebuilt unchanged around the rendered parent item. An exported mix has different control granularity from the source tracks. Keep the earlier routing map as the reference for that decision.
Compare the sound at both project levels
Audition an interval where the removed connection mattered: a reverberant phrase, a control-triggered effect or a shared bus transition. Compare the preserved original with the new parent arrangement at a consistent monitoring level.
Check the subproject's sound and the parent's resulting sound separately. Like other shared nested sources, the subproject can affect its parent, but source reuse does not establish routing equivalence. Acceptance is an accounted-for signal path and an approved result, not merely the presence of a new project file.
Related tasks
- Why Does Reverb Stay Loud When I Lower the Voice Fader in Premiere?
- Editing One Nested Intro Changes Every Copy: Is the Source Sequence Shared?
Sources and scope
- REAPER User Guide 7.81: Section12.24: Track > Move tracks to new subproject moves and saves selected tracks/folders, renders their output to one parent item on one track, removes sends/receives between selected tracks and other parent tracks. Include folder in selection if enclosed.
Based on the official REAPER 7.81 user guide downloaded and read on October 23, 2026. Proposed project and rendering checks have not been executed; no completed software test or measured result is claimed.
Prepared by Imagild Editorial, the company editorial team responsible for these guides. AI assisted research and drafting. This is documentation-based guidance with proposed examples, not a claim of hands-on testing or an independent product review. Report a correction.
Cover: Rumeyda Tutak / Pexels, Pexels License. This is an illustrative source photograph, not an application screenshot or a generated test result.