GEN-B Engineering Article

When iOS Doesn't Give You EDID, You Build with Geometry

GEN-B SWEEP is a geometry-driven autonomous reference layer for understanding how a generated signal is presented on an external display path. It works within the information iOS makes available, using known source geometry and output metrics instead of raw EDID.

SWEEP is not an EDID reader. It is a geometry-driven reference layer built within the boundaries of what an iOS app is allowed to render and calculate.

Professional display testing usually starts with a simple question: what signal did we generate, and what did the display path do with it? On a desktop engineering bench, the answer might involve EDID, DDC, direct hardware interfaces, and external measurement tools. On iOS, the app lives inside a much more controlled environment.

That constraint shapes the design. GEN-B does not claim to read raw EDID, bypass platform security, or inspect emitted display pixels. Instead, SWEEP treats the problem as geometry. If the app knows the generated signal dimensions and has access to available output metrics, it can build a repeatable reference model around active area, aspect relationship, matte regions, and raster utilization.

Autonomous Reference Layer

A moving reference that is separate from the source.

SWEEP is implemented as a controlled overlay, not as a mutation of the test pattern or video. The selected reference source remains the signal under test. The RasterScope box travels independently above it, giving the user a visible reference object whose position is derived from time and output geometry.

This keeps the workflow practical: the app can display a generated pattern or reference clip while the autonomous layer traverses the same output area. The moving box becomes a repeatable visual reference for display behavior, active boundaries, scaling, and matte conditions.

Public-safe Swift excerpt from GEN-B: time and output geometry drive the autonomous SWEEP overlay. Internal constants and proprietary analysis logic are intentionally omitted.

Why the traversal is deliberately simple.

A reliable engineering reference does not need theatrical motion. It needs predictable motion. SWEEP uses normalized movement that can be scaled to the available output rectangle. The box travels forward, reflects, and travels back, which keeps it inside the calculated boundaries without requiring object tracking inside the video.

The mathematical heart of the traversal is intentionally small: a normalized 0→1→0 curve that can be scaled to any output geometry.

The important idea is not animation for its own sake. The important idea is that time becomes a deterministic input, geometry defines the allowed travel area, and the reference layer stays independent from whatever pattern or video is currently selected.

When 16:9 is not the standard, SWEEP treats the raster as geometry — not as an assumption.

Raster Geometry

Non-16:9 workflows need measurements, not assumptions.

Broadcast and display workflows do not always behave like a clean 16:9 diagram. External displays may report ultrawide dimensions, adapters may negotiate different modes, and signal paths can introduce aspect adaptation. SWEEP approaches that condition by comparing the known generated source raster with the available display geometry.

From that comparison, GEN-B can describe the active sweep area, side matte regions, edge reach, and utilization in engineering language. It is not reading raw EDID. It is using the metrics available to the app and the known signal geometry that GEN-B generates.

Turning source and display metrics into useful feedback.

The mapping layer starts with two pieces of public-safe information: the generated source raster and the display/output size reported to the app. The source is fit into the display geometry, and the resulting rectangle becomes the basis for active area, pillarbox or matte estimates, coverage, and aspect relationship feedback.

Public-safe Swift excerpt from the geometry mapping layer: source raster and display geometry become active area, matte regions and utilization.

That is the core of SWEEP's engineering posture: use known signal geometry, respect the platform boundary, and present the result clearly enough for a field engineer to make a better decision at the display, converter, or signal path.

Technical Note

This article describes SWEEP as a geometry-driven engineering reference layer. It should not be interpreted as a claim that GEN-B reads raw EDID, bypasses iOS security boundaries, captures emitted display pixels, or performs object tracking inside the video.

GEN-B SWEEP

Built for practical display-path decisions.

For PBE, the engineering value is not pretending iOS exposes everything. The value is building a clear, repeatable reference layer from the geometry the app can know.