@torrent-tv/proxy 2.9.62 → 2.9.63

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/CHANGELOG.md CHANGED
@@ -1,3 +1,7 @@
1
+ ## 2.9.63
2
+
3
+ - **Fix**: A seek landed the encoder on exactly the requested segment, which is the one position the player never asks for — so it produced files nobody was waiting for and playback hung. Per Apple HLS authoring guidance, a player given a position locates the nearest keyframe **preceding** it, decodes from there, and only then presents from the requested point; it therefore always fetches segments **below** the target. Measured on iOS: a seek to #1082 fetched from #1074 (8 back), one to #1358 fetched from #1301 (57 back) and asked for **nothing at or above** the target. The encoder now starts `SEEK_BACKOFF_SEGMENTS` (12) before the requested segment, and — since the needed depth varies and no fixed number covers it — is pulled down further to the lowest segment the player is actually waiting on, which its own requests report exactly (`lowestAwaitedIndex`). Only ever moves the start earlier, never later. Costs a few seconds of extra encoding per seek.
4
+
1
5
  ## 2.9.62
2
6
 
3
7
  - **Fix**: The seek target is now taken **explicitly from the browser** (`POST /api/transcode-sessions/:id/seek`) instead of being inferred from which segments the player requests. Measured 2026-08-02: one viewer seek leaves **~25 concurrent segment requests** outstanding spanning #904..#1101, all held for a full 60 s with none aborted — ordinary read-ahead, not probing. There is therefore no such thing as "the segment the player ended on", and any rule choosing among them chooses noise: the old debounce produced **nine encoder restarts in one minute** (#576→#885→#609→#591→#673→#833→#624→#1071→#1101), each killed 5-8 s in, turning a single seek into a ~70 s ordeal that still landed correctly only by luck. Segment requests are now purely data fetches — held until produced, served from disk when behind the encoder — and never reposition it. Same separation both production references use (Jellyfin `startTimeTicks`, webtor `?t=`); see research/hls-seek-prior-art-2026-08-02.md. A seek already covered by the running encode does not restart it at all.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@torrent-tv/proxy",
3
- "version": "2.9.62",
3
+ "version": "2.9.63",
4
4
  "description": "Torrent proxy client that exposes webseed-like HTTP stream endpoint.",
5
5
  "license": "GPL-3.0-or-later",
6
6
  "publishConfig": {
@@ -69,6 +69,22 @@ const ENCODER_STALL_MS = 12_000;
69
69
  // 367,732,369,368,370 seconds apart) collapses to ONE restart at the position
70
70
  // the player ended on, instead of ping-ponging ffmpeg between positions and
71
71
  // producing nothing.
72
+ // How many segments BEFORE the requested position the encoder starts.
73
+ //
74
+ // Required by how HLS players seek, per Apple's HLS authoring guidance: given a
75
+ // position, the player locates the nearest IDR (keyframe) *preceding* it,
76
+ // decodes from there, and only then presents from the requested point. So it
77
+ // always fetches segments BELOW the target — measured 2026-08-02 on iOS: a seek
78
+ // to #1082 fetched from #1074 (8 back), one to #1358 fetched from #1301 (57
79
+ // back), and in the latter case the player asked for NOTHING at or above the
80
+ // target, so an encoder starting exactly on it produced only files nobody was
81
+ // waiting for and playback hung indefinitely.
82
+ //
83
+ // The observed backoff is not constant, so this is a floor, not the whole
84
+ // answer: #fireSettledSeek also pulls the start down to the lowest segment the
85
+ // player is actually waiting on when that is lower still. Costs a few seconds
86
+ // of extra encoding per seek.
87
+ const SEEK_BACKOFF_SEGMENTS = 12;
72
88
  const SEEK_SETTLE_MS = 1_200;
73
89
  // Hard cap on the total settle wait, measured from the first far request of a
74
90
  // burst, so a still-moving scrubber cannot delay a genuine seek forever.
@@ -1065,6 +1081,9 @@ export class HlsSessionManager {
1065
1081
  // #wireEncodeProcess and MAX_SEEK_FAILURES.
1066
1082
  seekFailureTarget: -1,
1067
1083
  seekFailureCount: 0,
1084
+ // Lowest segment index the player is currently waiting for; -1 when
1085
+ // nothing is pending. See getFileStream and #fireSettledSeek.
1086
+ lowestAwaitedIndex: -1,
1068
1087
  progress: {
1069
1088
  state: "starting",
1070
1089
  processedSeconds: 0,
@@ -2040,10 +2059,15 @@ export class HlsSessionManager {
2040
2059
  );
2041
2060
  return true;
2042
2061
  }
2062
+ // Start BEFORE the requested position (see SEEK_BACKOFF_SEGMENTS): the
2063
+ // player needs a segment containing the preceding keyframe, so one that
2064
+ // begins exactly at the target is useless to it.
2065
+ const startIndex = Math.max(0, index - SEEK_BACKOFF_SEGMENTS);
2043
2066
  logger.info(
2044
- `transcode ${session.id} viewer seek to ${positionSeconds.toFixed(1)}s → segment #${index}`
2067
+ `transcode ${session.id} viewer seek to ${positionSeconds.toFixed(1)}s → segment #${index}, ` +
2068
+ `starting at #${startIndex} (${SEEK_BACKOFF_SEGMENTS} back for the preceding keyframe)`
2045
2069
  );
2046
- session.seekTarget = index;
2070
+ session.seekTarget = startIndex;
2047
2071
  if (session.seekSettleTimer) {
2048
2072
  clearTimeout(session.seekSettleTimer);
2049
2073
  } else {
@@ -2140,10 +2164,22 @@ export class HlsSessionManager {
2140
2164
  : producedThisRun >= this.segmentDurationSec
2141
2165
  ? `run produced ${producedThisRun.toFixed(1)}s (first segment done)`
2142
2166
  : `grace of ${RUN_FIRST_SEGMENT_GRACE_MS / 1000}s expired`;
2167
+ // The player may be waiting on something below our fixed backoff — its own
2168
+ // requests say exactly how far back it needs the keyframe, so honour that
2169
+ // rather than a guess. Only ever pulls the start EARLIER, never later.
2170
+ const awaited = session.lowestAwaitedIndex;
2171
+ const effectiveTarget = awaited >= 0 && awaited < target ? awaited : target;
2172
+ if (effectiveTarget !== target) {
2173
+ logger.info(
2174
+ `transcode ${session.id} pulling encode start #${target} → #${effectiveTarget} ` +
2175
+ `(lowest segment the player is waiting on)`
2176
+ );
2177
+ }
2143
2178
  session.seekTarget = null;
2144
2179
  session.seekFirstFarAt = 0;
2145
- logger.info(`transcode ${session.id} seek settle → restart at segment #${target} (${allowedBecause})`);
2146
- void this.#startEncodeRun(session, target);
2180
+ session.lowestAwaitedIndex = -1;
2181
+ logger.info(`transcode ${session.id} seek settle → restart at segment #${effectiveTarget} (${allowedBecause})`);
2182
+ void this.#startEncodeRun(session, effectiveTarget);
2147
2183
  }
2148
2184
 
2149
2185
  /**
@@ -2346,9 +2382,20 @@ export class HlsSessionManager {
2346
2382
  // to wait for the current encode run to reach it or to restart the encoder
2347
2383
  // at this position (server-side seeking). The caller long-polls.
2348
2384
  if (!isPlaylist) {
2385
+ const requestedIndex = this.segmentFormat.segmentIndexFromName(fileName);
2386
+ // Remember the LOWEST segment currently being waited on. The player
2387
+ // always fetches below the seek target (it needs the preceding keyframe),
2388
+ // and by how much varies — 8 segments in one measured seek, 57 in
2389
+ // another. This is that figure straight from the player, and
2390
+ // #fireSettledSeek uses it to pull the encode start down when the fixed
2391
+ // SEEK_BACKOFF_SEGMENTS floor is not deep enough. Reset whenever a run
2392
+ // starts, so it only ever describes the pending seek.
2393
+ if (requestedIndex >= 0 && (session.lowestAwaitedIndex < 0 || requestedIndex < session.lowestAwaitedIndex)) {
2394
+ session.lowestAwaitedIndex = requestedIndex;
2395
+ }
2349
2396
  this.#ensureEncodingFor(
2350
2397
  session,
2351
- this.segmentFormat.segmentIndexFromName(fileName),
2398
+ requestedIndex,
2352
2399
  Number.isFinite(options?.requestSeq) ? options.requestSeq : Number.MAX_SAFE_INTEGER
2353
2400
  );
2354
2401
  }