AI video 6 min read
Runway in DaVinci Resolve: Plugin and Browser-to-Editor Workflows Compared
Use the Runway plugin when your creative question concerns footage already in a DaVinci Resolve edit and you want the generated result close to that timeline. Use a browser-based creation route when the idea, source images, or scene design still needs development before it belongs in the cut. The useful distinction is where the next decision happens.
This is a workflow comparison from MyloStudio's own blog. Our studio supports image and video generation, editing, sound, and assembly, making it relevant to developing material before a professional edit. We do not claim a MyloStudio Resolve plugin or automatic timeline synchronization.
What Runway's plugin provides#
Runway's September 23, 2026 announcement describes generating images and videos within Resolve, working on a selected source range, comparing a result, and importing it into the Media Pool and timeline. The download is free for macOS and Windows; it requires DaVinci Resolve Studio 19 or later, and generation uses credits from a paid Runway plan. Free installation therefore does not mean free generation. Runway's Resolve announcement
Check the current installer and your actual software version before planning a session around it. A statement about Resolve Studio should not be silently extended to the free edition. Similarly, the presence of a model in one Runway surface does not establish that every possible control or export setting is available in the plugin you have installed.
Two routes from question to accepted shot#
Plugin route: identify the timeline problem → select the relevant material → generate or revise in the panel → compare → import the result → review it inside the cut.
Browser route: prepare the source and brief → create or revise in the chosen studio → accept a version → export → inspect and import the file → review it inside the cut.
The browser route has an explicit file handoff. The plugin route brings that handoff closer to the edit. Neither route removes creative review, and neither guarantees that a generated shot will fit the timing, visual language, or sound of the surrounding sequence.
| Decision | Plugin route is relevant when… | Browser route is relevant when… |
|---|---|---|
| Starting material | The selected timeline shot is the source | References and a brief come before the edit |
| Main uncertainty | How a particular revision fits the sequence | What the scene should be |
| Reviewer focus | Neighboring shots, duration, and continuity | Subject, composition, action, and concept |
| Revision handoff | Work can stay close to the selected footage | An accepted replacement file can be delivered clearly |
Begin with the edit's problem, not the effect#
Imagine a sequence about a bicycle repair workshop. The cut moves from a close-up of a wheel to a wide shot of the workbench, but the wide shot feels visually flat. The problem might be its light, its background, its duration, or simply its position in the sequence.
Write the problem in one sentence before generating. “Make the wide shot feel like late afternoon while keeping the mechanic's action readable” is a clearer production request than “make this cinematic.” It establishes what changes and what still needs to function.
If the problem is a pause between two actions, first consider whether trimming the edit solves it. If the problem is that the workbench does not exist in the source material at all, creating a new shot may be more appropriate than repeatedly transforming the wrong source.
The plugin is attractive when the selected shot and its neighboring cuts provide the essential context. A separate creative studio is attractive when you need to develop the environment or assemble references before deciding which shot should enter the sequence.
Protect the original and name the replacement#
Keep the original material available during review. A generated revision may solve the requested light change while altering the tool in the mechanic's hand. If the source has been displaced or ambiguously renamed, comparison becomes slower and mistakes become easier to miss.
Use names that distinguish source, attempt, and accepted replacement. A name such as “workbench_wide_warm-light_v2” communicates more than “final-new.” Record the source range and intended purpose in your project notes, particularly when several similar shots exist.
Before accepting the revision, play the original and revised versions in context. Check the mechanic's action, the direction of the bicycle, and the transition from the wheel close-up. A convincing standalone wide shot can still break the sequence if screen direction reverses.
Build the scene in MyloStudio when the idea is still open#
For a scene that does not yet exist, MyloStudio can help interpret your references, generate a visual starting point, animate it, and revise the result. Start by distinguishing the workshop's appearance from the action you want to show.
An illustrative brief could read:
Use the workshop photograph for the arrangement of the bench and hanging tools. Create a quiet closing-time scene. The mechanic places a wrench on the bench and steps back from the bicycle. Preserve the bicycle's visible frame shape. Keep the action easy to read from a medium-wide viewpoint.
Review the scene before deciding its place in the edit. If the bicycle frame changes or the wrench appears in both hands, request a focused revision. If the action is correct but the scene is too busy, simplify the background rather than adding another stylistic demand.
MyloStudio can also help assemble shots into a sequence, but a creative assembly and the final Resolve project serve different purposes. Decide which environment owns the final timing and finish so that revisions do not become competing versions of the same film.
Inspect the file before importing a large batch#
For a browser-based route, begin with one accepted file. Check that the output you actually downloaded is suitable for the intended project. This guide does not promise a particular MyloStudio codec, frame rate, color space, or audio layout.
| Handoff item | What to inspect | Why it matters |
|---|---|---|
| Picture dimensions and framing | The visible crop and subject position | A change of frame shape can remove essential action |
| Duration | First action, last action, and usable pause | The shot needs room to enter and leave the edit |
| Frame cadence | Playback in the intended sequence | Motion can feel different after conforming |
| Audio | Presence, timing, unwanted sound, and intelligibility | A picture revision may also change the sound relationship |
| Color appearance | The imported file beside adjacent shots | A pleasing isolated image may mismatch the sequence |
| File identity | Version and source relationship | Later revisions must replace the correct shot |
If the file imports but behaves unexpectedly, isolate the issue before generating more. Determine whether the problem is in the source file, project settings, or creative content. Regenerating the scene does not necessarily solve a technical handoff problem.
Make revision requests refer to the current cut#
Once a shot is in the timeline, revise against its role there. “Hold the mechanic's final pause a little longer so the next close-up has a clean transition” gives the creator an editorial purpose. “Make it better” does not identify whether to change action, timing, framing, or detail.
When returning to a browser workflow, include the accepted version and a precise description of the change. When staying in a plugin, preserve the same discipline. Convenience should reduce unnecessary movement between tools, not reduce the clarity of the brief.
Choose Runway's plugin when the documented integration fits your Resolve setup and the edit is the center of the work. Choose MyloStudio when you want to develop and revise the scene from your ideas and materials before handing an accepted result to the editor. In both cases, the final test is the shot's behavior inside the sequence.