Multicamera review
Direct Play puts recordings from multiple cameras on one timeline. Find the footage you need, review synchronized angles, and export the selected range as separate files.

Workflow
Search the archive, compare cameras, and add the cut to the export queue in one session.
Search by name, date, time, or starting timecode. Load only the files you need to review.
ARCHIVELink cameras for shared playback. Line them up by timecode when the recordings support it, then jog frame by frame to check the action.
MULTIVIEWSet IN and OUT for one camera or add a linked cut. A linked cut creates a separate file for each included camera.
EXPORT LISTProduct views
Select a view to see the desktop multiview, archive, or web dashboard.

Linked cameras follow the same master position.

Search by name, date, time, or starting timecode.

The dashboard controls the current Direct Play session.
Timecode alignment
When linked recordings have overlapping time-of-day timecode, Direct Play places each camera at its recorded start time on the master timeline. A linked IN/OUT range then covers the same moment in each exported file.

Optional AI search
With a configured AI search service, enter a description such as "basketball player near the basket." Direct Play returns candidate moments in the archive or adds marks to loaded recordings. Review each match before setting IN and OUT.
Desktop and browser
Direct Play reads and exports media on the Windows workstation. The web dashboard connects to the running app and shares its sources, playback state, and export queue. Teams can also build their own controls with the REST API.
Load files, review footage, add marks, and export cuts.
Search the archive, control playback, and run exports.
List sources, control playback, search the archive, and manage jobs.
Use cases
Find a play, compare camera angles, and pull the relevant clips.
Review event recordings and prepare selected clips after the show.
Export the same time range from each camera for editing.
Practical details
Direct Play uses files the Windows workstation can access. The app must be running for browser control.
No. It creates a separate output file for each linked source that has a valid range.
No. You can play several cameras without timecode. To line them up by clock time, every linked file needs time-of-day timecode and overlapping recording times.
No. Name, date, and starting timecode search work without it. Description-based search needs a configured AI search service.
No. The Windows app must be running. It reads the files and writes the exports; the dashboard controls that session.
Contact Medialooks about your recording formats, archive, and review workflow.