docs: the superseded fallback answers its own session; who uses beacon()

2026-10-08 01:16:30 +02:00
parent 5095047c81
commit a504550196
2 changed files with 9 additions and 7 deletions
@@ -744,8 +744,9 @@ def start_session(
        # `replace_only` makes the supersede identity-aware for the runtime fallback: the whole
        # check-and-replace happens under ONE _lock, so a newer same-key session (a concurrent
        # seek-restart) installed between the fallback's decision and here is never clobbered. When the
-        # registered session is no longer `replace_only`, we abort and return None (the caller yields to
-        # whoever is registered now). The INITIAL spawn never gets None — see its call site.
+        # registered session is no longer `replace_only`, we abort and return None, and the caller
+        # answers with its own dead session — never the newer one, whose id a stale requester would
+        # stop. The INITIAL spawn never gets None — see its call site.
        # Software-fallback encode tuning — read only on the SW transcode path (the VAAPI path and
        # remux ignore preset/crf/max_height, and remux must not touch the DB for them).
        preset, crf, max_height = "veryfast", 20, 0