Resume/bookmark playback position for sequential channels (personal continue-watching) #68
Closed
opened 2026-07-01 23:02:11 +02:00 by timothy
·
4 comments
No Branch/Tag Specified
main
renovate/dotnet-monorepo
renovate/meziantou.analyzer-3.x
renovate/lucene.net
renovate/sqlitepclraw.bundle_e_sqlite3-3.x
renovate/cliwrap-3.x
913-scripted-playout-401
release/v26.15.0-notes
issue-806-guard-populations
scratch/767b-poisoned
scratch/767b-control
release/v26.14.0-notes
release/v26.14.0
docs/510-skill-logo-bug-policy
fix/510-watermark-resolution-policy
fix/629-verdict-classifier-falseopens
fix/609-decisions-edit-token-scope
issue-135-clear-to-none
release/v26.12.0-notes
fix/409b-lastscan-api-parity
fix/401-updatechannel-mirror-422
fix/327-playlist-rename-validation
fix/410-scancancel-log-level
fix/409-447-librariesscreen-neverscanned
fix/338-zap-exit-code
fix/367-plex-budget-message
fix/310-debom-legacy-cs
ci/604-lane-rebalance
feat/388-design-mirror
feat/247-test-ownership
feat/247-primary-action
feat/357-player-owned-playback
feat/357-jellyfin-plugin-poc
fix/289-mcp-hardening
issue58-mcp
feat/244-channels-extract
ci/auto-bump-prod-compose
feat/multi-rerun-collections-api
feat/collections-api
feat/quick-wins
feat/185-docs-part2
feat/140-collections-screen
feat/146-channel-edit
feat/147-classic-ui-link
issue22-renovate-dashboard
feat/91-cutover
feat/63-composite-create
feat/65-library-browse
feat/85-epg
feat/86-schedule-editor
feat/109-dashboard-data
feat/99-session-tracking
fix/dockerfile-node-tag
feat/59-spa-foundation
docs/59-ui-redesign-brief
feat/102-json-guide
feat/111-schedule-durations
feat/104-artwork-upload
feat/103-media-sources-api
feat/playouts-read-api
feat/108-health-api
feat/105-picker-list-endpoints
issue-97-channel-state-api
issue42-jellyfin-musicvideos
issue46-rest-api-error-contract
dependabot/nuget/ErsatzTV.FFmpeg.Tests/multi-d307a2e06f
qsv-improvements
hdr-vulkan-cuda-test
v26.16.0
v26.15.0
v26.14.0
v26.13.0
v26.12.0
v26.11.0
v26.10.0
v26.9.0
v26.8.0
v26.7.0
blazor-final
v26.6.0
v26.5.0
v26.4.0
v26.3.1
v26.3.0
v26.2.0
v26.1.1
v26.1.0
v25.9.0
v25.8.0
v25.7.1
v25.7.0
v25.6.0
v25.5.0
v25.4.0
v25.3.1
v25.3.0
v25.2.0
v25.1.0
v0.8.8-beta
v0.8.7-beta
v0.8.6-beta
v0.8.5-beta
v0.8.4-beta
v0.8.3-beta
v0.8.2-beta
v0.8.1-beta
v0.8.0-beta
v0.7.9-beta
v0.7.8-beta
v0.7.7-beta
v0.7.6-beta
v0.7.5-beta
v0.7.4-beta
v0.7.3-beta
v0.7.2-beta
v0.7.1-beta
v0.7.0-beta
v0.6.9-beta
v0.6.8-beta
v0.6.7-beta
v0.6.6-beta
v0.6.5-beta
v0.6.4-beta
v0.6.3-beta
v0.6.2-beta
v0.6.1-beta
v0.6.0-beta
v0.5.8-beta
v0.5.7-beta
v0.5.6-beta
v0.5.5-beta
v0.5.4-beta
v0.5.3-beta
v0.5.2-beta
v0.5.1-beta
v0.5.0-beta
v0.4.5-alpha
v0.4.4-alpha
v0.4.3-alpha
v0.4.2-alpha
v0.4.1-alpha
v0.4.0-alpha
v0.3.8-alpha
v0.3.7-alpha
develop
v0.3.6-alpha
v0.3.5-alpha
v0.3.4-alpha
v0.3.3-alpha
v0.3.2-alpha
v0.3.1-alpha
v0.3.0-alpha
v0.2.5-alpha
v0.2.4-alpha
v0.2.3-alpha
v0.2.2-alpha
v0.2.1-alpha
v0.2.0-alpha
v0.1.5-alpha
v0.1.4-alpha
v0.1.3-alpha
v0.1.2-alpha
v0.1.1-alpha
v0.1.0-alpha
v0.0.62-alpha
v0.0.61-alpha
v0.0.60-alpha
v0.0.59-alpha
v0.0.58-alpha
v0.0.57-alpha
v0.0.56-alpha
v0.0.55-alpha
v0.0.54-alpha
v0.0.53-alpha
v0.0.52-alpha
v0.0.51-alpha
v0.0.50-alpha
v0.0.49-prealpha
v0.0.48-prealpha
v0.0.47-prealpha
v0.0.46-prealpha
v0.0.45-prealpha
v0.0.44-prealpha
v0.0.43-prealpha
v0.0.42-prealpha
v0.0.41-prealpha
v0.0.40-prealpha
v0.0.39-prealpha
v0.0.38-prealpha
v0.0.37-prealpha
v0.0.36-prealpha
v0.0.35-prealpha
v0.0.34-prealpha
v0.0.33-prealpha
v0.0.32-prealpha
v0.0.31-prealpha
v0.0.30-prealpha
v0.0.29-prealpha
v0.0.28-prealpha
v0.0.27-prealpha
v0.0.26-prealpha
v0.0.25-prealpha
v0.0.24-prealpha
v0.0.23-prealpha
v0.0.22-prealpha
v0.0.21-prealpha
v0.0.20-prealpha
v0.0.19-prealpha
v0.0.18-prealpha
v0.0.17-prealpha
v0.0.16-prealpha
v0.0.15-prealpha
v0.0.14-prealpha
v0.0.13-prealpha
v0.0.12-prealpha
v0.0.11-prealpha
v0.0.10-prealpha
v0.0.9-prealpha
v0.0.8-prealpha
v0.0.7-prealpha
v0.0.6-prealpha
v0.0.5-prealpha
v0.0.4-prealpha
v0.0.3-prealpha
v0.0.2-prealpha
v0.0.1-prealpha
Labels
Clear labels
ad-hoc
api
bug
ci-cd
content
dependencies
enhancement
frontend
in-progress
jellyfin
parked
priority: high
priority: low
priority: medium
review
security
One-off / ad-hoc work not tracked by a dedicated issue
REST API / HTTP endpoints
Something isn't working
Build, test, deploy pipeline
Channel content / schedules / playlists
Dependency updates (Renovate)
New feature or improvement
ChicoryTV React SPA frontend
Claimed by an active session — do not pick up
Jellyfin tuner / IPTV integration
Excluded from automatic queue pickup; work only when explicitly selected
Adversarial review finding
Security / vulnerability fix
Milestone
No items
No Milestone
Projects
Clear projects
No projects
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: timothy/ersatztv#68
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Part of #62 context, but reframed — this is NOT "always-on vs on-demand / stream running" and NOT dizqueTV's wall-clock rewind-simulation. It is a personal resume/bookmark for sequential channels.
Goal
For a channel of sequential content (e.g. a Breaking Bad channel), the channel remembers where the viewer stopped and resumes there on next tune-in — like Plex "Continue Watching," but presented as a linear channel.
Behavior
Prior art
Exists in PseudoTV (related to its "Pause Channel" / resume behavior — exact name to confirm) and the user has seen it in another IPTV tool (possibly ErsatzTV or Tunarr). So it's a proven concept to borrow.
⚠️ The make-or-break requirement: EPG must stay in sync with the resumed position
The user's real-world pain with an existing implementation: the EPG kept ticking on wall-clock time while the stream resumed from the saved position — so the guide showed e.g. S2E3 while tuning in actually played S1E1. The guide and the actual playback desynced, which defeats the feature.
Requirement: when a channel is in resume mode, the XMLTV/EPG must be generated from the paused/resumed playout timeline, not a free-running wall clock. The "now / next" the guide advertises must match exactly what a viewer gets on tune-in. This is the primary thing to get right and the main differentiator vs. existing implementations.
Investigation / open questions
ChannelGuide/GetChannelGuideHandler) must read the resume state so the guide reflects actual upcoming content, not elapsed wall-clock. Interaction withXmltvTimeZone/block behavior to verify.Scope
Related: #59, #62.
Done-when
PlayoutTimeShifterreports the shifted channel numberInvestigate "always-on vs on-demand" playout mode for channelsto Resume/bookmark playback position for sequential channels (personal continue-watching)Claiming — design/investigation only, not implementation
Picked up as part of bundle B (closing out the #62 epic), but deliberately scoped down. Stating that up front so nobody reads this claim as "resume mode is being built."
Why: despite the "Part of #62" framing, this is not a peer of #67. The body describes a new playout mode — an "advance only while watched" playout clock that freezes when unwatched, persisted per-channel (per-viewer?) position, plus the make-or-break requirement that XMLTV/EPG be generated from the resumed timeline rather than a free-running wall clock (
GetChannelGuideHandler). The body's own "Investigation / open questions" section is unresolved. Building that blind, in the same session as an image-upload convenience, is how a half-designed playout mode ships.Deliverable this session: a design write-up posted to this issue — resume-state model and where it persists, how the EPG derives from the resumed timeline (the primary differentiator), per-channel vs per-viewer, and interaction with existing playout modes /
XmltvTimeZone. Implementation follows as separate tracked work once that design is agreed.Claim will be released with the design comment.
Claim released — design NOT delivered, issue untouched
Claimed alongside #67 as part of a "close out the #62 epic" bundle, scoped to a design/investigation deliverable only. That design was not produced. Nothing here was started beyond reading the issue body; no code, no recon, no partial write-up. Releasing the claim so the next session picks this up clean.
Why it's being deferred rather than rushed: this is not a peer of #67. It needs a new playout mode with an "advance only while watched" clock that freezes when unwatched, persisted per-channel (per-viewer?) position, and — the make-or-break requirement in the body — an XMLTV/EPG derived from the resumed timeline instead of a free-running wall clock. Getting that wrong reproduces the exact bug the issue was filed about (guide advertising S2E3 while tune-in plays S1E1). It deserves a fresh session with its own recon of the playout timeline, the anchor/history model, and
GetChannelGuideHandler, not the tail of an unrelated session.One piece of context worth carrying forward (learned while working #67 in the same area): the closest existing analogue in the codebase is the mirror-channel mechanism (
PlayoutSource.Mirror+PlayoutOffset), which already rebases one channel's timeline relative to another's — worth reading before designing a freeze/resume clock from scratch.Still open, unblocked, and unclaimed.
Claiming — design/investigation deliverable (per the prior claim's scope)
Picking this up as a design write-up, not implementation, exactly as the earlier claim intended. Session goal: resolve the open questions — resume-state model + persistence, EPG-derived-from-resumed-timeline (the make-or-break requirement), per-channel vs per-viewer, and interaction with existing playout modes / the mirror-channel
PlayoutOffsetrebasing machinery flagged by the prior session. Implementation to follow as separate tracked work once the design is agreed.Starting with recon of the tune-in→PlayoutItem timing path,
GetChannelGuideHandler, and thePlayoutSource.Mirror+PlayoutOffsetmechanism.Closing record
Outcome: Shipped in PR #540 (branch
fix/68-ondemand-guide-refresh, headdfed9a39). Merge pending — the only CI red is an unrelated flaky SPA test (LibrariesScreen.test.tsx:292, scan-pollingwaitFortimeout); needs an operator re-run of theBuild & test (.NET)job.fixes #68will auto-close this issue on merge.Recon finding (the real story): the feature #68 describes already exists as
PlayoutMode.OnDemand—Playout.OnDemandCheckpointpersists the viewer's position,UpdateOnDemandCheckpointadvances it while watching (minus one segmenter-timeout of rewind-for-context), andPlayoutTimeShifter.TimeShiftslides the whole materialized timeline forward on tune-in so the paused item is active again. Because the shift rewritesGuideStart/GuideFinishalongsideStart/Finishand both guide + playback read the samePlayoutItemrows, ErsatzTV freezes guide and playback together — structurally avoiding the free-running-wall-clock desync this issue was filed about.Root cause of the residual gap:
TimeShiftrewrote the stored rows but the XMLTV guide is served from a cached.xmlfragment that onlyRefreshChannelDatarebuilds, and the tune-in path never enqueued it (build/config edits did). So an external EPG client (Jellyfin) polling after a thaw could see a stale timeline until the next incidental rebuild — a cache-freshness bug, not a timing-model flaw.Files changed:
IPlayoutTimeShifter.cs(returnsList<string>— shifted channel + its mirrors),PlayoutTimeShifter.cs(mirror fan-out after a non-zero shift),TimeShiftOnDemandPlayoutHandler.cs(enqueueRefreshChannelDataonCancellationToken.None), +PlayoutTimeShifterTests.cs/TimeShiftOnDemandPlayoutHandlerTests.cs(9 tests).Decisions/conventions changed: added
scheduling.ondemand-guide-refresh-on-thawto docs/decisions.md.Reusable knowledge: OnDemand PlayoutMode is the resume/bookmark feature; a mirror channel of an on-demand source needs its guide refreshed on the source's thaw (same fan-out
BuildPlayoutHandleralready does).Verification: 1793 C# tests green (9 new; non-vacuity proven by a compiling negative control); the flaky SPA test passes 3/3 locally. Two cold adversarial reviews → MERGEABLE. Live-E2E not required (internal background MediatR command, not an
/api/*write-path handler).Deferred: per-viewer resume (single per-channel checkpoint; #68 says per-channel suffices for one household).
Docs updated: docs/channels.md (On-demand resume section), docs/domain-model.md, docs/decisions.md (+ regenerated catalog).