Docs › After the conversion

Results and Interrupted Tasks

Every conversion, and every Return to Premiere run, is saved as a task in the Results tab, so you can review it later, including after closing and reopening CrossFlow.

The Results tab keeps every past conversion.

For each past task, you can:

  • review the analysis of the source project (media and clip breakdown, project size)
  • review which options were used for that run
  • see in Full Details what was transcoded or replaced and what was converted, including the Encoding Preset used per clip, and any warnings or errors
  • delete the task and its stored results

The top of the list shows how much disk space the stored results take, and Clear all past tasks deletes them all at once.

In Full Details, each line is colored for what it says, not for the clip it belongs to: a clip can be listed under Warning for an effect that could not be transferred while its other lines, such as the keyframes that came across natively, still appear as successes.

Full Details: what was transcoded, then what happened to each clip in Resolve.

If CrossFlow runs into an unexpected problem with one clip, transition, marker or link while building the Resolve project, it does not stop the whole conversion: that item is listed in Full Details as an error saying "CrossFlow ran into an unexpected problem", and the rest of the project is converted. A clip in that case is either left out of the timeline, or placed on it with some of its settings (position, scale, effects, keyframes...) possibly missing, and the line says which. Please report it (see How to report an error): it is something CrossFlow should handle.

If you go back to an older version of CrossFlow after running a newer one, tasks produced by the newer version are not listed, since their results are stored in a form the older version cannot read. They are left untouched on disk and appear again as soon as you run the newer version. A task that the older version can still list, but whose clip data it cannot match up, keeps its history and only refuses the Return to Premiere trip, so it can never send the wrong clips back.

While a task is running, the Results tab shows its live progress instead of the list of past tasks, and the Main tab's options are hidden until the process finishes.

Continuing an Interrupted Conversion#

A conversion can stop before its end: CrossFlow's window stops (for example when the computer runs out of memory during a long transcode), CrossFlow is closed during a run, or the computer restarts. Such a task is listed as "Interrupted" in the Results tab.

If CrossFlow's window stops on its own, it restarts by itself and tells you why. Premiere Pro and Adobe Media Encoder are separate applications, so they usually keep working on the transcode in the meantime.

A conversion that ended in an error during the transcode or the conversion to DaVinci Resolve can be continued the same way, since what was already done is still usable. For example, if DaVinci Resolve stops responding while CrossFlow builds the project, CrossFlow stops with a message saying so instead of waiting for it. Close the applications you don't need, then continue: the transcoded clips are kept and only the conversion to DaVinci Resolve runs again.

When the last conversion did not finish, or failed after the analysis, the Main tab shows an "Unfinished Task" message (right away after an error, and when CrossFlow opens), with two buttons:

  • Continue Task picks the conversion up where it stopped, with the options and the DaVinci Resolve project name it was started with:
    • if Premiere Pro is still working on it, CrossFlow simply follows its progress again;
    • if Premiere Pro already finished it, its result is used as it is, and only the conversion to DaVinci Resolve runs;
    • otherwise the transcode is launched again, but clips already transcoded are not rendered a second time. Each one is checked first, and only the missing, unfinished or damaged files are transcoded again.
  • Dismiss hides the message for good. The task stays "Interrupted" in the Results tab.

Any past conversion can be continued from the Results tab too, not only the last one: a task that can be continued shows a small continue icon next to its status, and its Full Details have a Continue Task button. CrossFlow asks before starting, and names the DaVinci Resolve project that will be created again. For a task that stopped but can't be continued, the Full Details say why. When an older task is continued, a transcoded clip written again since by another conversion (into the same folder, with the same name) is transcoded again rather than reused.

Before continuing, CrossFlow may ask you to close Premiere Pro first: when Premiere Pro was left open while CrossFlow was updated, it still runs the CrossFlow panel of the older version, which would transcode every clip again. CrossFlow opens Premiere Pro again itself.

The interrupted conversion's unfinished jobs are usually still in Adobe Media Encoder's queue: they are handled as described in Media Encoder's Queue, so they are not rendered twice.

If Premiere Pro stops during a conversion (closed or crashed), CrossFlow notices it after about a minute and a half, stops waiting, and shows the same "Unfinished Task" message right away.

If you start a new conversion while Premiere Pro is still finishing an interrupted one, the new conversion waits for it, then starts.

Return to Premiere runs can be continued the same way, from the Main tab's message, the Results tab or the Full Details:

  • stopped while CrossFlow was looking for the graded clips in DaVinci Resolve: it runs again from the start, without having to pick the Resolve project again;
  • stopped during the export from DaVinci Resolve: every clip already exported is checked and kept, and only the missing or damaged ones are exported again;
  • stopped during the replace in Premiere Pro (Premiere Pro closed or crashed, which CrossFlow notices as for a conversion): the exported clips are kept, and only the replace runs again. If Premiere Pro is still replacing, CrossFlow simply follows it again.

DaVinci Resolve not responding: CrossFlow watches every request it makes to DaVinci Resolve, for a conversion as for a Return to Premiere. When DaVinci Resolve stops answering (often because the computer is short of memory), CrossFlow stops with a message saying so, instead of waiting minutes for each remaining clip. Close the applications you don't need, then continue the task.

DaVinci Resolve stuck in the background (Windows): DaVinci Resolve can only run once at a time. If an earlier DaVinci Resolve never finished closing (it is still in the Task Manager, but has no window and does nothing), CrossFlow can't open a new one. While waiting for DaVinci Resolve to open, CrossFlow notices such a process after about a minute and tells you, with the time it was started. End "DaVinci Resolve" in the Task Manager: CrossFlow then opens DaVinci Resolve again and the conversion carries on. A DaVinci Resolve that is simply slow to open, or waiting on one of its own windows, is not reported.

A task can't be continued, and the message says why, when:

  • it was started with another version of CrossFlow;
  • its Premiere Pro project was saved since the task started, because the clips already transcoded (or the places the clips go back to) would no longer match the edit;
  • its Premiere Pro project is no longer where it was;
  • for a Return to Premiere, the conversion it returns from was deleted from the Results tab.

In those cases, just run it again. Starting any new conversion also hides the message.

Something missing or unclear on this page? Write to contact@nablast.com.