A Web player is the audience boundary. Verify the media first, then configure who may watch, what the page looks like and whether a scheduled or paid access step applies.
Antes de empezar
A verified live source or finalized media file.
The audience policy: open, password, per-viewer credentials or PayPal pay-per-view.
Approved branding assets and event schedule when used.
Ajustes explicados
Se explican los controles que necesita el operador. Los nombres internos y eventos de implementación se omiten intencionadamente.
Player and source
Connect one delivery-ready source.
- Player name and active state
Operator identity and lifecycle state.
- Player type
Choose the supported live or on-demand playback mode.
- Input source
Select the verified live stream or file.
- Port
Listener port when required by the selected player mode.
Playback
Tune browser delivery only when required.
- Resolution and adaptive bitrate
Prepare the intended rendition behavior for the audience network.
- HLS fragment and live-edge settings
Control latency and playlist depth for HLS delivery.
Change these only after baseline playback works.- Media type
Describe the live or recorded media behavior expected by the player.
Audience access
Choose one explicit admission model.
- Open access
Anyone with the viewer URL can watch.
- Shared password
One password protects the player.
- Per-viewer credentials
Generate or assign email/password access for individual viewers.
- PayPal pay-per-view
Require a configured PayPal payment and amount before playback.
The reviewed UI supports PayPal; do not promise arbitrary providers.
Presentation and event
Create the viewer-facing page.
- Logo, cover and background
Upload or select approved player branding.
- Event date and timezone
Show countdown/calendar behavior before the planned start.
- Support email
Give viewers a contact for access or playback problems.
Primer flujo seguro
- 01
Verify the input outside the player.
- 02
Create the player, select its live or file source and start with default playback tuning.
- 03
Choose exactly one audience access model and test both an allowed and denied session.
- 04
Add branding and event details without hiding playback controls.
- 05
Start the player and test the viewer URL in a clean desktop and mobile browser.
Ejemplos de flujo
Publish a secure customer livestream
A live SRT or RTMP source should be available only to invited viewers.
Cómo construirlo
- 1
Verify the live source and create a player from it.
- 2
Choose shared-password or per-viewer credential access.
- 3
Test a denied session before testing the valid credential.
- 4
Share the viewer URL and credential through separate channels.
Sell access to a scheduled replay
A finalized recording should open after a PayPal payment.
Cómo construirlo
- 1
Preview the recording file and create an on-demand player.
- 2
Configure the PayPal client and price in a non-production test first.
- 3
Set event date/timezone and support email when the replay has a launch window.
- 4
Complete the payment flow and verify playback in a new browser session.
Verificar el resultado
- A supported browser plays the expected source with audio.
- An unauthorized session is denied and an authorized session succeeds.
- Payment, countdown and support controls appear only when configured.
- Branding remains readable across desktop and mobile layouts.
Solución de problemas
The page opens but video does not play
Comprobar- Verify the source independently.
- Check the player is active.
- Test default HLS settings before custom fragments or ABR.
Repair the media boundary first, then reintroduce playback tuning.
A valid viewer cannot pass authorization
Comprobar- Confirm the selected access mode.
- Check the exact credential or payment state.
- Use a clean browser session.
Correct the audience record without making the player public.