
REAPER's ordinary solo is Solo in place, which includes the soloed track's sends. A separate Solo Defeat state can keep another track audible even during exclusive solo. Before chasing a routing fault, distinguish an intended reverb return from a track explicitly exempted from solo suppression.
Key Takeaways
- Solo in place and plain solo differ in whether sends are heard.
- Solo Defeat is an independent exemption, not a volume adjustment.
- Restore audition controls before judging or delivering the full mix.
Identify what remains audible
For a hypothetical narration track, a reverb tail from its send may be exactly what a solo-in-place audition should include. An unrelated reference track continuing to play raises a different question.
Identify the audible source and the track actually soloed. Do not diagnose a second path solely because the result sounds louder. The double-route guide concerns audio reaching the output twice; these REAPER controls determine audition membership.
Keep the current mix state available before changing solo controls, particularly when several tracks are selected.
Compare solo with and without sends
Section 5.2 of the REAPER 7.81 manual says a normal solo includes the output of sends, such as a reverb bus. It documents Alt-clicking the Solo button of an already soloed track to toggle between that state and plain solo without sends.
Use the Solo button's context menu to inspect the available choices when modifier gestures are unfamiliar. Confirm which state is active rather than repeatedly clicking until the ambience disappears.
A dry-versus-wet audition does not establish whether the final send balance is correct. The linked guide uses separate application controls.
Check explicit solo exemptions
The manual describes Ctrl+Shift with Solo as toggling Solo Defeat. An exempted track remains audible even when another selection is soloed exclusively. Its context menu provides the corresponding control as well.
Inspect that state on an unexpected reference, cue or other track. Remove an exemption only when it conflicts with the intended audition; an editor may have deliberately kept a guide audible.
The documented !S indicator means a track is suppressed by another solo state. It does not by itself diagnose a missing source file or failed plug-in.
Restore the complete listening context
On a retained copy, compare the intended track alone, its intended sends and the full mix. Verify that temporary exemptions or exclusive-solo choices are no longer shaping the review unintentionally.
No listening test has been executed here. Accept the diagnostic only when the heard sources match the chosen solo contract; approve the finished soundtrack separately.
Related tasks
- Why Does One Premiere Voice Track Become Louder Through a Submix?
- Why Does Reverb Stay Loud When I Lower the Voice Fader in Premiere?
Sources and scope
- REAPER User Guide 7.81: Section5.2: ordinary solo is solo in place including sends; Alt-click an already soloed track toggles plain solo without sends; Ctrl+Shift toggles Solo Defeat allowing tracks even under exclusive solo; context menu also exposes these choices; !S denotes suppressed by another solo.
Documentation-based guidance from the verified official REAPER 7.81 manual, read on October 23, 2026. Proposed diagnostic projects, creative sound examples and external-device checks have not been executed; no recovery, latency, compatibility or listening 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: Mak Cézar / Pexels, Pexels License. This is an illustrative source photograph, not an application screenshot or a generated test result.