Skip to content
SoundBuddy

SoundBuddy editorial

REAPER render queue: check which edit you actually queued

Published

An open folder and pencil sit apart from an earlier closed folder.
AI-generated editorial illustration. Separating working material from a retained earlier state. Conceptual props, not app UI or a tested result.

You correct a phrase in a REAPER project, then find the older phrase in a queued render. Before editing the source again, compare when the queue entry was created with when the correction was made. A saved current project and a previously queued render can represent different states.

This is a different question from whether a render completed. The file may exist and play while still containing an edit you intended to replace.

Know what adding to the queue preserves

REAPER’s rendering overview describes saving render instructions for later batch processing. Geoffrey Francis’s 7.85 User Guide, section 21.9 on printed page 419, gives the important qualification: a queued file is saved at the point it is added. To include subsequent changes, the guide instructs you to remove the entry and add it again.

Match this guidance to the version you use. Do not treat the queue as a live checklist that necessarily follows every later change to an open project. Record the project revision and the expected edit when you queue a delivery.

Compare the project, queue and output separately

An illustrative sequence makes the mismatch easier to locate:

EventState to record
Add an interview project to the queueRevision A and its render choices
Correct a phrase in the project afterwardsRevision B and the corrected passage
Inspect the existing queue entryWhether it was replaced after that correction
Open the completed listening fileWhether the corrected passage is actually present

These labels describe a proposed comparison, not a project rendered for this article. Saving revision B does not, by itself, prove that an earlier queue entry was replaced. A filename containing “final” does not establish that either.

Use the blank queued-revision record to connect the project state, queue action and actual output. Include a short identifying passage rather than private interview content in a shared note.

A preserved sheet in a transparent sleeve beside a separate working sheet.
AI-generated editorial illustration. A retained-copy metaphor for revision comparison. Conceptual props, not app UI or a tested result.

Replace the intended entry without losing the source

Keep the current project and any earlier output you need for comparison. In the queue, identify the specific entry you intend to replace. Follow the matching guide’s remove-and-add procedure after confirming the desired project and render settings.

Review the destination and output names too. Use a separately identified review destination when comparing an old and new attempt, so the result you are investigating is not silently overwritten. Inspect which queue entries will run before selecting a batch-wide action; unrelated projects may be waiting there.

The guide describes selecting a subset of queued entries or rendering the whole queue. Use the option appropriate to the files you actually intend to produce. Completion of an unrelated queued project does not settle whether your corrected interview was included.

Check the change that motivated the new render

Open the resulting listening file independently and inspect the corrected passage first. Then check the required beginning, ending and included sources. Record the exact output filename and whether the expected edit is present.

If it is still wrong, retain the mismatch and inspect the identified project revision, queue replacement and render choices separately. Avoid repeatedly changing the audio to compensate for an output that may have come from an earlier queued state.

For a region-specific delivery, the region render matrix guide addresses which track-and-region combinations should produce files. For an editable session, use the project-media handoff guide. Neither replaces checking the revision in the actual listening file.

This guide is based on the cited documentation. No REAPER project, queue entry, recording or render was operated for it, and the accompanying record contains no observed results.

The cited reference passages were reviewed on 13 November 2026.