SCANNY
1.1.0 beta 6
1.1.0 beta 6SHOWDATE04 OCT 2026CHANGES15BETA
On the ALEXA page settings change straight from the page: a first change checks itself, AGAIN? sends only the change it asked about, RESET ALL and AWB respect the RCP hold, and faders with no known range still move one fine step at a time. On the RCPs tab, a value the RCP already holds now says so plainly, a confirmed DISP, LED, DIM, SLEEP or GAIN change reads saved on the RCP and read back, the rows always plan on the read the table shows, a value that goes back after a change is shown and logged, and a WENT BACK row clears on a newer read.
SAFETY 03
A first change checks itself
After a change Scanny reads the setting back from the camera. If it matches, the setting counts as checked for that camera software on every ALEXA, and stays checked after a restart. If the camera reports another value, the row shows what the camera reports and nothing else changes.
COPY waits for a first change on a page
COPY to other ALEXAs still skips a setting not yet checked on that camera software; its chip reads SET ONCE FIRST. Change it once on a camera page and COPY takes it from then on. COPY and undo never write an unchecked setting, on the camera link or the LAN link. LOCKED cameras are skipped. The test spare stays under Settings › ALEXA for diagnostics.
RESET ALL and AWB respect the RCP hold
MULTIMATRIX RESET ALL and AWB now check the RCP hold, from the page and from the queue. While an RCP holds paint they send nothing and read Held by RCP. RESET ALL no longer marks the multimatrix rows as checked.
NEW 01
WENT BACK when a changed value doesn't stay
After a confirmed change, if a later read (the regular reads, RE-READ, the read after the send or the 10 s check) finds the RCP holding another value, the row reads WENT BACK TO 3 with DISP went back to 3 after the 10:00 write, and Activity logs it once. Scanny never sends it again by itself: edit the cell to send it again.
IMPROVED 06
A change reads saved on the RCP · read back 8
A confirmed DISP, LED, DIM, SLEEP or GAIN change now reads SAVED · READ BACK 8 on the row and saved on the RCP · read back 8 in Activity. Its help says Scanny checks the value stored on the RCP, and that what the screen shows can also depend on the panel being dimmed or on the panel's own Engineering Menu brightness (Shift Panel lock).
Every ALEXA setting changes from its page
On an unlocked ALEXA the settings on the page now change when you click, step, pick or type them, with no test spare needed. Off air it is one click. On air, in preview, with tally unknown, rolling or in pre-record, a setting not yet checked on that camera software asks AGAIN? once: click the same change again within 3 s to send it. A different change, or a held key, asks again and sends nothing. ENG settings still ask for the camera name, off air only. IRIS OPEN / CLOSE and pre-record over the LAN link stay UNVERIFIED on a show camera until the test spare has checked them.
Faders with no known range still move
A paint fader or trim uses the camera's range, else the documented one. With neither it no longer sits at RANGE ?: it moves one fine step per click. Typed values, coarse steps and drags wait until a range is known; a typed value there reads Range unknown: one fine step at a time. Nothing sent. If the camera refuses a value, the row shows its answer.
No more UNVERIFIED line on the ALEXA page
The orange "n of N UNVERIFIED — shade from RCP" line is gone, and so is the STATUS-tab link to the test spare. On a base station a dim line counts the settings on the open tab that only a LAN link or the camera menu reaches, and hides at 0; they stay folded away in their section.
Type a value into RGB trims and the PAINT strip
Off air, double-click an RGB trim or the PAINT strip master or R / G / B field to type a value. With LINK on it sets R, G and B. Typing needs a known range and is never offered on air or on a LOCKED camera. The SHIFT coarse hint only shows where a coarse step is allowed.
Plainer words around first use
The AGAIN? hover reads On air: click again within 3 s to send. Settings › ALEXA, the Wall spare alert and the LIVE 1-CLICK dialog say test mode is diagnostics only. A read-only row reads Read now. Change it on the camera.
FIXED 05
ALREADY says which RCP holds the value
When you type the value an RCP already holds, the chip reads ALREADY SET, the row ALREADY 8 ON RCP and the line above the table DISP → 8 ON 1 RCP · ALREADY 8 ON RCP-14 · NOTHING TO SEND. Return no longer closes without a word: the rows and the line say RCP-14 already holds DISP 8 with the time it was read, and Activity gets one line, Nothing sent: RCP-14 already holds DISP 8. Nothing is sent.
The rows plan on the read the table shows
While you edit, the rows are planned again on the newest read of each RCP, so a cell never shows 3 beside ALREADY 8. If the two still differ, the chip and the row read READING… and Scanny reads that RCP again once (reads only) before anything can be sent.
A WENT BACK row clears on a newer read
When a newer read shows another value, for example 8 again from the web page or a sheet, the WENT BACK row goes plain and shows what the RCP holds now. Nothing is sent and nothing more is logged.
CHANGED TO when it is not the old value
The row reads WENT BACK TO 3 only when 3 was the value before the change. Otherwise it reads CHANGED TO 5, matching the line DISP changed to 5 after the 10:00 write.
Drift reads the group first
When a value moves after a change, the row shows the group's value first, every time. The panel's own value shows only when the group did not move and the panel holds its own value. An inherited value is never shown.