A live session has already done expensive work. It has identified the programme, synchronized speakers and slides, created a recording, applied policy and preserved the audience experience. Replay should not rebuild that meaning from disconnected files. It should reuse the verified work already completed.
TL;DR
- Replay begins only after the approved recording or programme source is ready.
- It reuses Program Output identity, timing, captions, presentation state and lineage instead of recomposing the session from scratch.
- On demand, Simulive and scheduled replay are delivery modes around the same approved programme, not separate products.
- Transcode once and reuse avoids repeated processing when an existing rendition is suitable for the destination.
- Live Gap Recovery is different from replay because it returns the participant to current live time first.
- Access, retention, privacy and distribution remain governed by the customer product and approved commercial scope.
Replay is not a second production
When a live session ends, the programme already has an identity and an authoritative order. Speakers appeared at particular times. Slides, captions and overlays changed in relation to the live clock. Recording captured the approved output and produced a readiness state.
A replay system that ignores that work has to guess again. It may attach the wrong slide, flatten structured state unnecessarily or create a new composition that differs from the session the audience saw. That duplication adds cost and weakens trust.
Replay treats the verified programme as the source. It can package and deliver the material differently without inventing a new version of the event.
Readiness before availability
Replay should not appear merely because a recording job or file exists. The approved source must be ready for the intended use. That can require completed composition, verified duration, accessible media, synchronized timing and any expected captions or structured assets.
A clear readiness boundary prevents a viewer from receiving a partial file or a session whose supporting state is still processing. Processing, failed, unavailable and ready should remain distinct outcomes.
The customer product can then decide when replay becomes visible and who may access it. cRUD Morph returns the state; it does not invent the commercial or audience rule.
One source, several replay modes
A verified programme can support more than one approved viewing mode. On demand gives a viewer control over when to watch. Simulive schedules the recorded programme as a timed experience. A secure replay can remain connected to registration and entitlement. Destination delivery can prepare a suitable package for another approved surface.
These modes may use different controls and audience rules, but they should not require separate media truth. The same programme identity, source and lineage remain underneath them.
This makes later comparison and reporting more dependable. A team can distinguish how the programme was delivered without pretending each mode created a separate original.
Makes the verified programme available under the customer’s approved audience and access rules.
Lets an entitled viewer choose when to consume the programme and available structured material.
Presents an approved recording on a schedule while the surrounding product governs participation.
Packages or distributes the programme through an approved destination without changing its source identity.
Transcode once, reuse when suitable
Repeated processing is easy to hide. A live output may be transcoded for recording, processed again for replay and processed once more for each destination. Sometimes another rendition is required. Often an existing approved rendition can do the job.
Optimize checks whether suitable work already exists before asking the system to repeat it. Reuse depends on format, quality, policy, destination and retention. It is not permission to reuse any available file.
This approach reduces unnecessary compute, storage and delay while preserving evidence about which rendition served which purpose.
Keep structured state structured
Some parts of a media experience remain more useful as state than as pixels. Presentation assets, captions, chapters, polls and interaction records can support navigation, accessibility and review when they retain structure.
A composed replay can show what the audience saw while those elements remain separately available where the customer product is authorized to use them. This avoids forcing every later experience to depend on information burned into a video frame.
Structure also supports new renditions without changing the authoritative source. A viewer can search captions or move to a chapter while the underlying programme remains the same.
Live Gap Recovery is not replay
A participant who reconnects to a live session should not be forced to watch stale buffered media. Live Gap Recovery expires obsolete media and returns the participant to the current live moment first.
The missed interval may then be explained through an authorized transcript, state summary or bounded replay when available. Exact authoritative records must remain distinct from generated summaries. The participant chooses whether to inspect what was missed without losing the live event again.
Replay looks back at a completed or bounded programme. Gap recovery restores current participation. Both reuse session evidence, but they serve different experiences.
Reuse needs lineage and authority
An efficient system can still be wrong if it reuses the wrong source. Every replay should retain a dependable relationship to the session, recording, composition, processing and destination that produced it.
Provenance supplies that relationship. Access and retention policy determine whether reuse is permitted. The Experience to Cost Governor can avoid unnecessary work, but cost does not override privacy, security, customer entitlement or the approved experience.
The result is reuse with accountability rather than reuse because a file happened to be available.
Questions to ask about replay
- Which verified recording or Program Output is the replay using?
- What must be ready before the replay becomes available?
- Do on demand, Simulive and secure replay share one source identity?
- Which captions, slides, chapters or interactions remain structured?
- Can an existing rendition be reused instead of processing the programme again?
- How does the system distinguish live gap recovery from ordinary replay?
- Which access, retention and customer ownership policies apply?
- Can every package and destination be traced to the approved source?
Summary
Replay should reuse the programme authority, timing, recording and structured state already created by the live session. It can package that work for secure replay, on demand, Simulive or approved destinations without producing a second original.
Reuse remains governed. The source must be ready, the rendition must suit the destination and the customer’s access, privacy, retention and commercial rules continue to apply.
Frequently asked questions
What does Replay do?
Does replay use the same file as live delivery?
Is Live Gap Recovery a replay feature?
Why keep slides and captions structured?
About this article. It explains the public role of Replay within cRUD Morph. It does not disclose private processing implementation or promise that every replay mode, package, destination or derivative is available in every engagement. Scope follows the released service, entitlement and certified configuration.