aboutsummaryrefslogtreecommitdiffstats
path: root/docs
diff options
context:
space:
mode:
Diffstat (limited to 'docs')
-rw-r--r--docs/MESHBAY_DESIGN.md7
-rw-r--r--docs/USERGUIDE.md4
2 files changed, 10 insertions, 1 deletions
diff --git a/docs/MESHBAY_DESIGN.md b/docs/MESHBAY_DESIGN.md
index 2419916..eec354a 100644
--- a/docs/MESHBAY_DESIGN.md
+++ b/docs/MESHBAY_DESIGN.md
@@ -3352,6 +3352,13 @@ any LAN renderer can play; the relay is device-agnostic. Chromecast discovery an
control ship. DLNA/UPnP is designed and not built: it is a second device backend
beside the first, not a second relay.
+**Discovery lists receivers as they answer.** The mDNS scan runs six seconds,
+because a receiver coming back from a reset can take that long, but most answer
+within two. The main process holds what the scan has found and the page polls it
+(`cast:scan`, then `cast:devices`) for as long as the picker is open, rather than
+waiting on one call for the whole scan; a poll uses the same checked `handle()`
+door as every other call, where a pushed event would be a second one.
+
**Subtitles are rebased onto the relay's clock before they are sent.** The node
extracts a track whole, so its cues carry the film's timeline, and the player
can use them unchanged because its SourceBuffer is given `timestampOffset =
diff --git a/docs/USERGUIDE.md b/docs/USERGUIDE.md
index e92f6bc..e85b260 100644
--- a/docs/USERGUIDE.md
+++ b/docs/USERGUIDE.md
@@ -394,7 +394,9 @@ resume.
**Desktop application only.** A film playing in the application can be sent to a
cast-capable TV or dongle on the same network: *Cast to device* in the player,
-pick one from the list.
+pick one from the list. Devices appear as they answer, usually within a couple
+of seconds; the search carries on for a few more, for a TV that is still
+waking up.
The application decrypts the film and relays it to the TV itself, over your LAN.
The TV is not a group member and holds no key — which is also why the relay's