Pixel-Map Capacity

Calculate pixel-map canvas size and control-universe capacity.

Description

A pixel-map canvas describes image size, while control-channel demand follows fixture count and channel footprint.

A pixel-map canvas describes image size, while control-channel demand follows fixture count and channel footprint. Those two capacities need not be one-to-one.^[1]

Calculate pixel-map canvas size and control-universe capacity.

When to use Pixel-Map Capacity

Use this tool to calculate pixel-map canvas size and control-universe capacity.

Prepare production measurements or checklist records for one planning period. Confirm units, staffing assumptions and caller-selected criteria before running the calculation.

How to use Pixel-Map Capacity and understand its results

Prepare production measurements or checklist records for one planning period. Confirm units, staffing assumptions and caller-selected criteria before running the calculation.
Enter canvasWidthPixels, canvasHeightPixels, fixtureCount, channelsPerFixture, universeCapacityChannels using the field table and calculation rules, then run the tool.
Read pixelCount, requiredChannels, requiredUniverses. The explanation below defines the units, signs, ordering and any flags or placeholder values.
If the tool reports an input issue, correct the values and run it again. Apply the stated assumptions when interpreting a successfully returned result.

Input field	Meaning	Value type; see rules below	Requirement
canvasWidthPixels	Canvas width (px)	integer; minimum: 1	Required
canvasHeightPixels	Canvas height (px)	integer; minimum: 1	Required
fixtureCount	Mapped fixture count	integer; minimum: 0	Required
channelsPerFixture	Channels per fixture	integer; minimum: 1	Required
universeCapacityChannels	Channels per universe	integer; minimum: 1	Required

Enter positive integer canvas dimensions, channel footprint/capacity and nonnegative integer fixtures. Return pixel count, total channels and upward-rounded universe count. Zero fixtures require zero universes even with a nonempty canvas.

pixels=width×height; channels=fixtures×channelsPerFixture; universes=ceil(channels/capacity)

Units, indexing, boundary conditions and exceptional cases are defined in the calculation rules above.

Output field	Meaning	Value type
pixelCount	Canvas pixel count	integer; minimum: 1
requiredChannels	Required output channels	integer; minimum: 0
requiredUniverses	Required universes	integer; minimum: 0

json

{
  "input": {
    "canvasWidthPixels": 1920,
    "canvasHeightPixels": 1080,
    "fixtureCount": 100,
    "channelsPerFixture": 4,
    "universeCapacityChannels": 512
  },
  "output": {
    "pixelCount": 2073600,
    "requiredChannels": 400,
    "requiredUniverses": 1
  }
}

Limitations and assumptions

This aggregate count does not pack fixtures across universe boundaries or verify protocol addressing. Canvas pixels do not determine channel count automatically.

Numeric inputs must be finite. Follow the calculation-specific rules for overflow, underflow and exceptional cases. Missing required fields, extra fields, wrong value types and violations of the calculation rules are input errors.

Alternative or Complementary methods

Use Edge-Blend Overlap: Calculate overlap pixels and total blended width for a horizontal projector row. For a complementary task, use Show-Control Trigger Coverage: Audit show-control trigger mappings.

References

Pixel-Map Capacity — tool.io

Similar or alternative tools

Edge-Blend Overlap
Calculate overlap pixels and total blended width for a horizontal projector row.
Show-Control Trigger Coverage
Audit show-control trigger mappings.