Urgent.News

What's breaking now, across thousands of outlets.

AI

Writing better prompts for image-to-video: camera moves, motion and start frames

Image-to-video models are surprisingly literal. Give them a vague prompt and they invent motion you didn't want; give them a clear start frame and a short, specific motion brief and they behave much more like a camera operator. Here is the checklist I use. 1. Let the start frame carry the composition The single biggest upgrade is to stop describing what is already in the image. If your start…

Image-to-video models can take prompts that are too vague and interpret them in unexpected ways, like inventing motion that wasn't intended. However, by providing a clear start frame and a concise description of what should move, how the camera should move, and the pace of the action, the model can produce more predictable results. Here's a simple checklist for writing better prompts for image-to-video:

1. Let the start frame do the heavy lifting by showing the key composition elements. Avoid repeating these details in the prompt, as the model will likely re-imagine the scene.

2. Limit camera moves to one per clip, focusing on specific actions like push-in, pull-out, orbit, pan, or static shots. This will help maintain a coherent shot.

3. Describe motion using verbs and pace words, such as "turns her head," "smiles slightly," or "slowly." Avoid writing "The woman moves" as it provides little direction to the model.

4. Include small, subtle motions in the background to give the clip a sense of life, like hair in the breeze or steam rising from a cup. Phrase these requests as "subtle" or "light" to prevent them from competing with the main action.

5. Use a template to structure your prompts, separating the camera move, main subject action, secondary ambient motion, lighting changes, and style or mood constraints. For example: "[camera move], [main subject action with pace], [secondary ambient motion], [lighting change if any], [style/mood constraint]."

6. Test different models with the same start frame and prompt to find the best performer for your specific needs. Some models may excel at smooth camera work, while others are better at faces or physics.

7. If you encounter issues like subject morphing, camera drift, or flickering textures, adjust your prompt accordingly. Shorten the prompt, remove unnecessary adjectives, add "locked-off camera" or specify one camera move, slow down the action, or simplify the start frame. By separating the composition from the motion, you'll achieve more consistent and predictable results.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in AI

How much RAM you actually need to run AI locally

Higher-end AI PCs landed this month at prices that make people ask the wrong question first: which one is worth the money?

  • Small models (7–8B parameters) need around 5 GB at 4-bit quantization.
  • Mid-size models (30B) require approximately 15–20 GB at 4-bit, not including context.
  • Large models (70B) need about 35–40 GB at 4-bit, plus context.

A Photographer’s Perspective on New Tools

** The Evolving Lens ** For over a decade, my work as a photographer has centered on observing reality. Capturing genuine human emotion requires patience, natural light, and an eye for unscripted…

  • Photographer sees reality as career focus for over a decade.
  • AI tools enhance, don't replace, creative intent in photography.
  • Technology provides new lens, preserves human perspective in images.

TouchGrass AI: Building a Local AI Companion That Gets You Outside 🌿

TouchGrass AI: Building a Local AI Companion That Gets You Outside 🌿 An AI companion designed to help you spend less time on screens and more time in the real world. 1.

  • TouchGrass AI aims to encourage outdoor activities over screen time
  • App generates personalized outdoor micro-adventures based on user input
  • Local AI implementation prioritizes privacy and offline functionality

MCP vs A2A vs ACP: Open Protocols for Multi-Agent Systems, Compared

MCP vs A2A vs ACP: Open Protocols for Multi-Agent Systems, Compared If you're building a multi-agent system, you've hit this question: how should agents talk to tools, and how should they talk to each…

  • Multi-agent systems require open protocols to streamline agent-tool and agent-agent communication.
  • MCP maintains by Anthropic, standardized open protocol; A2A maintained by Google, industry support.
  • MCP solves Agent ↔ Tool/Data layer, A2A solves Agent ↔ Agent layer.

More from Sunday 11 October →