Readdress a line in one plan
When a line’s units all need new addresses or modes (units all on address 1, or a rig being repatched), set them together as one plan instead of one unit at a time. The bench checks the whole plan before it sends anything, so a clash that the fifth change would make shows before the first change goes out.
To change one unit, use Change Address and Mode… as in Wrong colors: check the patch. That stays the way to do it on the bench.
In the app, choose Fixture → Change Addresses and Modes on Line…: the plan is a grid of the line’s units, explained under “Change a line in the grid”. (macOS) / This app cannot change a whole line yet. Use the command line below, or change each unit with Change address and mode…. (Windows, Linux)
From the command line
rdmbench-cli set-line --plan plan.csv reads a CSV file with a header
line: uid, plus dmx_address and/or personality. A blank cell keeps
the unit’s value, and other columns are ignored. Those are the rig
sheet’s own column names, so rdmbench-cli scan --all --csv -o rig.csv,
edited in a spreadsheet, is a plan.
rdmbench-cli set-line --plan plan.csv --dry-run prints each change as
from → to, with anything refused, and sends nothing. Without
--dry-run, nothing is sent unless the whole plan passes. Each unit’s
result is printed as it goes, and Ctrl-C stops between units.
Two units on some of the same channels are refused. A stack is the
exception: units of the same model, in the same mode, on exactly the
same channels, which the console drives as one. A stack is printed as
STACKED so you can check it is meant, and it does not stop the plan.
rdmbench-cli set-line --plan plan.csv --put-back back.csv also writes
the plan that puts every changed unit back. rdmbench-cli set-line --plan back.csv
then restores them. If units shared channels before, putting them back
puts them on the same channels again: the overlaps are printed, and they
do not stop it.
A plan is one line: a sheet with more than one universe in it is refused.