Render Queue: Difference between revisions

From ACT3ai MediaWiki
Jump to navigation Jump to search
(Created page with "= Render Queue = == Overview == The Render Queue in ACT 3 AI is a cloud-based pipeline that manages, schedules, and executes the rendering of AI-generated video content. It ensures efficient distribution of compute resources across tasks, tracks job progress, and aligns with user subscription and credit models. == 1. Purpose == * Serve as the central pipeline for rendering all video assets * Prioritize tasks based on plan tier, complexity, and dependencies * Track prog...")
 
No edit summary
Line 1: Line 1:
= Render Queue =
== Overview ==
== Overview ==
The Render Queue in ACT 3 AI is a cloud-based pipeline that manages, schedules, and executes the rendering of AI-generated video content. It ensures efficient distribution of compute resources across tasks, tracks job progress, and aligns with user subscription and credit models.
The '''[[Render_Queue|Render Queue]]''' in [[ACT3AI|ACT 3 AI]] manages all rendering tasks — from draft previews to final 4K exports.
 
It allows you to schedule, monitor, and prioritize jobs, making rendering efficient for both solo creators and collaborative teams.
== 1. Purpose ==
* Serve as the central pipeline for rendering all video assets
* Prioritize tasks based on plan tier, complexity, and dependencies
* Track progress, failures, and resource consumption
* Support hybrid rendering between local and cloud systems


== 2. Core Components ==
== Key Functions ==
* '''Job Scheduler:''' Orders tasks based on priority, dependencies, and credits
* '''Job Scheduling:''' Queue multiple [[Scenes|scenes]], [[Shots|shots]], or full [[Build_Video|videos]] for processing. 
* '''Progress Monitor:''' Tracks job completion and notifies users
* '''Progress Tracking:''' Monitor render status, estimated time, and credit usage. 
* '''Output Manager:''' Stores rendered outputs with metadata
* '''Batch Processing:''' Render overnight or in parallel to save time. 
* '''Credit Meter:''' Deducts credits based on quality level and duration
* '''Prioritization:''' Reorder or pause jobs depending on urgency. 
* '''Collaboration:''' Team members can submit renders, with visibility across the organization. 


== 3. Job Types ==
== How to Use ==
* Script-to-Storyboard
# From the [[Editor|Editor workspace]] or [[Build_Video|Build Video]] page, select **Render → Add to Queue**
* Scene and Shot Rendering
# Choose render settings (resolution, quality, engine). 
* Motion Capture Integration
# Confirm estimated [[Credit_System|credit cost]]. 
* Final Export: 4K, ProRes, MP4, DCP
# Submit the job — it appears in the Render Queue dashboard. 
# Track progress in real time, cancel or reprioritize if needed. 


== 4. Quality Tiers ==
== Render Settings ==
* Q1 – Preview Quality: Fast, low-res, watermark included
* '''Resolution:''' Draft, 720p, 1080p, 4K 
* Q2 Standard Quality: 1080p, full audio/scene consistency
* '''Engines:'''
* Q3 Premium Quality: 4K, cinematic lighting, no watermark
** [[Google_Veo_3|Google Veo 3]] – cinematic realism 
** [[Runway|Runway Integration]] stylized/experimental 
** [[Wan|WAN AI Integration]] collaborative previews 
* '''Quality Levels:''' Draft (low-cost), Medium, High, Ultra (4K
* '''Output Formats:''' MP4, MOV/ProRes, WebM 


== 5. Intelligent Prioritization ==
== Managing the Queue ==
* Higher-tier plans receive queue priority
* Drag jobs to reprioritize. 
* Render jobs sorted by:
* Pause, resume, or cancel active tasks. 
  * Subscription tier
* View per-job credit usage and resolution.
  * Job type (blocking vs. non-blocking)
* Completed jobs are saved for download in [[Export_Distribution|Export Distribution]]. 
  * Deadline proximity
  * Batch size


== 6. Hybrid Rendering Model ==
== Credits & Billing ==
* '''ACT 3 Cloud:''' GPU-enabled, scalable render nodes
* Each job consumes credits based on resolution, engine, and duration (see [[Billing_Model|Billing Model]]). 
* '''Local Sync App:''' Optional desktop tool for rendering lighter jobs locally
* Draft previews are low-cost; 4K exports consume more. 
* Automatically offloads jobs to the cloud when local resources are idle or insufficient
* Admins in [[Organization_Management|Organization accounts]] can view usage by user/project. 


== 7. Render Status Tracking ==
== Troubleshooting ==
* Real-time job dashboard
* '''Job stuck in queue''' → Try canceling and re-queuing. 
* Indicators: Queued ▸ Rendering ▸ Complete ▸ Failed
* '''Credits insufficient''' → Top up via [[Subscription_Plan|Subscription Plan]]. 
* Hover tooltips show:
* '''Output missing audio/video''' → Recheck [[Build_Video|project assembly]] settings. 
  * Estimated time remaining
* '''Slow rendering''' → Heavy loads may delay jobs; schedule overnight or lower resolution. 
  * Credit cost
  * Task breakdown


== 8. Notifications & Alerts ==
== Best Practices ==
* In-app toast notifications on job completion
* Use draft previews first to validate timing before high-res renders. 
* Email summaries for batch render jobs
* Batch similar jobs together to save time. 
* Warnings for failed renders, credit shortfalls, or expired assets
* Keep the queue organized by project or client. 
* Schedule overnight to avoid bottlenecks during active work hours. 


== 9. Credit Usage Logic ==
== See Also ==
* Credits deducted per job based on:
* [[Build_Video|Build Video]] 
  * Resolution
* [[Export_Distribution|Export Distribution]] 
  * Runtime
* [[Google_Veo_3|Google Veo 3 Integration]] 
  * Additional features (e.g., voice sync, lighting complexity)
* [[Runway|Runway Integration]] 
* One-click “Calculate” button shows projected credit cost before rendering
* [[Wan|WAN AI Integration]] 
* [[Credit_System|Credit System]] 
* [[Billing_Model|Billing Model]] 


== 10. Output Management ==
[[Category:ACT 3 AI Features]] 
* Files auto-organized by Project → Scene → Shot
[[Category:Guides]]
* Render outputs downloadable in multiple formats:
  * .mp4, .mov, .jpg (frames), .fbx, .json
* Storage quota tracked per plan tier


== 11. Roadmap ==
[https://act3ai.com/contact Contact Us] if you need support with rendering or queue management.
* Pausable and resumable render tasks
* Scene-level dependency detection (render in correct order)
* Render token marketplace (buy/sell compute credits)
* Regional rendering zones for faster output

Revision as of 08:26, 27 August 2025

Overview

The Render Queue in ACT 3 AI manages all rendering tasks — from draft previews to final 4K exports. It allows you to schedule, monitor, and prioritize jobs, making rendering efficient for both solo creators and collaborative teams.

Key Functions

  • Job Scheduling: Queue multiple scenes, shots, or full videos for processing.
  • Progress Tracking: Monitor render status, estimated time, and credit usage.
  • Batch Processing: Render overnight or in parallel to save time.
  • Prioritization: Reorder or pause jobs depending on urgency.
  • Collaboration: Team members can submit renders, with visibility across the organization.

How to Use

  1. From the Editor workspace or Build Video page, select **Render → Add to Queue**.
  2. Choose render settings (resolution, quality, engine).
  3. Confirm estimated credit cost.
  4. Submit the job — it appears in the Render Queue dashboard.
  5. Track progress in real time, cancel or reprioritize if needed.

Render Settings

  • Resolution: Draft, 720p, 1080p, 4K
  • Engines:
  • Quality Levels: Draft (low-cost), Medium, High, Ultra (4K)
  • Output Formats: MP4, MOV/ProRes, WebM

Managing the Queue

  • Drag jobs to reprioritize.
  • Pause, resume, or cancel active tasks.
  • View per-job credit usage and resolution.
  • Completed jobs are saved for download in Export Distribution.

Credits & Billing

  • Each job consumes credits based on resolution, engine, and duration (see Billing Model).
  • Draft previews are low-cost; 4K exports consume more.
  • Admins in Organization accounts can view usage by user/project.

Troubleshooting

  • Job stuck in queue → Try canceling and re-queuing.
  • Credits insufficient → Top up via Subscription Plan.
  • Output missing audio/video → Recheck project assembly settings.
  • Slow rendering → Heavy loads may delay jobs; schedule overnight or lower resolution.

Best Practices

  • Use draft previews first to validate timing before high-res renders.
  • Batch similar jobs together to save time.
  • Keep the queue organized by project or client.
  • Schedule overnight to avoid bottlenecks during active work hours.

See Also

Contact Us if you need support with rendering or queue management.