Shot Prompting
Overview
The Shot Prompting feature in ACT 3 AI allows creators to define detailed instructions for how individual shots should look and feel. By writing descriptive prompts, users guide the AI to generate visuals that match creative intent, including framing, lighting, style, and mood. Shot prompts bridge the gap between scriptwriting and rendering, ensuring cinematic control even when using generative models.
Key Capabilities
- Text-to-Shot Control: Translate descriptions into visual outputs at the shot level.
- Camera Directives: Include lens type, angle, dolly/zoom moves, and depth of field.
- Lighting & Style: Specify mood (e.g., “film noir lighting,” “neon cyberpunk city”).
- Actor Actions: Describe what digital actors do or feel during the shot.
- AI Flexibility: Combine structured tags with free-form language for precision.
How to Use
- Open the Editor workspace and switch to Timeline View or Storyboard.
- Select a shot block and click **Add Prompt**.
- Enter descriptive instructions (e.g., *“Wide shot of a lone astronaut walking across a red desert, golden hour lighting”*).
- Adjust parameters such as resolution, duration, or credit cost.
- Generate a preview using the chosen AI engine (Google Veo 3, WAN AI, or Runway Integration).
Prompt Structure
Effective prompts typically include:
- Camera Direction – e.g., “close-up,” “aerial drone shot.”
- Subject – actor, object, or scene focus.
- Action – movement or behavior.
- Environment – setting details (city street, spaceship interior).
- Mood & Style – tone, artistic influence, or lighting.
Example Prompts
- “Medium close-up of a detective under a flickering neon sign, cigarette smoke swirling.”
- “Tracking shot through a forest at night, fog on the ground, flashlight beams piercing the darkness.”
- “Over-the-shoulder shot of a programmer staring at cascading green code on a retro CRT monitor.”
Collaboration
- Team members can annotate or refine prompts in shared projects.
- Approved prompts can be locked to prevent accidental edits.
- Iterations are saved in the version history.
Credit Usage
- Each generated shot consumes credits based on duration and resolution.
- Example: 5-second shot at 1080p = ~5 credits.
- Higher detail or 4K rendering increases usage (see Billing_Model and Credit_System).
Troubleshooting
- If results don’t match, break prompts into shorter, specific phrases.
- Avoid overloading a prompt with too many conflicting directions.
- Use iterative previews before rendering in full quality.
See Also
Contact Us if you have any problems using our product, or if you have questions.