
REAPER distinguishes mouse edits to lead items from actions in Media/Razor edit groups. The 7.81 guide says mouse edits affect follow items in the group whether selected or not, whereas actions affect only selected items. A valid group therefore does not guarantee that an action reaches the same items as a mouse edit.
Key Takeaways
- Inspect the operation as well as group membership.
- Lead/follow roles and item selection are separate controls.
- Matching item start and end times can restrict the eligible group items.
Identify how the edit was initiated
Suppose a hypothetical dialogue edit has a close microphone and a room microphone grouped, while music remains outside the group. Moving a lead item with the mouse and invoking an editing action are not interchangeable ways of specifying the recipients.
The REAPER 7.81 guide, section 7.5.1, states this scope difference explicitly. Before treating the missing companion edit as broken grouping, record whether you used a mouse operation or an action, which item was the lead, and which items were selected.
Inspect the group and selection settings
Open View > Track Grouping Matrix and check the Media/Razor edits column for the relevant group. Distinguish its lead/follow assignments from grouped volume or pan controls. A shared fader relationship does not by itself establish this media-edit relationship.
The grouping toolbar must have item and track media/razor edit grouping enabled. Its Selecting one item selects group option can change the selection created by a click. Also inspect Track media/razor edit grouping affects only items that start and end at the same time, documented as enabled by default. Different item boundaries may therefore matter before the operation is even attempted.
Do not turn on automatic grouping of all tracks merely to force a missing item to participate. That would broaden the editing scope beyond the intended microphones.
Compare the two operations on a copy
Prepare a reversible project revision with two eligible microphone items and clearly identified lead/follow roles. Record their positions and selection. Try a small mouse edit from the lead item, inspect both results, then undo. Before trying the corresponding action, explicitly inspect the selected-item set.
This is a proposed diagnostic comparison, not a tested claim about every action or mouse modifier. The guide's general rule does not document all specialized action behavior. If an operation remains unclear, consult that action's definition rather than assuming an exception.
Preserve the intended editing relationship
After resolving selection, verify the dialogue remains aligned and unrelated music is unchanged. This task concerns operation-dependent recipients; Kdenlive grouped cutting and Audacity Sync-Lock boundaries describe different grouping contracts. Neither supplies REAPER's mouse-versus-action rule. Keep that distinction in the edit note so the next operator does not repeat the same scope assumption.
Related tasks
- How to Split Grouped Video and Separate Audio at the Same Point in Kdenlive
- Why Does an Unselected Audacity Track Move When I Edit Another?
Sources and scope
- REAPER User Guide 7.81, section 7.5.1: Media/Razor grouping enablement, selecting-one-selects-group, matching-boundary restriction, lead/follow matrix roles, and mouse edits versus selected-item actions. Verified local text lines 7046-7133.
Based on REAPER User Guide 7.81, section 7.5.1, read on October 23, 2026. The comparison is proposed guidance, not a performed test; specialized action and mouse-modifier behavior must be checked separately.
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: Mariya Eskina / Pexels, Pexels License. This is an illustrative source photograph, not an application screenshot or a generated test result.