Why do I need to include duration and aspect ratio in the prompt?

The Gemini Omni Video model expects both fields to resolve temporal and spatial constraints. Providing them helps prevent timing drift, cropping, or letterboxing and improves overall consistency. Use the Prompt Constructor subgraph to add them correctly.

What happens if my prompt’s duration doesn’t match the source clip?

You may see truncation, repetition, or timing artifacts. For best results, set the prompt duration to the exact clip length (in seconds) from LoadVideo so the edit aligns frame-for-frame.

How do I avoid stretching or cropped outputs?

Match the prompt’s aspect ratio to the source video’s aspect ratio. If the input is 1920x1080, use aspect ratio: 16:9. Mismatches can introduce letterboxing or unintended crops.

Does this workflow handle audio?

This workflow focuses on visual edits. If you need audio, export the edited video and remux it with the original audio track in a video editor or command-line tool.

Gemini Omni Flash - ComfyUI Workflow

This workflow lets you precisely edit an input video with a single, well-structured prompt using Google’s Gemini Omni Video through the GeminiVideoOmni node. It starts by loading your source clip via LoadVideo, then routes the frames and your instructions to GeminiVideoOmni, which performs the video-to-video transformation. A small, focused subgraph called Prompt Constructor (subgraph id: 331103d2-d660-4a88-abf0-1117dc46b2df) helps you assemble a clean, model-friendly prompt that includes the two required parameters for Gemini Omni Video: duration and aspect ratio. The output can be reviewed instantly in PreviewAny and finalized with SaveVideo.

Technically, the workflow reduces ambiguity by embedding temporal (duration: e.g., 5s) and spatial (aspect ratio: e.g., 16:9) constraints directly into the prompt, which is important for stable, temporally consistent edits. The MarkdownNote node embedded in the graph provides guidance and examples so you can iterate quickly. Together, these nodes create a tight loop for prompt-driven visual effects, color/style changes, or localized alterations, without manual keyframing or complex compositing.

API

Use this workflow from code

Every Comfy workflow is a JSON graph. The payload below is this workflow, exactly as ComfyUI runs it — fetch it from the URL, keep it in version control, or load it in ComfyUI and run it node by node.

GET https://comfy.org/workflows/download/a0e9a3b16f63.json

Fetching workflow JSON…

Run it from Python or TypeScript with the Comfy SDK. The same code targets Comfy Cloud or a ComfyUI you host yourself — only the base URL changes.

# Install (beta)
pip install comfy-sdk        # Python
npm i @comfyorg/sdk          # TypeScript

# Run this workflow (Python)
from comfy_sdk import Comfy

client = Comfy(api_key="comfyui-...")
wf = client.workflows.from_file("workflow_api.json")
job = client.run(wf)
for output in job.get_outputs("<output-node-id>"):
    output.to_file(output.name)

The SDK takes a workflow in API format: open this workflow in ComfyUI and use File → Export Workflow (API). API access requires a Comfy Cloud plan with an API key. SDK docs · Get an API key

FAQ

Frequently Asked Questions

View all workflows