Skip to content

Architecture Overview

ziviDomeLive 2.0 organizes rendering into two domains that can be required independently or in the same Processing frame. This separation is the central architectural fact behind routing and reuse.

flowchart LR
  S[Updated Scene state] --> SD[Standard domain]
  S --> CD[Spherical cubemap capture]
  SD --> ST[Standard final view]
  CD --> DM[Domemaster]
  CD --> EQ[Equirectangular]
  CD --> SB[Skybox]
  ST --> C[Preview / outputs]
  DM --> C
  EQ --> C
  SB --> C
  • Standard Domain

    Scene → Standard renderer → Standard final target. No spherical cubemap is required for Standard-only work.

    Standard Domain →

  • Spherical Domain

    Scene → internal cubemap capture → Domemaster / Equirectangular / Skybox.

    Spherical Domain →

Capture once, project many, consume many

The cubemap is the shared spherical capture. Requested spherical projections should reuse it whenever the frame requirements permit. Preview and output consumers receive final views; they should not force duplicate scene capture merely because several consumers request the same domain.

Architecture is not a prerequisite for creative use

Artists can remain at the Scene, RenderMode, ViewType, camera and calibration level. This section exists for contributors, developers and researchers who need the engine contracts.

Continue through the engine

  • Rendering Pipeline — requirement resolution and final-view reuse. Open →
  • OpenGL Backend — Processing/OpenGL boundary and resource behavior. Open →
  • Lifecycle — ownership, invalidation and shutdown. Open →
  • Output Backends — NDI/Syphon/Spout internal boundaries. Open →