@torrent-tv/proxy 2.9.67 → 2.9.68

package/CHANGELOG.md

@@ -1,3 +1,7 @@
+## 2.9.68
+
+- **Fix**: A seek could be dragged back to the position the viewer had just left. The encoder start was pulled down to the lowest segment the player had outstanding — a stand-in from when the distance to the preceding keyframe was unknown — but at seek time those requests still describe where the player was PLAYING, not where it is going. Field 2026-08-02: a seek to 23:34 (#135) correctly resolved to a start of #134, then got pulled to **#82** (14:15, the position just left) and crawled forward from there. Removed: since boundaries became real keyframes (2.9.65), exactly one segment back always suffices, so the pull has nothing left to correct for.
+
 ## 2.9.67
 
 - **Fix**: A seek waited far longer than it needed to — 56 s measured in the field, of which roughly 50 s was self-inflicted. `SEEK_BACKOFF_SEGMENTS` (how far before the requested segment the encoder starts) was **12**, chosen when segments were an invented 4 s apart and the distance to a usable keyframe was unknown. Since 2.9.65 every boundary IS a real keyframe read from the container index, so the single preceding segment is guaranteed to start on one — and with real 10.43 s segments the old value meant encoding **125 s of content** before reaching the viewer position. Lowered to **1**. Observed: the encoder started at #332 for a seek to #344 and the requested segment only arrived 56 s later, while every segment after it was served in ~100 ms.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@torrent-tv/proxy",
-  "version": "2.9.67",
+  "version": "2.9.68",
   "description": "Torrent proxy client that exposes webseed-like HTTP stream endpoint.",
   "license": "GPL-3.0-or-later",
   "publishConfig": {

package/services/hls-session-manager.js

@@ -2244,18 +2244,15 @@ export class HlsSessionManager {
       : producedThisRun >= this.segmentDurationSec
         ? `run produced ${producedThisRun.toFixed(1)}s (first segment done)`
         : `grace of ${RUN_FIRST_SEGMENT_GRACE_MS / 1000}s expired`;
-    // The player may be waiting on something below our fixed backoff — its own
-    // requests say exactly how far back it needs the keyframe, so honour that
-    // rather than a guess. Only ever pulls the start EARLIER, never later.
-    const awaited = session.lowestAwaitedIndex;
-    const pullFloor = Math.max(0, target - SEEK_PULL_LIMIT_SEGMENTS);
-    const effectiveTarget = awaited >= pullFloor && awaited < target ? awaited : target;
-    if (effectiveTarget !== target) {
-      logger.info(
-        `transcode ${session.id} pulling encode start #${target} → #${effectiveTarget} ` +
-          `(lowest segment the player is waiting on)`
-      );
-    }
+    // Deliberately NOT pulled towards the lowest segment the player is waiting
+    // on. That was a stand-in for not knowing how far back the preceding
+    // keyframe lay, and it is now both unnecessary and harmful: boundaries are
+    // real keyframes (2.9.65), so exactly one segment back always suffices,
+    // while the player's outstanding requests at seek time still describe where
+    // it was PLAYING, not where it is going. Field 2026-08-02: a seek to #135
+    // was dragged back to #82 — the position the viewer had just left — because
+    // the player was still fetching around it.
+    const effectiveTarget = target;
     session.seekTarget = null;
     session.seekFirstFarAt = 0;
     session.lowestAwaitedIndex = -1;