Ray3 Prompt Library & Shot Planning
TL;DR
This library keeps Ray3 prompts organized by genre, camera move, lighting, and style so you can grab the right template fast. Every prompt has a TL;DR you can copy, parameters to replicate, pitfalls to dodge, and related templates for clustering sequences or campaigns.
Follow Tutorials · Check API Tracker
Why the Library Matters
- Prompt scaffolds with precise camera language reduce failure cases across teams and make remote collaboration smooth.
- Organized clusters (genre, movement, lighting) let you mix and match templates to build full shotlists without reinventing the wheel.
- Each template links to related shots so you can plan sequences, experiment with variations, and cover B-roll needs quickly.
- Copy tracking via analytics (
prompt_copy
) shows which templates actually ship and which need refinement. - Shared vocabulary across Parameter Cards, prompts, and shotlists keeps legal, creative, and technical teams aligned.
How to Use the Library
- Filter by genre, camera move, or lighting to narrow options, or jump via the sticky TOC.
- Copy the TL;DR prompt and replace subject, setting, duration, or BPM while keeping camera language intact.
- Adjust parameters (duration, camera modifiers, lighting specifics) to match your brief, then run Draft Mode to validate movement.
- Log results in the Prompt → Shotlist tool, update Parameter Cards with wins or misses, and mark favorites for future reuse.
- Share learnings in-line; note which clients approved which prompts and why so others can replicate success.
Prompt Clusters
- Genre Cards: product hero, automotive, fashion, documentary, experimental—each links to curated templates and the matching TL;DR.
- Camera Moves: dolly, track, orbit, follow-cam, tripod sequences; pick one that fits your storyboard and chain related templates for coverage.
- Lighting Looks: top, rim, volumetric, neon, practical mixed lighting; control exposure and mood with one dominant cue per shot.
- Shot Size Mixes: WS/MS/CU/ECU bundles for assembling complete sequences quickly; each bundle includes recommended pacing and transitions.
- Special Modes: Draft-first sets, HDR-ready prompts, looping-friendly templates for stickers or background plates.
Tips for Editing Prompts
- Keep one lighting descriptor per prompt; add color palette or material notes after camera terms so Ray3 prioritizes movement.
- Note movement speed explicitly (“slow orbit 90°,” “medium track forward 5m”) to avoid jitter or overshoot.
- Mention duration and BPM to control pacing when combining shots, especially if you cut to music.
- Attach reference frames for style stabilization and mention lens attributes (“anamorphic flare,” “35mm prime”) only after camera verbs.
- Version prompts sequentially (v1, v2, v3) with short notes so you can trace how language improved output quality.
Common Pitfalls
- Copying prompts without adjusting subject scale, leading to mismatched compositions or cut-off subjects.
- Mixing lighting cues (“neon + top light + volumetric”) which confuses Ray3’s exposure logic and adds flicker.
- Forgetting to update duration; mismatched timings break edit rhythm and require manual retiming later.
- Skipping Parameter Cards, making it hard to reproduce a winning look or explain why a version failed.
- Losing track of analytics; if nobody copies a template for a month, revise or archive it.
Checklist
FAQ
How many prompts should I prepare per project?
Plan 1.5× your needed shot count so you can swap underperformers without re-scoping or stalling the edit.
Can I mix multiple templates into one prompt?
Yes, but keep camera instructions singular—merge lighting or palette details after the movement statement so Ray3 keeps focus.
Where do I log feedback on a prompt?
Add notes to the Parameter Card, update the template entry with learnings, and link related prompts for future reference.
How do I maintain prompt hygiene over time?
Archive outdated language quarterly, refresh examples with current campaigns, and use analytics to retire low-performing templates.
What’s the fastest way to translate prompts into shotlists?
Use the Prompt → Shotlist tool: paste the TL;DR, generate 3–5 camera directions, then export as CSV for your production tracker.