- run/relaunch_x265.sh: start ONLY the x265 tier. run/relaunch_tiers.sh hardcodes
`for t in x265 nvenc`, and the nvenc tier must not start while another job owns the
GPU (the TubeSync 58-file repair batch holds it since 2026-10-09 20:36). x265 is
pinned to the E-cores, so it shares only the RaiDrive mount -- 2 concurrent share
jobs is the documented safe limit.
- The launcher redirects its own banners into the log (under -WindowStyle Hidden,
stdout goes nowhere) and documents the -ArgumentList form: the script path alone.
- STATE.md: LastBootUpTime 2026-10-09 16:51:58 -- both tiers stopped by a REBOOT, not a
bug (x265 404/589, nvenc 308/589); the stale lock pids need no cleanup because
transcode.Lock is staleness-aware. Memory after reboot: 13 GB free / 50.3 of 55.9 GB
committed, but the commit limit fell from 79.6 GB because D: is 92% full.
The x265/nvenc tiers launched as Hermes background processes were killed
mid-encode at 10:37 when the user's session was closed, so persist_on_release
is not enough here: run/relaunch_tiers.sh starts them orphaned from Hermes
(Start-Process) with a retry loop, which is why they are no longer tracked and
must be stopped by PID only.
STATE.md now carries the progress table (242/589 done, 347 pending: 169 x265 +
174 nvenc + 4 copy), the reason a full `--tier copy` pass must NOT be run (its
only skip test is "already HEVC", which a copy output never satisfies - it
would redo all 193), and the four new weekly episodes handled one file at a
time.
hoelee