Scrim — Support

Most questions about Scrim are versions of the same one: why won’t it just give me a number? Here are the answers.

Why does it say “I can’t measure this”?

Pointing up or down

The horizon angle is computed from the horizontal part of the gravity vector, and that part shrinks to nothing as the phone tilts toward the sky or the floor. The same sensor noise then translates into a much larger angular error: ±0.12° upright, ±3.48° at 88° of pitch. When the band grows past 3° there is no angle left to print, so Scrim stops printing one. Bring the phone back toward vertical and the number returns.

Too dark

If almost the whole frame sits below preview code 5, there is no scene to measure — only quantisation. Scrim says so instead of reporting a range built from rounding error.

Undecided

Between “level” and “tilted” the band can straddle the tolerance. Neither claim is available, so Scrim shows the third answer. Steadying the phone — a wall, a rail, a tripod — narrows the band and usually resolves it.

Why is the range written with “at least”?

Because one end is saturated. A pixel sitting at the ceiling might be one stop over or five; the preview keeps no record of the difference. The honest statement is a floor, so Scrim writes a floor. Lower the exposure until the clipping clears and the range becomes a real interval with a band.

Why does the clipping figure not come with a number of stops?

Clipping is observed — the fraction of pixels at the ceiling is a measurement. Its size is not observable from the preview. Scrim reports the first and refuses the second. Under 0.2% of pixels it does not call clipping a defect at all: at that level it is a lamp or the sun itself, and pulling exposure down for it buries the rest of the frame.

Why do I have to choose a lens for converging verticals?

Because without a field of view the convergence cannot be computed at all — it is not a refinement, it is the input. A default here would be a made-up number wearing the clothes of a measurement. Pick the option closest to the lens you are using; the assumption Scrim makes about the façade is printed next to the result.

The watch app shows “Not connected to iPhone”

The watch shows the phone’s decision; it does not measure on its own, because the light measurement needs the phone’s camera. Open Scrim on the phone, keep both devices in range, and the decision appears. If the connection drops, the watch says so rather than leaving the last decision on screen — a stale verdict on a changed frame is the one thing worse than no verdict.

Does Scrim take photos?

No. It measures the live frame and leaves capture to the system camera. It has no photo library access and stores no images.

Which devices?

iPhone and iPad on iOS 17 or later, Apple Watch on watchOS 10 or later. There is no Mac version: Scrim’s inputs are a camera preview and an accelerometer, and a Mac target would be an empty product rather than a smaller one.

Languages

English, German, Spanish, French, Japanese and Turkish.

Something is wrong, or a number looks off

Write to hello@norea.studio with what the screen said and what you expected. If a measurement is wrong, that is a defect in the core, and the core is where it will be fixed and tested.

norea.studio · Scrim · Privacy