Render Options Reference

The renderOptions field on a render job request controls how the render pipeline executes. These options affect performance and parallelism — they do not affect the visual output quality.

{
  "kind": "movie",
  "projectId": "proj_abc123",
  "movie": { ... },
  "renderOptions": {
    "qualityPreset": "fast",
    "requestedConcurrency": 4
  }
}

---

qualityPreset

Type: "stable" | "balanced" | "fast" | "turbo"
Default: "balanced"

Controls how many scene workers run in parallel. Despite the name, this does not affect visual quality — it only controls the parallelism strategy.

Preset	Parallel scenes	Typical use case
stable	2	Debugging; when you want predictable, sequential-ish behavior
balanced	3	General purpose — most videos (default)
fast	4	Short videos with 4–8 scenes
turbo	6	Long videos on Business or Enterprise plans

Example:

"renderOptions": { "qualityPreset": "turbo" }

For a 12-scene video on turbo:

• Rounds 1 and 2 each render 6 scenes in parallel
• Wall-clock time ≈ 2 × (average single-scene render time) + assemble time

---

requestedConcurrency

Type: integer
Range: 1–32
Default: derived from qualityPreset

Override the parallelism with an exact number of scene workers.

Actual concurrency = min(requestedConcurrency, sceneCount)

If you have 3 scenes and set requestedConcurrency: 10, only 3 workers run (one per scene).

"renderOptions": { "requestedConcurrency": 5 }

Use this when you know exactly how many parallel workers you want, regardless of the preset mapping.

---

Omitting renderOptions

If renderOptions is omitted entirely, ViralSync uses qualityPreset: "balanced" (3 parallel workers). This is suitable for most use cases.

{
  "kind": "movie",
  "projectId": "proj_abc123",
  "movie": { ... }
  // renderOptions omitted → balanced (3 workers)
}

---

Choosing the right preset

Scenario	Recommended
Single-scene video	Any preset — parallelism has no effect
2–4 scenes, fast turnaround	fast
5–10 scenes, standard production	balanced
10+ scenes, Business plan	turbo
Debugging a render failure	stable
Exact worker count needed	requestedConcurrency

---

Effect on render minutes

Quality presets and requestedConcurrency do not affect how many render minutes are consumed. Render minutes are measured by output video duration, not by worker count or compute time.

A 10-scene, 60-second video consumes 1.0 render minute regardless of whether you use stable (slower) or turbo (faster).

See Render Minutes →