Skip to content

CalibrationTool

CalibrationTool is the current visual qualification instrument for ziviDomeLive. It is not a learning example and it is not a substitute for the historical 1.5 protocol. Use it to inspect spherical orientation, projection mapping, focus, color, calibration controls and output behavior on the actual target system.

Capture must be evidence

A final image for this page must be captured from the installed, qualified 2.0 package and record the active scene, ViewType, resolution and calibration state. No editorial mockup is accepted as qualification evidence.

The tool starts on Paul Bourke Environment Background in DOMEMASTER with FOV 210°, Size 100%, and global pitch/yaw/roll at . A fixed 90° rotation around X is applied directly to the Environment source lookup, keeping image alignment independent from dome orientation and scene geometry. The 0 key restores this exact startup state.

Cube Focus and Color

Six GLSL 4.10 targets form a closed cube around the observer. Each face uses explicit local 0..1 coordinates so grids, geometric references, focus features, color ramps and annotations form one continuous spherical calibration surface.

The scene contains:

  • 24 × 24 grid with quarter divisions and face boundaries;
  • safe-area rectangles, concentric circles, radial spokes and center crosshairs;
  • 1, 2, 4 and 8 pixel line pairs;
  • 1, 2, 3 and 4 pixel points, starbursts and a deterministic star field;
  • RGB/CMY/white/black references;
  • continuous grayscale, discrete levels and near-black/near-white clipping patches;
  • face index, axis, direction, grid coordinates, UP and R orientation markers.

Pixel-sized features are exact only when a cubemap face is sampled one to one. Their degradation through another projection, resolution, codec or receiver is part of what the tool is intended to reveal.

Initial scene — Paul Bourke Environment Background

The initial scene supplies one of four original, unmodified Paul Bourke v14 equirectangular test patterns through SceneEnvironmentService. The library-owned far-depth pass is translation-invariant, composes the source-image alignment independently from the shared spherical orientation, and follows the same source in Standard, Domemaster, Equirectangular, and Skybox views.

The source follows the active output-resolution bucket when an external output is enabled. With outputs disabled, the nearest bucket is selected from the Processing window.

Render bucket Source used by the example
1024 (1k) spherical2400.png (2400 × 1200)
2048 (2k) spherical4096.png (4096 × 2048)
3072 (3k) spherical4800.png (4800 × 2400)
4096 (4k) spherical8192.png (8192 × 4096)

The Paul Bourke scene also provides a slow, time-quantized rotation for observing aliasing and playback discontinuity:

  • Space: toggle one revolution per 60 seconds;
  • T: switch between 30 fps / 1800 positions and 60 fps / 3600 positions;
  • , / .: step backward / forward by one degree and pause;
  • C: restore source orientation and pause;
  • V: toggle Environment visibility;
  • D / B: decrease / increase Environment intensity.

The rotation profile does not change Processing's global frame rate.

Shared controls

Use Left/Right arrows to switch scenes.

Control Effect
1 Domemaster ViewType
2 Equirectangular ViewType
3 Skybox ViewType
4 Standard ViewType
[ / ] Decrease / increase Domemaster Size% by 10
- / + Decrease / increase FOV by 10°
P Add 90° pitch
Y Add 90° yaw
R Add 90° roll
F Toggle floating Domemaster preview
0 Restore the startup projection state

The example starts in RenderMode.FULL. View selection therefore exercises the same independent Preview/Output routing model documented for normal projects.

  1. Start on the Paul Bourke Environment Background in the startup/reset state (0).
  2. Switch to Cube Focus and Color and inspect it in Domemaster, Equirectangular, Skybox and Standard.
  3. Apply P, Y and R independently and verify continuous orientation across the spherical projections.
  4. In Domemaster, vary FOV and Size% and confirm that they solve angular coverage and physical image fitting rather than Scene camera movement.
  5. Toggle the floating preview and confirm it does not redefine external-output resolution.
  6. Return to the Paul Bourke scene and inspect poles, equator, longitude continuity, translation invariance, visibility/intensity controls and the slow rotation profile.
  7. Repeat on every GPU/platform/output configuration that will be claimed as tested for the release.
  8. Record screenshots and receiver evidence from the actual installed package or qualified checkout.

Visual inspection is hardware evidence

Source compatibility is not proof that a GPU, driver, projector, lens or receiver chain is qualified. Record the exact environment used for every release claim.

Current protocol vs. historical protocol

This page is the current CalibrationTool protocol. The preserved 1.5 Calibration Tool and Compatibility Baseline documents the historical 1.5 qualification state and should remain unchanged except for factual errata explicitly identified as historical corrections.