Rendering System

From ACT3ai MediaWiki
Revision as of 16:12, 27 August 2025 by Rafin (talk | contribs) (→‎See Also)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

Overview

The Rendering System in ACT 3 AI powers the transformation of scripts, scenes, and digital actors into AI-generated video. It connects creative inputs (scripts, storyboards, timelines) with compute-intensive AI models like Google_Veo_3, Runway, and WAN AI, delivering both quick previews and production-quality outputs.

Key Components

  • Rendering Engines: Specialized AI models for different visual styles.
  • Resolution & Quality Settings: Draft, Medium, High, Ultra/4K.
  • Credit Usage: Each render consumes credits depending on resolution, duration, and model used.
  • Render Queue: Manages all rendering jobs.
  • Preview vs Final Renders: Quick low-res iterations before committing to final exports.

Supported Engines

Render Workflow

  1. Prepare scenes and shots in the Editor.
  2. Select **Render → Add to Queue**.
  3. Choose settings:
    1. Resolution (Draft, 720p, 1080p, 4K).
    2. Quality (low-cost draft → cinematic).
    3. Engine (Google Veo 3, Runway, WAN AI, etc.).
  4. Confirm estimated credit cost.
  5. Render job runs in the Render Queue until complete.
  6. Download output or send to Build Video / Export Distribution.

Resolution & Credits

Resolution Preview (per 10s) Final Render (per 10s)
Draft (low-res) 1 credit N/A
720p 2 credits 4 credits
1080p 2 credits 5 credits
4K 4 credits 10 credits

Preview vs Final Rendering

  • Previews: Fast, low-cost, lower resolution, used for timing and rough visualization.
  • Final Renders: High resolution, polished visuals, suitable for distribution.
  • Strategy: Use draft previews frequently; only commit to final renders once locked.

Best Practices

  • Always generate draft previews before 4K outputs to save credits.
  • Use WAN AI sessions for brainstorming and collaborative testing.
  • Group jobs into the Render Queue overnight to avoid bottlenecks.
  • Keep track of credit usage in the dashboard.

Troubleshooting

See Also


Contact Us if you have questions about rendering or engine performance.