SCANNY
1.1.0 beta 7
1.1.0 beta 7SHOWDATE04 OCT 2026CHANGES18BETA
SETUP PUSH is one simple window: drop a .stp file with any name, tick where it goes and whether it loads, and LOAD on any off-air camera with every guard kept. The button says what will happen, a camera one cut from air reads PVW, and a file type not seen from a camera here asks once before it loads. On the ALEXA page the LAN link respects the RCP hold, and the one-fine-step move is for paint rows only.
SAFETY 07
The LAN link respects the RCP hold
Settings and IRIS OPEN / CLOSE sent over the LAN link now check the RCP hold, as the camera link does, and so does a value waiting in the queue. While an RCP holds paint, a paint setting or IRIS sends nothing and reads Held by RCP. Other settings still go.
One fine step on paint rows only
The one-fine-step move with no known range is for paint faders and trims only. Other rows with no known range, such as genlock shift, pre-record duration, look intensity and filter sharpness, read RANGE ? and stay read-only. Master black and the RGB trims still move one fine step.
PVW on the camera list
A camera one cut from air now reads PVW in amber on the camera list, not OFF AIR. LOAD skips it; INSTALL still goes.
LOAD checks the camera model
When a file names a camera model, LOAD runs only on cameras of that model; the others install only and say so. A file that names no model asks once: No camera model found in this file — load anyway?
Same name in another case
A setup on the camera whose name differs only in upper and lower case counts as already there. Nothing is written over it unless you tick Replace.
RCP hold before the serial is read
The LAN link's RCP hold also covers a camera whose serial has not been read yet, using the serial Scanny expects, as the camera link does.
A new file type asks before LOAD
A file whose first bytes match no file got from a camera here reads new file type in the library. LOAD asks once: This file's format wasn't seen from a camera here — load anyway? INSTALL is unchanged. A 3D CAD file that also ends in .stp is refused: A 3D CAD file, not a camera setup.
NEW 01
SETUP PUSH: drop a file and it imports
Drop .stp files on the SETUP PUSH window, or click to choose. Any file name imports: Scanny keeps letters, digits, _ and -, turns every other character into -, and keeps the name within 32 characters. SHOW_3.8K_59.94.STP is saved as SHOW_3-8K_59-94, and one line says so. A different file with the same name gets -2, -3 and so on; the same file dropped again is the one already in the library. The size, .stp and file checks are unchanged.
IMPROVED 07
Rename, delete and get from a camera in the library
Click a file to pick it. Double-click to rename it: the same name fix applies and a rename is never refused. Return saves, Esc cancels. The x or a right-click moves a file to the Trash after a confirm. Get from camera is one row: pick the camera and the file, then GET.
Tick boxes for where it goes and if it loads
Camera body (on by default), USB stick in the camera, Load it after install, Replace a file with the same name, and Include on-air cameras (store only, never load). The USB box is greyed out with Store on USB from the camera menu: Scanny stores setups on the camera's internal storage. The INSTALL ONLY / INSTALL LOAD switch and the test-spare lines are gone.
LOAD on any off-air camera
With Load it after install ticked, Scanny loads the setup on any off-air camera, no test spare needed. Every LOAD guard stays: on air, tally unknown, REC, PRE-REC and preview refuse it; Scanny saves a backup on the camera and copies it to the Mac first; cameras load one at a time and stop at the first failure; you type the camera names to confirm; the active setup is read back after; UNDO loads the backup. A camera that refuses shows its answer, for example NoSuchFile: not loaded, the backup stays.
One camera list and one button
ALL / NONE, then one line per camera with OFF AIR, ON AIR or NO LINK. The plan shows on each line before the run and the result after it ( STORED · LOADED · × reason), with UNDO on the lines that loaded. One button: INSTALL ON 3 CAMERAS. The window fits a 1080 × 680 screen.
The button says what will happen
The SETUP PUSH button names the job: INSTALL ON 3 CAMERAS, INSTALL LOAD ON 3 CAMERAS, or INSTALL ON 3 · LOAD ON 1 when only some cameras can load.
Drop anywhere, click a line to tick
Drop a file anywhere on the window. Click a camera line to tick it. Typed confirms sit in the footer, one at a time, so the library and tick boxes never move. Esc while renaming only cancels the rename. The footer says the next step, for example Saved as SHOW_A · Tick a camera.
Plain results on each camera line
After a run each camera line says what happened in plain words. A camera that installed but did not load says why, for example STORED · not loaded: made on ALEXA LF, camera is ALEXA 35.
FIXED 03
CALL and typed faders
RCP CALL no longer counts as checked the first time you press it. A fader offers typing only with a known range, like the RGB trims and the PAINT strip.
COPY over the LAN link logs as COPY
A COPY or undo sent over the LAN link is now logged as a COPY, not as a press on the page.
Get setup from this camera
The Wall right-click item now reads Get setup from this camera…, like GET in the window. A drop with no file says No file in that drop. Drop the .stp from Finder, or click to choose it. The file menu reads no files when the camera has no link, never reading… for ever. A rename that only changes upper and lower case keeps the file in the library even if it fails.