Ray3 Tutorials: Zero to Controlled Production

TL;DR

Progress through Ray3 in layers: basic text-to-video, camera precision, keyframes, looping, HDR/EXR finishing, and API-ready automation. Each tutorial includes a friction test so you know you’ve leveled up before moving on, and builds assets you can drop straight into production.

Open Prompt Library · Track API Progress

Why This Path Works

• Momentum builds fastest when you validate shot grammar before chasing style; tutorials reinforce that order.
• Modular walkthroughs prevent gaps—camera control, pacing, finishing, and automation each get focused reps.
• Frequent friction tests (loop smoothness, exposure match, metadata logging) make progress measurable and shareable with leads.
• Documentation habits (Parameter Cards, checklists, shot IDs) prepare you for production handoffs and future automation.
• The curriculum mirrors real deliverables: storyboards, animatics, graded masters, and API endpoints become portfolio pieces.

Learning Path

1. Text → Video Foundations: craft prompts with shot size, movement, lighting, and 6-second duration; confirm camera obeys instructions by comparing to a reference storyboard.
2. Image Conditioning: add a reference frame to stabilize style and composition; measure similarity scores and adjust lighting cues to maintain look.
3. Looping & Extensions: use Draft Mode to nail seamless loops and extend sequences without jump cuts; run a visual inspection plus waveform check.
4. Keyframes & Pacing: anchor start/end poses or camera moves; enforce BPM-driven timing per shot and align transitions in your NLE.
5. Draft → Hi-Fi Discipline: apply the budget ratio, promote only validated drafts, and log parameters; grade a short sequence to verify HDR handling.
6. HDR/EXR Finishing: run the export checklist, align ACES/Rec.2100 pipelines, and create both HDR and SDR trims for the same shot.
7. API Prep: mirror the submit/get_job/get_asset contract locally, simulate payloads, and log analytics to prove readiness when Ray3 opens.
8. Team Scaling: document SOPs, create reusable Prompt Library tags, and set up analytics dashboards for prompt_copy and tool usage.

Tips While Practicing

• Restrict each session to one capability so you can isolate wins and regressions; context switching slows learning.
• Use the Camera Phrase Helper to translate storyboards into precise language before generating; keep versions for A/B comparisons.
• Compare outputs side by side in a shared board (Figma, Notion, Miro) to spot pacing drift or lighting inconsistency quickly.
• Track learning milestones with reading times (10–15 min each) and practice durations so leads can schedule training realistically.
• Schedule peer reviews; having another eye on camera grammar surfaces blind spots faster.

Common Pitfalls

• Jumping to HDR before the camera language is solid—keep finish work for later modules so you’re not polishing shaky shots.
• Skipping Parameter Cards, which removes the audit trail you need for approvals, regrades, or bug reports.
• Mixing loop practice with long-form shots; shorter clips teach timing faster and prevent momentum loss.
• Treating prompts as disposable; instead, organize them by genre/camera/lighting so future you has references.
• Ignoring analytics—if prompt_copy event volume drops, your library may need pruning or clearer labeling.

Checklist

• Module 1 prompt hits shot size, movement, lighting, duration, tempo.
• Module 3 loop passes a seamless playback test and BPM check.
• Module 5 includes Draft vs. hi-fi budget notes and version history.
• Module 6 exports graded HDR and SDR trims plus QC reports.
• Module 7 integrates submit/get_job/get_asset with mock data and alerts.
• Module 8 publishes SOPs and connects analytics dashboards.

FAQ

How long should I spend on each module?
Plan 30–60 minutes for focused drills; repeat until the friction test passes three times in a row.

Where do I log practice clips?
Use shared Parameter Cards linked to prompt entries in the library so teammates can replicate results or troubleshoot quickly.

Can I skip straight to HDR training?
Only after camera and pacing control feel automatic; otherwise you’ll chase exposure issues instead of storytelling wins.

Do I need a team to follow this path?
No, but documenting your work with cards and SOPs makes onboarding future collaborators far easier.

How do I know I’m ready for API access?
When your mock contract handles retries, logging, capability flags, and metrics, you’re ready to swap to Ray3 with minimal downtime.