Learn / Development guide

Choose the output your next step needs.

Keep rendered files, editable Fusion and direct Resolve transfer distinct, and inspect the actual result before another action.

Development guide · source-reviewed foundation · public-package walkthrough pending

Choose the destination and method.

RoutePurpose
FilesSave output to a chosen folder
ResolveDeliver to a deliberately selected local destination
Files → ResolveSave output, then send the saved result

Rendered media preserves the finished appearance within the chosen format. Editable Fusion prepares supported elements for editing in Resolve. These are different documents/results; neither implies automatic bidirectional synchronisation.

Use the format advertised by your candidate.

Format and codec support vary by platform, route and candidate. The older source-reviewed foundation describes stills, sequences, GIF and audio routes; it is not a current comprehensive format matrix. Newer native media work does not automatically qualify every container or codec.

  • Check dimensions, frame rate/count and the selected range.
  • Inspect alpha in the actual format/output; some formats cannot carry it.
  • Check audio duration, alignment and meaningful playback.
  • Keep original sources available; preview proxies do not replace them.
  • Do not infer support from an extension or visible setting alone.

Export a small local result.

  1. Save and confirm comp, size, rate and duration.
  2. Apply pending templates and resolve missing media/asset requests.
  3. Open Deliver and choose Files with a supported method/format.
  4. Review full-comp versus marked scope, output folder/name and collision handling.
  5. Read the plan/refusals, then export.
  6. Inspect first/middle/final output and duration, rather than only success feedback.

Make destination identity deliberate.

Editable generation runs locally; no hosted compiler or Carvercat account is required. Resolve needs the specific route’s qualified edition/version and setup. A Free-compatible internal route does not imply every Free/Studio/version combination is supported.

Choose project, timeline, track, placement and insert/replace intent before sending. Action labels can differ by route. Check the actual plan. Use a disposable destination for learning.

Verify what remains editable.

Inspect actual Fusion output and change a supported control. Check appearance, intermediate motion, placement, duration and destination save/reopen. Custom carvercat promotion does not certify Edit Inspector controls, arbitrary effects or reverse sync.

A successful compiler/golden check is structural evidence. Actual Resolve rendering and editing are required for destination claims.

A known failed send differs from an unknown outcome.

Saved-output retry may reuse verified unchanged output for a known failed send. Source/settings/output changes can invalidate that reuse. Session-lifetime send state is different from durable render jobs.

Use rendered output in other editors.

Other editing applications can import suitable rendered media through their own workflows. That is not native editable-title integration. Frame rate, sequences, alpha and audio interpretation require destination-specific inspection.