Host Live Roles, Viewer Audio, and Receive-Only Behavior

Host Live has two managed realtime roles: host and viewer. The exact Topic Host is the only publisher; ordinary Watch Party viewers subscribe to Host tracks and receive media without gaining publishing controls.

Host Live begins with the Host camera and microphone off, and viewer audio can still require a one-time browser gesture even after the remote microphone track is connected.

Host Role

The Host receives microphone, camera, device, fullscreen, and Stop Host Live controls. The browser restores only media the Host deliberately enabled; the initial desired camera/microphone state is off.

Viewer Role

Viewer authorization is room-scoped and receive-only in the QCLF UI. The client auto-subscribes to the exact managed Host identity and ignores unrelated participant tracks for the Host tile. Viewers get Host-audio mute/enable and fullscreen controls, not camera/microphone publishing buttons.

Viewer Audio and Browser Policy

When a Host microphone track arrives, QCLF attaches an audio element and tries to start playback. If the browser blocks audio, the viewer sees Enable Host audio; one click retries audio playback without changing the Host microphone state.

Turning Host Tracks Off Is Not a Disconnect

If the Host turns camera or microphone off, viewers clear that track and continue to treat the room as connected. Only an actual Host participant/room disconnect enters reconnect/status-check behavior.

Host Live and Watch Party Audio Are Separate

Viewer controls for Host Live audio are separate from the YouTube player volume/mute controls. Muting Host Live does not mute the YouTube Watch Party, and vice versa.

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.