Understand Archived Watch Party Media Position Context
When Watch Party timestamp capture is enabled, QCLF can attach the current YouTube item and playback position to each live chat Message as it is sent. Archive conversion then preserves that source context on the permanent forum reply.
The stored media context helps later history/search explain where in the Watch Party a message occurred; it does not record or copy the YouTube media itself.
How Live Messages Capture Context
Before a Watch Party live Message is submitted, the frontend reads the current player time and current YouTube video ID into hidden fields. The server stores those values as media_position_seconds and media_item_id on the live Message when timestamp capture is enabled.
Timestamp Capture Is Configurable
The Watch Party session setting capture_media_timestamps defaults on. If it is disabled, the composer skips this position capture and archived replies therefore do not gain that per-Message media position from the player.
What Archive Conversion Preserves
The permanent reply receives the original live timestamp plus source_media_source_id, source_media_item_id, and source_media_position_seconds. Archive conversion is idempotent, so retries do not create a second permanent reply for the same live Message.
How Search Uses the Context
Archived Watch Party Message results retain the “From Watch Party” source label. When a stored media position exists, Search also shows a human-readable Video M:SS (or H:MM:SS) context alongside the result.
What This Does Not Mean
- QCLF does not save the YouTube video bytes.
- A media position is contextual metadata, not a promise that the external YouTube source will remain available forever.
- Host Live camera/microphone is a separate managed stream and is not recorded into this archived media context.
Community Discussion
Want to compare forum workflows, share practical QCLF tips, or discuss how other Joomla site owners use this feature? Visit the QC Live Forum Community. For private support, bug reports, account-specific entitlement problems, or feature requests, use the QuantaCade support system.