Rendering System: Difference between revisions

From ACT3ai MediaWiki
Jump to navigation Jump to search
(Created page with "= Rendering System = '''Topic:''' Rendering_System '''Title:''' Rendering System == 1. Overview == The '''Rendering System''' in ACT 3 is responsible for turning creative assets — scripts, shot definitions, set configurations, and character cues — into fully realized visual outputs. This system supports automated, high-quality video rendering using cloud-based infrastructure and AI-assisted processes. == 2. Key Components == === 2.1 Scene Compilation === * '''F...")
 
No edit summary
Line 1: Line 1:
= Rendering System =
= Rendering System =


'''Topic:''' Rendering_System  
== Overview ==
'''Title:''' Rendering System
The '''[[Rendering_System|Rendering System]]''' in [[ACT3AI|ACT 3 AI]] powers the transformation of [[Scripts|scripts]], [[Scenes|scenes]], and [[Digital_Actors|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|WAN AI]], delivering both quick previews and production-quality outputs.


== 1. Overview ==
== Key Components ==
The '''Rendering System''' in ACT 3 is responsible for turning creative assets — scripts, shot definitions, set configurations, and character cues — into fully realized visual outputs. This system supports automated, high-quality video rendering using cloud-based infrastructure and AI-assisted processes.
* '''Rendering Engines:''' Specialized AI models for different visual styles. 
* '''Resolution & Quality Settings:''' Draft, Medium, High, Ultra/4K. 
* '''Credit Usage:''' Each render consumes [[Credit_System|credits]] depending on resolution, duration, and model used.
* '''[[Render_Queue|Render Queue]]:''' Manages all rendering jobs. 
* '''Preview vs Final Renders:''' Quick low-res iterations before committing to final exports.


== 2. Key Components ==
== Supported Engines ==
* [[Google_Veo_3|Google Veo 3 Integration]] – photorealistic cinematic output. 
* [[Runway|Runway Integration]] – stylized and experimental visuals. 
* [[Wan|WAN AI Integration]] – low-latency collaborative previews. 
* [[Stable_Diffusion|Stable Diffusion XL / Flux]] – creative generation (experimental). 
* [[ComfyUI|Comfy UI Integration]] – advanced node-based rendering for technical users. 


=== 2.1 Scene Compilation ===
== Render Workflow ==
* '''Function:''' Aggregates all data from the Set, Camera, Characters, Lighting, and VFX sections of the Shot YAML.
# Prepare [[Scenes|scenes]] and [[Shots|shots]] in the [[Editor|Editor]].
* '''Purpose:''' Ensures all inputs are validated and complete before rendering.
# Select **Render → Add to [[Render_Queue|Queue]]**. 
# Choose settings:
## Resolution (Draft, 720p, 1080p, 4K). 
## Quality (low-cost draft → cinematic). 
## Engine (Google Veo 3, Runway, WAN AI, etc.). 
# Confirm estimated [[Credit_System|credit cost]]. 
# Render job runs in the [[Render_Queue|Render Queue]] until complete.
# Download output or send to [[Build_Video|Build Video]] / [[Export_Distribution|Export Distribution]].


=== 2.2 Frame Rendering Engine ===
== Resolution & Credits ==
* '''Function:''' Converts compiled scenes into image frames.
* '''Technology:''' Utilizes cloud GPU services and AI video models (like Veo 3) for photorealistic generation.
* '''Output:''' Raw frames in .png or .jpg format.
 
=== 2.3 Video Stitcher ===
* '''Function:''' Combines rendered frames into a seamless video sequence.
* '''Features:''' Frame transition smoothing, background audio sync, title and credits overlays.
 
=== 2.4 Post-Processing Module ===
* '''Function:''' Enhances visual output through filters, grading, and corrections.
* '''Customizations:''' LUTs, color grading profiles, camera shake simulation, focus/blur depth adjustments.
 
== 3. Workflow ==
# User defines a project and configures shots using the ACT 3 interface.
# System compiles all assets into a rendering-ready format.
# Rendering engine executes shot-by-shot frame generation.
# Frames are stitched and processed into final video.
# Output is stored in user-accessible media library or cloud bucket.
 
== 4. Features ==
* Automated Frame Rendering based on AI-driven interpretation of YAML prompt structure
* Cloud-Based Infrastructure for scalable processing
* Multi-shot Support with transition and timing control
* Custom Post-FX including mood filters, VFX overlays, and lens effects
* Model Integration: Supports tools like Google Veo 3 or Runway ML
 
== 5. Performance Considerations ==
{| class="wikitable"
{| class="wikitable"
! Aspect !! Strategy
! Resolution
! Preview (per 10s)
! Final Render (per 10s)
|-
|-
| GPU Optimization || Uses parallel GPU pipelines for multi-shot tasks
| Draft (low-res)
| 1 credit
| N/A
|-
|-
| Render Failures || Includes intelligent retry and fallback mechanisms
| 720p
| 2 credits
| 4 credits
|-
|-
| Output Resolution || Renders up to 4K with optional aspect ratio control
| 1080p
| 2 credits
| 5 credits
|-
|-
| Credit Cost || Billed per frame or per second of video output
| 4K
| 4 credits
| 10 credits
|}
|}


== 6. API Integration ==
== Preview vs Final Rendering ==
* '''POST /render/start''' — Starts rendering job  
* '''Previews:''' Fast, low-cost, lower resolution, used for timing and rough visualization.  
* '''GET /render/status/:id''' — Returns status of a render job  
* '''Final Renders:''' High resolution, polished visuals, suitable for distribution. 
* '''GET /render/download/:id''' — Provides video download URL  
* Strategy: Use draft previews frequently; only commit to final renders once locked. 
* '''POST /render/cancel/:id''' — Cancels an in-progress job
 
== Best Practices ==
* Always generate draft previews before 4K outputs to save credits. 
* Use [[Wan|WAN AI]] sessions for brainstorming and collaborative testing. 
* Group jobs into the [[Render_Queue|Render Queue]] overnight to avoid bottlenecks. 
* Keep track of [[Credit_System|credit usage]] in the dashboard. 
 
== Troubleshooting ==
* '''Job not rendering''' → Check [[Render_Queue|queue status]] and [[Credit_System|credit balance]]. 
* '''Output looks inconsistent''' → Verify prompts and locked [[Characters|character profiles]].  
* '''Slow rendering''' → Reduce resolution or batch at off-peak times.  
* '''Missing assets''' → Ensure [[Import_BRoll|B-Roll]] or [[Audio_Tracks|audio files]] are attached. 
 
== See Also ==
* [[Render_Queue|Render Queue]] 
* [[Google_Veo_3|Google Veo 3 Integration]] 
* [[Runway|Runway Integration]] 
* [[Wan|WAN AI Integration]] 
* [[Credit_System|Credit System]] 
* [[Billing_Model|Billing Model]] 
* [[Build_Video|Build Video]] 
* [[Export_Distribution|Export Distribution]]
 
[[Category:ACT 3 AI Features]] 
[[Category:Reference]]
 
[https://act3ai.com/contact Contact Us] if you have questions about rendering or engine performance.

Revision as of 08:29, 27 August 2025

Rendering System

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.

Retrieved from "https://wiki.act3ai.com/index.php?title=Rendering_System&oldid=623"