A selected clip is not necessarily the input an integration will render. Before submitting a paid edit, check the plugin's documented source rule and its visible preview. A highlight in the timeline, the playhead location and the In/Out range can point to three different pieces of material.
Read the integration's source contract
Runway's DaVinci Resolve plugin guide says its Edit Studio flow works from the playhead or In/Out range rather than a selected clip. That behavior belongs to the documented Runway integration. Do not generalize it to every Resolve plugin or describe it as an Imagild feature.
Record the current sequence, the playhead time and any active range marks before opening the workflow. In a multilayer edit, also inspect what the rendered preview actually contains: a title, adjustment or neighboring cut can be part of a range even when one underlying clip is selected. The preview is evidence of the submitted input; the selection color alone is not.
Reconcile three visible choices
Consider a fictional sequence with a portrait interview followed by a product insert. The interview is highlighted, but the playhead rests on the product. A third range mark still covers an earlier montage. Decide which passage should be edited and make the integration's source preview match that intention before submitting anything.
| Timeline state | What to verify |
|---|---|
| Highlighted interview | Does the plugin actually use selection? |
| Playhead on product | Is this the source currently rendered? |
| Existing In/Out marks | Do they override or define the requested range? |
This hypothetical check does not require a generation. Inspect the start and end of the prepared source, count its shot changes and verify its duration through the integration's available review controls. If the panel does not provide enough evidence, use a supported explicit export/import route rather than guessing.
Keep the result's identity separate
The same official guide documents where imports land. Check the actual returned media and timeline placement instead of assuming the original selected shot was replaced. A newly appended result can look unrelated if you keep watching the old source instance. Identify the new asset, its source interval and the intended destination before making further edits.
If you discover a wrong source after submission, preserve the task state and inspect its status before submitting again. Changing the selected clip while a cloud job is running does not retroactively change that job's input. Nor does cancelling a local panel necessarily establish a refund or remote cancellation.
For footage planned in Imagild and finished externally, keep an input note containing sequence, source interval and intended edit. Accept a plugin task only when its prepared source visibly matches that note. This guide reports no paid plugin test; it offers a source-verification procedure designed to resolve the mistake before generation rather than after an attractive but irrelevant result arrives.