Catch-up versus live: different products, shared EPG
Linear channels broadcast once in real time; catch-up lets viewers watch aired programs after the live window without planning a recording. Restart lets someone join a live show from the beginning while the broadcast continues. Both features reuse electronic program guide metadata but attach different entitlement objects and storage policies. Rights holders often grant live simulcast narrowly while catch-up requires separate fees, day counts, and ad load rules.
Operators conflate cloud DVR with catch-up in marketing, but engineering must separate them. DVR is user-initiated recording with quota; catch-up is platform-published replay slices tied to EPG events. Mixing the two breaks compliance when users expect to keep recordings ninety days but catch-up expires in seven.
Cloud DVR architecture choices
- Network DVR records once per program for shared replay versus per-subscriber copies.
- Storage retention aligns with licensor days and storage cost models.
- Concurrent recording limits prevent STB scheduling wars on shared tuners emulated in cloud.
- Conflict resolution when two programs overlap on same channel stream.
- Failover when origin misses recording start due to encoder glitch.
Shared network recordings reduce storage but require geo and blackout enforcement at playback identical to live. Per-user recordings increase cost linearly with subscribers yet enable pause and rewind during live with private copy semantics in some jurisdictions.
Start-over without full DVR
Restart uses a rolling buffer retained from program start or fixed minutes behind live edge. Buffer depth trades storage against sports fans arriving late. DRM and ad insertion must reposition to correct mid-roll cues when viewer joins from beginning while live ad pod may differ. Player UX should show spoiler-safe progress relative to broadcast clock.
EPG accuracy drives trust
Catch-up tiles appear from schedule metadata; if end times slip because live event runs long, automated cutters truncate finals or include post-game studio talk licensors forbid. Ingest schedule updates from broadcasters with SLA and manual override consoles for operations during overtime games. Link catch-up assets to schedule version IDs so replays update when EPG corrections land.
- Expose program boundaries with frame-accurate in markers where contracts require ad pods.
- Handle daylight saving jumps without duplicating or deleting hour-long slots.
- Mark repeats versus first-run in UI to avoid viewer confusion on catch-up rows.
- Support series recording rules that expand to new episodes in rolling seasons.
- Disable scheduling on channels without catch-up rights even if live plays fine.
Retention windows and automated expiry
Each title carries catch-up availability hours from rights deals. Expiry jobs delete objects from storage and search indexes simultaneously. Grace extensions for technical failures should be logged for licensor reporting. Subscribers who started watching before expiry need policy on whether playback completes or hard-stops at license end.
Ads in catch-up and replay
AVOD catch-up may require ad slots distinct from live avails. Server-side stitching must swap creative for replay context and respect frequency caps per viewer. FAST channels monetizing replay windows need SCTE markers preserved through record path or replaced with alternate ad decision rules.
SVOD and ad-free replay
Premium tiers sometimes offer ad-free catch-up while free tier keeps ads. Entitlement checks apply at replay manifest request, not only live tune-in. Promotional free preview of catch-up must honor downgrade when trial ends mid-binge.
Device and platform constraints
Some TV platforms restrict restart UX patterns or mandate their own DVR APIs. Certification guides define trick-play keys and how far seek backward moves relative to live edge. Mobile apps may disable background recording scheduling to save battery; communicate limits clearly.
Bandwidth and storage cost governance
Long retention on popular sports multiplies egress when fans rewatch highlights. Tier storage policies: more hours for premium SVOD, shorter for AVOD. Cold storage tiers for expired-but-not-yet-deleted objects reduce cost if legal holds apply.
Rights audits specific to time-shifted viewing
Licensors distinguish start-over, catch-up, and full DVR in contracts. Audit exports list programs available beyond live window with deal ID references. Geo for replay may shrink versus live if replay rights exclude border markets. Fast takedown workflows execute when licensor pulls permission after controversial broadcast.
Music rights inside live events sometimes block catch-up entirely while live cleared with separate sync licenses. Metadata flags on episodes prevent accidental publish of blocked replays.
User experience patterns
Guide rows should show remaining catch-up time badges so urgency drives views before expiry. Continue-watching for replay uses broadcast date ordering, not upload date. Restart buttons on live player need confirmation if user will lose current live point unless dual-buffer supported.
Failure modes operators rehearse
Missed recording start due to upstream blackout leaves angry subscribers; offer credit policies and automatic re-ingest if broadcaster provides backup feed. Partial recordings from encoder crash should not publish; QA gates compare duration to EPG expected length within tolerance.
- Simulate EPG drift during load test before major sports season.
- Verify CDN cache keys for replay differ from live to prevent wrong manifest.
- Test trick-play near replay expiry boundary at midnight local rights cutoffs.
- Ensure analytics attribute replay views separately from live concurrents.
- Document subscriber communication when platform-wide retention policy shortens.
Integration with VOD catalog
Some networks want catch-up to graduate into library VOD with new asset IDs. Handoff workflows remap watch progress and remove duplicate rows from UI. Contract may require ad-free only in VOD phase; enforce with new entitlement package on transition.
Concurrent viewers and time-shifted peaks
Catch-up creates secondary viewing peaks hours after live airing. Origin and CDN capacity plans must include replay surges for prime time dramas, not only live concurrent counts. Recommendation rails pushing catch-up before expiry can shift load unpredictably; coordinate with SRE when marketing runs binge reminders.
Multiview and alternate feeds
Sports may offer tactical camera angles as separate linear streams with independent catch-up objects. UI must clarify which angle recorded when user schedules generic team match recording. Rights for alternate feeds differ; mislinked EPG causes replay of unauthorized bench camera.
Regional channel variants
Local news inserts break national feed synchronization. Catch-up for national version should exclude local opt-out segments or stitch regional slates per market. Ad substitution on replay must respect same local avails rules as live if not pre-negotiated simplification.
- Expose recording quota in settings with human-readable hours not opaque points.
- Notify subscribers before quota deletion policies remove oldest recordings.
- Support series cancel mid-season without orphan partial recordings cluttering library.
- Align trick-play keys on STB remotes with catch-up versus live buffer semantics.
- Test HDMI passthrough audio formats on replay identical to live path.
Partner platform catch-up requirements
Some MVPD integrations require standardized metadata for replay assets delivered via partner API. Late delivery penalties apply when catch-up publish misses SLA after broadcast end. Automate handoff timestamps and alert operations when pipeline exceeds contractual minutes.
Subscriber education and expectation setting
Help centers should illustrate difference between record, restart, and on-demand library with diagrams because marketing terms blur in consumer minds. Clear copy on which channels support catch-up prevents support volume when cable-style favorites fail on FAST-only brands.
Disaster recovery for recording pipelines
When origin fails mid-broadcast, decide policy: partial replay with apology credit, black slate, or alternate feed from backup encoder. Legal pre-approves messaging templates. Post-incident, reconcile which subscribers lost recordings and automate goodwill credits where contracts silent but brand reputation demands action.
Cold storage restores for aged catch-up titles requested for clip licensing should not block hot playback paths; isolate archival retrieval queues from primetime replay CDN paths.
Measurement and programming feedback loops
Replay viewership informs syndication pricing and ad inventory forecasts separate from live ratings. Analytics must attribute minutes watched on catch-up with broadcast date dimension so programmers see delayed audience for scheduling decisions. Under-reporting replay because events tagged as live-only skews renewal talks with advertisers.
Kids and time-shifted parental controls
Catch-up of mature programs aired after watershed may still be available mornings on kids profiles if parental schedule rules ignore replay context. Apply rating time windows to replay start times or block catch-up on child profiles entirely for flagged channels.
FAST channels looping short catalogs blur line between live and replay; document internally whether loop repeats count as catch-up for rights reporting or as continuous linear.
Accessibility on replay surfaces
Catch-up players must expose same caption and audio description controls as live, including language persistence across episodes in binge mode. Seek previews on scrub bars need audio description timing adjustments when users skip recaps.
Operators publishing replay-only FAST channels should verify EPG still reflects original airtime for compliance reports even when content loops artificially.
Contract renewals and catch-up depth negotiation
Licensors trade longer catch-up windows for higher fees or ad load minimums. Model viewer hours per day of replay before renewing seven-day versus thirty-day terms. Finance should see storage and egress cost per extra replay day, not only headline license fee.
When renewals shrink windows mid-season, grandfather in-progress series recordings with explicit sunset banners so subscribers understand why future episodes will not record.
Load-test restart buffers during simultaneous live finales across multiple channels; shared origin recorders can miss starts when ingest spikes exceed planner assumptions.
Document difference between nPVR and cPVR in internal wiki so sales engineers do not promise personal library retention when contract sells broadcast catch-up only.
Align billing descriptors on invoices with catch-up features actually enabled; refunds spike when subscribers expected unlimited cloud DVR but purchased basic live-only tier.
LinqTV Playout and live stacks integrate with operators who monetize both linear and replay. Validate end-to-end by airing test pattern channel, recording network DVR, exercising restart during simulated live slate, and confirming expiry removes URLs from all app surfaces within agreed SLA.
FAQ
How much catch-up retention do viewers expect?
Seven to thirty days is common for broadcasters; sports-heavy services may offer shorter highlight windows but promote longer for drama. Set expectations in UI rather than hiding expiry until play fails.
Is restart always allowed when catch-up exists?
Not legally. Some deals permit catch-up next day but forbid restart during live airing. Encode flags per program or channel.
Shared or per-user DVR for cost control?
Shared network DVR scales for popular linear; niche channels with few viewers may still need shared copy. Per-user matters when pause-buffer privacy or jurisdiction treats copies as personal recordings.
Do downloads apply to catch-up?
Offline download rights are yet another licensor checkbox. Do not inherit from catch-up without explicit flag or mobile downloads will violate contract.
Related LinqTV pages