Exporting and applying the .cube

MOVON generates one .cube per camera group. How to export them from the panel and apply them in any NLE that reads LUTs.

After Analyze and a confirmed hero, MOVON has one matched .cube LUT ready per non-hero camera group. This page is how those files come out of the panel and how they go onto clips, both inside Premiere and in any other NLE the project ends up in.

Export from the panel

In the MOVON panel, the grouping plan shows the hero camera and the other camera groups with their generated LUTs. Each non-hero group has an Export action.

• Export all writes one .cube per non-hero group into a single folder.
• Export one writes a single group's .cube to a chosen location.

The default destination is the Premiere project folder, under MOVON LUTs/. The naming convention is <project>_<camera-group>.cube, so a project called *Wedding-Cut* with cameras grouped as Cam A, Cam B, and Drone produces Wedding-Cut_CamA.cube, Wedding-Cut_CamB.cube, Wedding-Cut_Drone.cube. The hero group does not get a .cube; the hero is the target, not a clip that needs transforming.

The export is fast. The .cube file is small (a 33³ LUT is a few hundred kilobytes) and writes in under a second per group.

Apply in Premiere

The matched .cube lives in Lumetri Color → Creative → Look, on top of the Input LUT that converts LOG to display space:

1. Select all clips from one non-hero camera (in the bin or on the timeline).
2. Open Lumetri Color → Creative.
3. Look → Browse… and pick the matching .cube for that camera group.
4. Confirm. The matched LUT applies to every selected clip at once.

Repeat for each non-hero camera. The hero camera's clips need nothing applied; they are already the target the others were matched toward.

If the match feels a touch heavy, the intensity slider directly below the Look picker is the right place to pull it back. 70-80% is the common landing zone for skin tones. Below 60% the match starts to disappear; the .cube is built to be applied at full strength on the bulk of the cut and tuned per shot only where it matters.

Apply in DaVinci Resolve

The same .cube files work in Resolve unchanged. The standard load path:

1. Drop the .cube files into the Resolve project's LUT folder, or any folder Resolve is configured to scan.
2. On the Color page, right-click the matched camera's first node and **Apply LUT → MOVON folder → <project>_<camera-group>.cube**.
3. To apply across many clips, select all clips from that camera in the timeline thumbnails (Cmd+click), then right-click and Apply LUT.

Resolve handles the .cube the same way it handles any other 3D LUT: as a transform on a node. Put the matched LUT on a dedicated node so it can be bypassed for QA without losing the creative grade.

Apply in Final Cut Pro

In Final Cut Pro, the matched .cube goes on as a Custom LUT:

1. Select the clips from one non-hero camera.
2. In the inspector, add Effects → Color → Custom LUT.
3. LUT dropdown → Choose Custom LUT… → pick the matching .cube for that camera group.

Final Cut keeps the LUT as a per-clip effect. Drag the Custom LUT effect onto a compound clip if grouping the camera's clips into one container makes downstream finishing cleaner.

Carrying the .cube between tools

The .cube is a plain text file in a standard format (33³ trilinear, three RGB values per line, ASCII). It opens in any LUT-aware tool, including Lumetri Color, Resolve, Final Cut, and most plugin-level color tools. No conversion needed. The longer format note lives at .cube specification.

This portability is the point: a project matched in Premiere can finish in Resolve without re-running MOVON, because the file the matched look is encoded in is something every NLE already understands. Standard formats are how a project survives the next tool migration.

What changes when MOVON's effect ships

Once one-click apply through MOVON's own effect lands, the same .cube data will write back to every camera's clips on the timeline as a single undo step. The export-to-Lumetri flow above will still work for cross-tool finishing; the one-click path will be the in-Premiere shortcut. The dispatch on the homepage carries the cut when it lands.