Choose the input your actual generator accepts, rather than the one that looks easiest to draw. A path sketch describes a route, a text prompt describes movement in words, and a camera-reference video provides a continuous example. They can express similar intentions, but they are not interchangeable files or controls.
Read the connection between the canvas and the model
A canvas may contain a photo, a colored line and a video node. That does not prove the video model directly reads the line. The canvas could convert the drawing into text, send an annotated image, or use a dedicated path control. Find out which of those happens before you rely on the result.
Kolbo lists a Draw to Video mode. That is a product-specific workflow, not evidence that every model listed on the page accepts arbitrary line coordinates. Ask what data reaches the renderer and whether the tool documents timing, direction and camera-versus-object interpretation.
Pick the representation that carries your requirement
| Requirement | Useful representation | Missing information to add |
|---|---|---|
| Move left past a foreground plant | Text or a documented path tool | Speed, finish and subject behavior |
| Repeat a real handheld retreat | Camera-reference video | New subject and scene requirements |
| Follow a curved route around furniture | Path sketch plus a brief | Height, clearance and stopping point |
Adobe describes a video camera reference. Runway describes motion in text alongside an image. Use these as examples of different contracts, rather than a recommendation that one is always more accurate.
Translate one route into a complete brief
For a fictional room shot, draw an arrow from the doorway toward a table and then curve toward a window. Add a written explanation: the arrow represents the camera, the person remains seated, the viewpoint stays near eye level, and the movement ends before reaching the table.
Without that explanation, the line could be interpreted as a walking route, an object trajectory or a graphic that should appear in the output. Specify whether annotations are instructions only. Keep the clean source photo separately so you can verify that no arrow, label or canvas interface leaked into the video.
An Imagild prompt or shot plan can hold the written version of this route. Do not treat that text as a claim that Imagild currently exposes the drawing tool or accepts a path file. Confirm the chosen renderer's supported inputs separately.
Run a contract check before an effect check
First verify that the intended photo, reference and instructions reached the right fields. Then review the result. If the output contains a visible arrow, resolve the annotation interpretation. If the person walks along the path while the camera stays still, resolve the moving entity. If the camera reaches the wrong place, clarify the destination.
A successful test should show one understandable move, clean scene content and the intended final composition. Add route complexity only after those requirements hold. Keep the accepted brief and the exact input files together; a line alone is rarely enough to reconstruct why a previous attempt worked.