Ray3 Draft Mode: Faster Iterations
TL;DR
Draft Mode is your sandbox for testing pacing, camera moves, and composition before you spend on hi-fi. Plan multiple variations, log every attempt, and promote only the takes that nail movement and timing. Treat Draft outputs like animatics: they guide decisions, not final quality, and they anchor conversations with stakeholders.
Study Tutorials · Raid the Prompt Library
Why Draft First
- Draft Mode costs less and returns faster, enabling broader exploration without burning production budget or GPU credits.
- Camera language sticks once you front-load shot size, movement, speed, and duration in each prompt; Draft runs test whether Ray3 obeys those cues.
- Comparing 3–5 drafts side by side exposes pacing issues long before edit or grade, giving editors a head start on rhythm.
- Stakeholders can sign off on coverage using Draft clips, reducing downstream surprises when you swap to hi-fi.
- Draft archives become training data: over time you learn which phrases unlock reliable moves and lighting setups.
Draft Mode Workflow
- Break your script into 3–7 shots with explicit shot size, angle, movement, duration, lighting, and tempo; capture them in the Prompt → Shotlist tool.
- Generate Draft runs (4–8 seconds) with minimal style words; record prompt, seed, fps, aspect ratio, and quick notes in Parameter Cards.
- Review for camera accuracy, subject coherence, rhythm, and exposure; tighten prompts to fix drift, adjust movement speed, or clarify lighting.
- Host a quick playback review with key stakeholders; label keepers, alternate options, and reshoots directly in the library.
- Tag winners for hi-fi or HDR upgrades, schedule renders in your post pipeline, and archive unused drafts for reference.
Tips for Better Drafts
- Anchor your prompt with verbs: “slow dolly-in,” “medium orbit 90°,” “tripod pan left 45°”; Ray3 follows verbs more reliably than adjectives.
- Mention lighting once (“top light,” “volumetric haze,” “neon rim”) to keep exposure stable and predictable when you upscale.
- Swap filler adjectives for measurable cues: pace, distance, BPM, camera height, or speed percentages; they survive upgrades.
- Keep durations short so you can stack more permutations per hour; extend only after the move works.
- Store references or LUTs alongside prompts so visual intent stays consistent during reviews.
Pitfalls to Avoid
- Sending stakeholders Draft clips without context—always label them as motion studies and embed notes on what will improve in hi-fi.
- Dropping movement terms between iterations, which reintroduces drift and forces rework when you upscale.
- Ignoring failed attempts; annotate why they missed so you don’t repeat phrasing that confuses Ray3.
- Upgrading every Draft to hi-fi; commit to a budget ratio before you render so you protect final polish time.
- Mixing Draft outputs from multiple aspect ratios; keep them aligned to avoid reframing later.
Checklist
FAQ
How many Draft runs should I plan per shot?
Three to five variations usually surface the best pacing without overwhelming review time; add more only if camera drift persists.
Can I carry Draft seeds into hi-fi?
Yes—log the seed and camera parameters in your Parameter Card so you can reproduce the path when upgrading or rerendering.
Do style words matter in Draft Mode?
Keep them minimal. Use Draft runs to validate camera, movement, and timing; add stylistic nuance during hi-fi passes when the shot is locked.
How do I share Drafts with clients?
Watermark them, include a caption that they are motion studies, and link to the plan for hi-fi upgrades so expectations stay clear.
What if Draft latency spikes?
Check the News timeline for platform alerts, queue renders during off-peak windows, and adjust your budget ratio temporarily.