Make timed player overlays recover correctly after a seek

Define state rather than a sequence of commands

Mux Player’s documented cue points associate metadata with time ranges. In its Web Component and React implementations, omitting an end time joins a cue to the next one, and seeking within that interval can activate the earlier cue. These details were checked on 7 November 2026. The web player is in maintenance mode; scope acceptance to an existing deployed implementation rather than prescribing it for every new project.

Write the intended overlay for each interval, including intervals with no overlay. Use the media clock, not the time elapsed since the page loaded. A product label should not remain visible merely because the application never received the next sequential cue. The contract must answer what belongs on screen after entering the interval from any supported direction.

Choose explicit endings where silence matters

Identify callouts that must disappear before the next one begins. A price card shown during one product demonstration should not linger over an unrelated scene. Have the developer represent that gap through the supported cue mechanism and verify its actual behavior. Do not assume that a start-only event implies a short display duration.

Separate descriptive state from consequential actions. Becoming the active cue can update a label or reveal a link; it should not itself place an order, send a message or establish that the viewer consented to anything. Replaying an interval can activate it again. Keep ordinary user confirmation and authorization in the application’s action path, regardless of how many times the media revisits the same cue.

Rebuild state after non-linear viewing

Create a fixture with an overlay interval, a gap and a second overlay. Test forward playback, seeking directly into each interval, seeking into the gap and moving backward across both boundaries. Pause on a callout and resume. Record the expected active state before running each case so a callback log does not become the only definition of success.

Mux documents removal of cue points when media is unloaded or the playback identity changes. Ask the application owner how the correct cue set is attached to a new source and how the previous overlay is cleared. A player that shows the second video beneath the first video’s product label has failed even if both individual cue lists are valid. Use invented product references and avoid live transactional fixtures.

Accept the visible result and the reset behavior

Inspect the visible overlay alongside the current content, then compare the event trace only as diagnostic evidence. Repeated callbacks are not necessarily repeated user exposures, and a callback is not proof that a person read the callout. Keep marketing measurement separate from state correctness.

Record the asset revision, cue-set revision, player version and expected reset behavior. When an edit changes the scene order, review the interval contract rather than merely preserving the old timestamps. If the implementation cannot reliably rebuild state after seeking, simplify or remove the affected overlay until the behavior is resolved. The acceptance artifact is a small state table that remains correct under non-linear playback, not a list of moments that happened to work during one uninterrupted viewing.

Make the reasoning concrete.

A fictional cookware film shows a product card during one demonstration. The application reveals the card on a start cue but never clears it when a viewer seeks past the demonstration into a caption-only safety explanation.

The team implements the approved state contract and keeps purchase behavior behind an explicit user action. It does not count cue callbacks as purchases, consent or verified reading.

Take the questions into your next brief.

Use these prompts in your own notes. Nothing is submitted from this page.

1. Interval

   What overlay, if any, belongs at this media position?

2. Gap

   Where must the previous callout stop before another begins?

3. Seek

   Does entering from either direction reconstruct the same state?

4. Reset

   What clears and reloads when the playback source changes?

5. Action

   Are consequential actions still controlled by explicit user interaction?

Watch for the wrong conclusion.

• Treating cue starts as a complete state model.
• Leaving gaps undefined.
• Using replayable callbacks to trigger consequential actions.

Sources & scope

Workflows, worksheets and fictional examples are original editorial analysis, not supplier implementation instructions or measured business results. Sources support only the specifically attributed platform facts. Supplier controls, contracts and local requirements can change; verify the actual placement and current provider guidance before implementation.

• Mux: Advanced usage of Mux Player →Primary platform documentation · Supports: Supports cue ranges, omitted-end behavior, seek activation, source-change removal and maintenance-mode scope; state contract and safeguards are editorial.