DaVinci Resolve Replay Editor

DaVinci Resolve Replay Editor: prepare control and replay output

Prepare control, media, and video output for a replay station with DaVinci Resolve Replay Editor. Ask about options for your event.

Model and use

With the date, location, and intended use, we can review which equipment and combination can be offered. You can inquire before measurements, drawings, or the final schedule are ready.

Replay Editor is a control panel for multicamera editing and replay in DaVinci Resolve. It has USB-C, Bluetooth, and a battery with a power switch; it differs from Speed Editor.

Preparation includes the computer and the media path through video output. We can help define that system around the cameras, content, and planned operation.

Panel, media, and output

Panel: USB-C connects and charges; Bluetooth provides wireless control. Check recognition and response inside Resolve.
Media: One official example combines HyperDeck recorders, Blackmagic Cloud Store shared storage, and Resolve. The manual also describes a smaller system using specific ATEM ISO models; choose the architecture around the planned equipment, versions, and output.
Output: Plan the video interface and switcher inputs. During rehearsal, check the signal received by that switcher and the operator’s view separately.

What to prepare

Tell us what you want to replay, planned cameras, and who will operate production and replay. We can prepare an initial diagram before the final program is available.

Record models, versions, formats, and destinations. Define entry/exit graphics, audio, backup media, and what happens if a replay is not ready.

Basic preparation

Identify the panel and record Resolve and connected hardware versions. Preserve a project copy.
Test the panel over USB-C with a data cable. With Resolve open, the JOG light is a check described in the manual.
Prepare a sample using the planned sources. Check media availability and matching timecode across angles.
Define and test the video path to the switcher and operator monitor with the actual formats.
Mark a point of interest and inspect angles before rehearsal. Agree with production on when replay can go on air.
Test a complete entry, playback, speed change, and return-to-program sequence. Record picture, audio, and results at each destination.

Technical questions and show decisions

Is renting the panel enough to put replays on air?
What if camera angles show different moments?
What if replay appears in Resolve but reaches the switcher incorrectly?
When should we add replay to a show’s screens or stream?
What should be quoted beyond the panel, and what happens if replay is not ready?

Is renting the panel enough to put replays on air?

The panel controls Resolve; on-air replay also requires a computer, available media, and a prepared output path. Verify each segment with the operator.

If recorders or the video interface are still undecided, share sources and the planned switcher. We can organize options before finalizing the system.

What if camera angles show different moments?

Multi Source displays clips with matching timecode together. Compare recordings of the same event and check that those codes refer to the same moment before selecting cameras.

Record which shots match and which do not, including formats and recording method. Avoid changing the whole project based on one clip.

What if replay appears in Resolve but reaches the switcher incorrectly?

Check the operator view and the signal received by the switcher separately. Verify the selected interface, format, cabling, and inputs against the system diagram.

If using Key/Fill, check both signals at the intended switcher inputs. For graphics, rehearse composition entry and exit along the chosen path.

When should we add replay to a show’s screens or stream?

Start with moments worth seeing again: a demonstration, an action detail, or a competition moment. Agree which cameras cover them, who selects the replay, and when production can make room without losing the live action.

For review during the event, we can assess the recording and output path and plan a rehearsal with representative content. For a later recap, compare an editing proposal without immediate on-air output. The panel alone does not define angle count or time to have a replay ready.

What should be quoted beyond the panel, and what happens if replay is not ready?

The proposal can bring together a computer and Resolve, recording, shared storage, output interface, monitoring, configuration, and an operator. It specifies the Resolve edition and license scope, who prepares replay and who calls the take in production, along with audio, graphics, and return to program.

Plan a rehearsal of selection, entry, playback, and exit, and agree how to continue with live action or prepared content if replay is unavailable. For clips or a recap, define selection, format, and delivery timing separately around workload and available media.

Checks by symptom

DaVinci Resolve Replay Editor
Symptom	Check	What it helps distinguish
Panel unresponsive	USB-C, Resolve, and JOG light.	Control connection.
Angles out of sync	Same event and clip timecode.	Media and temporal alignment.
Incorrect output	Interface, format, and switcher inputs.	Path to production.

Limits and precautions

Preserve project and originals before changing settings. Schedule updates and tests outside operation.

Test simultaneous recording load and playback on the planned system; do not derive channel counts or response times from the panel alone.

Check slow motion and graphics with representative content. Agree on a rehearsed way to continue if replay is not ready.

Official documentation

Panel manual: September 2024; Resolve manual: 21.1, September 2026. Examples must be checked against the models and versions used.

Help us improve this guide

Is an explanation missing, did you find an error, or did you solve something differently? Tell us on WhatsApp.

Ask a question Share how I solved it Suggest a correction

WhatsApp opens with an editable draft. Review it and send it if you choose. Do not include passwords, keys or client information. Contributions are reviewed before being added to guides; they are not published automatically.