Ray3 with Dream Machine: Hybrid Workflow
TL;DR
Use Dream Machine for fast ideation and style exploration, then shift critical shots to Ray3 when you need rock-solid camera control and HDR/EXR finishing. Keep both systems in sync with shared prompts, Parameter Cards, and consistent shot planning so clients see continuity from pitch to delivery.
Learn the Tutorials · Check Prompts
Why Pair Them
- Dream Machine delivers quick visual directions for client approvals, mood boards, or social tests when time is scarce.
- Ray3 adds disciplined camera grammar, HDR-ready renders, and audit trails when the shot must hold up in post.
- Alternating tools keeps pipelines moving even when one queue is busy or when pricing shifts unexpectedly.
- Shared analytics (prompt_copy, tool_open_shotlist, hdr_checklist_open) prove which platform drives outcomes and where to invest budget.
- Having both in play reduces risk: if Ray3 access is limited, you can still prototype in Dream Machine and upgrade later.
Workflow Steps
- Draft storyboards in Dream Machine using the same camera template (shot size, movement, lighting, duration, tempo) to gather quick stakeholder feedback.
- Present mood boards or animatics; capture notes on pacing, style, and lighting, and translate them into Parameter Cards.
- Migrate approved shots to Ray3 prompts, tightening camera language, lighting control, and HDR requirements while maintaining subject descriptors.
- Run Draft Mode in Ray3, compare outputs to Dream Machine references, and iterate until movement, exposure, and rhythm align.
- Upgrade winning shots to hi-fi/HDR, export masters, grade or composite as needed, and archive both versions for documentation.
Tips for Smooth Handoffs
- Keep a synced Prompt Library with tags indicating which platform produced each shot and why; note success metrics or feedback.
- Match aspect ratios and frame rates across platforms to avoid reframing or audio sync shifts when you transition to Ray3.
- Note discoveries from Dream Machine (palette, lens look, particle effects) and layer them into Ray3 prompts after camera terms.
- Use the Prompt → Shotlist tool to maintain one shot plan, regardless of provider; treat Dream Machine outputs as visual references.
- Set analytics alerts when a Dream Machine prompt converts to shipped work; evaluate whether Ray3 should mirror that language.
Common Pitfalls
- Treating Dream Machine outputs as final; camera inconsistencies and lack of HDR may surface later in grade or comp.
- Forgetting to adjust lighting language when shifting to Ray3, leading to exposure drift or flicker in hi-fi renders.
- Mixing platform exports without grade; align color management and LUTs before presenting or cutting sequences.
- Neglecting to update Parameter Cards, breaking traceability between providers and forcing manual detective work.
- Allowing version sprawl; document which shots moved from pitch to Ray3 hi-fi so the team knows the latest source.
Checklist
FAQ
Why not stay in Dream Machine?
Use it for speed, but switch to Ray3 when camera accuracy, HDR finishing, enterprise control, or client audits are required.
How do I align color between platforms?
Use LUTs or grade references; log palette, lighting, and exposure notes in Parameter Cards so Ray3 matches the Dream Machine look.
Can I automate the handoff?
Yes—normalize prompts through your submit/get_job/get_asset contract so both providers plug into the same abstraction, then toggle via config.
What if Dream Machine bests Ray3 on style?
Blend the two: keep Dream Machine plates for stylized segments, but use Ray3 for shots requiring camera discipline or HDR depth.
How do I report metrics to leadership?
Track time-to-approval, cost per render, and revision counts across platforms; present the data alongside creative wins to justify Ray3 investment.