mirror of
https://github.com/Dispatcharr/Dispatcharr.git
synced 2026-07-18 00:55:50 +00:00
7655060149
Clients (TiviMate) keep the ?session_id= query when they rebuild the seek URL with a new start timestamp, so every timestamp-jump FF/RW landed on the reused session's STORED provider_timestamp — playback snapped back to the position the session was created for (the rewind anchor), 100% reproducible: two requests with different start values on one session returned byte-identical streams. The reuse path now always recomputes the provider timestamp from the REQUESTED one (the provider zone is a property of the account — read from the default profile's server_info, same as the fresh path) and moves the pool descriptor (media_id + provider_timestamp) to the position actually served, so fingerprint matching and same-channel displacement keep comparing against reality. Slot continuity is unchanged. Regression tests: reused session serves the requested timestamp (unit), descriptor follows the seek (unit), and an end-to-end timestamp-jump with the same session_id reaches the new position through timeshift_proxy. |
||
|---|---|---|
| .. | ||
| accounts | ||
| api | ||
| backups | ||
| channels | ||
| connect | ||
| dashboard | ||
| epg | ||
| hdhr | ||
| m3u | ||
| output | ||
| plugins | ||
| proxy | ||
| timeshift | ||
| vod | ||