
Check Only sent to parent when a REAPER stem omits internal track channels. With that render option enabled, the output includes only channels routed to the parent. A track's internal channel capacity and its parent-send range can be different by design.
Key Takeaways
- Internal track channels are not automatically all delivery channels.
- Parent routing and render channel selection must agree.
- Do not export sidechain or control channels as program audio accidentally.
Inventory channels and their purpose
Open the track routing and identify its internal channel count, parent-send source range and destination. The parent may be a folder track rather than the master.
Determine what each channel actually contains. Some channels may carry the audible program, while others serve a detector or parallel processing path. A missing internal channel is not necessarily lost narration.
Write the required output layout before changing settings. A multichannel delivery must preserve the intended signals and order, not merely report a large channel count.
Compare routing with the render option
The REAPER 7.81 render options define Only sent to parent. The manual's multichannel routing discussion explains why parent sends can cover fewer channels than the track contains.
In the Render dialog, inspect this option alongside the selected source and output channel configuration. If the intended deliverable excludes control channels, limiting the render may be correct. If the brief requires channels outside that range, establish a deliberate compatible routing and rendering arrangement.
Avoid blindly setting every range to All. That can expose processing or detector signals that were never meant for the recipient.
Render a recognizable channel test
Choose an interval in which the required signals can be identified independently. Export to a new file and inspect both channel count and audible content.
Solo the output channels using a suitable editor or inspector. A six-channel container with duplicated or silent content does not establish a valid six-channel mix.
For a receiving editor, separate file content from clip channel mapping and track format. A correct stem can still be imported or monitored incorrectly.
Document the delivered channel map
Label the intended channels and state whether the file represents a mixed program, separate production signals or another agreed arrangement. Keep the original routing configuration in the editable project.
When stems need to reconstruct the film mix, check common start times and reconstruction as well as channel identity.
If the desired signal is absent even before rendering, investigate the upstream source and routing. Changing the export checkbox cannot restore a recording that never reached the track. Approve the handoff only after the rendered channel map matches the receiving specification.
Related tasks
- Should I Change Fairlight Clip Attributes or the Audio Track Format?
- Why Do Delivered Dialogue, Music, and Effects Stems No Longer Line Up?
Sources and scope
- REAPER User Guide 7.81 — page 415: render parent send channels multichannel
Based on the official REAPER 7.81 User Guide, retrieved October 23, 2026, with the relevant sections checked against the complete manual. The workflow and hypothetical review situations are documentation-based; no REAPER processing test was performed.
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: Pignatta / Pixabay, Pixabay Content License. This is an illustrative source photograph, not an application screenshot or a generated test result.