Media Sources And Playback Windows
Configure a source, put its picture on a grid and troubleshoot playback.
Playback windows are independent grid objects. Video monitor and Multiviewer remain equipment templates for documenting physical ports and signal flow. They do not automatically create players.
Use + Playback in the grid toolbar, choose a configured source, name the window, and choose its grid. An optional equipment reference is descriptive: the equipment can live in another grid, and moving or deleting it does not move or delete the playback. Add the same source again to place it in another grid, or twice in one grid. Each placement saves its own position, size, title and enabled state. Source credentials are excluded from workspace exports.
Drag a window heading to move it; drag its lower-right corner to resize. Properties also accepts width/height. Pause, Retry, and Expand operate on that window. Delete uses the normal focused Confirm dialog. Observe locks editing while keeping playback live. Simulate pauses real feeds. A dashboard can contain only text, conditional status shapes and live feeds, with no equipment.
The grid menu has Open grid in a new window (the browser may open a tab). Move that window to another display. Grid URLs include ?grid=<id>, so different windows can retain different grids on reload. Each visible browser window subscribes independently. Disable the grid carousel and alert following if a particular display must remain on one grid; these settings are currently workspace-wide.
Configure a source in the panel
- Open Media sources in the equipment sidebar, or + Playback → + New source.
- Enter a name and choose the connection type. The form shows only relevant fields: VNC host/port/credentials, RTSP URL/transport, Proxmox host/realm-qualified username/node/VM ID, or capture driver/device.
- Save source, then Preview from Media sources to check the picture. Use Test pattern to verify the playback path without equipment.
- Use + Playback, select the source and destination grid, then add the window. One source can appear in multiple grids.
Create and edit operations apply immediately without server file edits or a restart. Saved URLs are shown in the editor and can be edited directly. Passwords and tokens are not returned; leave their fields blank to retain them. Explicit remove controls clear optional credentials. Changing the connection type clears its previous connection settings. Editing a source reconnects affected players; unrelated feeds continue. Remove placements (including saved scenario references) before deleting a source. Conflicting edits are rejected so one editor cannot silently overwrite another.
Saved source credentials are encrypted and managed by Sysavia. Workspace exports contain source references, not saved passwords. Some playback protocols still pass connection details to the browser while a viewer is open.
Supported paths
| Input | Source kind | What runs where |
|---|---|---|
| RTSP camera, RTP/UDP, SRT, MPEG-TS | ffmpeg | FFmpeg on the panel host decodes input and sends a shared MJPEG confidence feed |
| HDMI, DisplayPort, SDI | ffmpeg | Compatible capture hardware and its driver on the host running FFmpeg |
| ASI | ffmpeg | A compatible ASI receiver/driver must expose a decodable MPEG-TS stream, file or network input |
| Remote agent/capture host | mjpeg | Run the authenticated capture sidecar beside the agent; panel proxies its feed |
| HLS | hls | Browser reads an HTTPS/CORS-enabled playlist and segments; native HLS or bundled hls.js |
| WebRTC | whep | Panel proxies WHEP signaling; media travels between browser and the configured gateway |
| VNC | vnc | Panel bridges TCP VNC or a configured VNC WebSocket to bundled noVNC, view only |
| Proxmox QEMU VM | proxmox | Panel obtains a login ticket and per-VM VNC ticket, then proxies the authenticated console WebSocket |
| Hyper-V / ESXi / vSphere | vnc or embed | Guest VNC, or an existing embeddable console gateway such as a configured Guacamole/WebMKS application |
Hyper-V VMConnect and vSphere console-ticket APIs are not native adapters in this version. A vendor management dashboard URL is not automatically an embeddable console. The gateway must supply the actual viewer, handle its own session/ticket flow, and permit framing by Sysavia. Embedded gateways may expose interaction: configure their own view-only policy. Direct VNC/Proxmox players are view only in Sysavia.
FFmpeg/MJPEG previews are video only, default 640 px wide at 8 fps. Configure width (160–1920) and fps (1–30) per source. Resizing a window scales its picture; it does not change capture resolution. For motion-critical monitoring, full frame rate or audio, supply an HLS or WHEP feed. Browser videos start muted; controls allow unmuting where the source includes audio. Codec compatibility still depends on the browser. There is no recording, transcoding cluster, ONVIF discovery, freeze detection, black-frame alarm or visual-content trigger in this version.
Remote capture beside an agent
Install the repository dependencies and FFmpeg on the capture machine. Configure a local source:
{
"sources": [{
"id": "program",
"name": "Program capture",
"kind": "ffmpeg",
"inputArgs": ["-f", "v4l2", "-i", "/dev/video0"],
"width": 960,
"fps": 12
}]
}
Set MEDIA_CONFIG, MEDIA_HOST_TOKEN (a random secret at least 24 characters), and optionally MEDIA_HOST_PORT (3041) / MEDIA_HOST_BIND (127.0.0.1). Run:
npm run media:host
Use an HTTPS reverse proxy on that host with buffering disabled. In the panel, create an MJPEG / remote capture source with the HTTPS URL ending in /api/media/program/stream and enter the capture host token in Bearer token. The sidecar only serves configured feeds; it does not accept arbitrary URLs or capture commands. It is a separate process beside the agent, not a new agent heartbeat payload. Windows capture devices must be accessible to the service account; interactive desktop capture is subject to session isolation.
The panel must be able to reach this capture host. This is a pull relay, not an outbound NAT-traversing agent tunnel. A camera behind a switch similarly requires routable IP access, camera credentials and a supported media endpoint. Switch topology alone does not reveal or carry a playable camera feed.
Console and browser media details
- Proxmox: configure a dedicated account with
VM.Consolepermission on the specific VM, its realm-qualified username, password, node and QEMU VM ID. The adapter uses password login, not an API-token or interactive MFA flow. Trust the Proxmox CA using Node'sNODE_EXTRA_CA_CERTSif needed; TLS verification stays enabled. LXC terminal consoles are not handled by this graphical player. Proxmox behavior is tested against a protocol fixture, not live hardware in this environment. - VNC: use
hostandport, optionalusername/password; orwebsocketUrlwith optionalheadersandwebsocketProtocols. The panel must reach that endpoint. noVNC needs credentials in browser memory to complete RFB authentication; they are never saved in the workspace. Use read-only VNC credentials where available. Only the UI is view-only; this unauthenticated development panel is not a console authorization boundary. - HLS: source and segment hosts must permit browser CORS. HTTPS panels need HTTPS media URLs. URLs are sent to the browser, so do not put long-lived secrets in query strings. Per-request secret headers are not supported for browser-direct HLS.
- WHEP: use a WHEP endpoint, not an arbitrary RTC page. Configured
headersare resolved server-side. Advanced operator configuration can supplyiceServers, which uses the standard RTCPeerConnection configuration (STUN/TURN); TURN credentials are visible to the browser. UDP/TCP media reachability and gateway ICE candidates must be configured independently of the Nginx signaling proxy. The implementation gathers ICE before posting an offer; it does not implement trickle-ICE PATCH or automatic session renewal. Retry opens a fresh session. - Embed: only trusted, configured HTTP(S) viewer pages can be selected. Their frame policies and authentication must support embedding. An iframe loading does not prove the underlying signal is live; the UI reports “Viewer loaded.”
Playback lifecycle and troubleshooting
Changing grid, hiding a browser tab, entering Simulate, disabling/removing a window, or leaving the page releases its player. Returning to a visible grid starts a fresh player unless you manually paused that placement. Multiple visible FFmpeg viewers on one source share one process. After its last viewer leaves, FFmpeg is stopped after a 250 ms grace period; stalled captures stop after 15 seconds without frames. A visible copy in another grid/browser keeps its shared capture alive. HLS instances, VNC sockets and WebRTC peers are destroyed on hide; WHEP session deletion is attempted. An upstream gateway may keep its own ingest running independently of Sysavia viewers.
Routine monitoring updates retain player DOM and do not reconnect feeds. Failures show “Unavailable,” “Feed ended,” or “No recent frames”; Retry reconnects explicitly. Playback state is separate from service health and does not claim that a documented cable or monitor is working. Stream ingestion needs CPU and network capacity; begin with low-resolution previews before increasing frame rate or source count.
When using a reverse proxy, verify buffering is off and VNC WebSocket upgrades are passed through. FFmpeg stderr is drained without logging input URLs because these may contain credentials. To diagnose an input failure, run the corresponding FFmpeg input locally on its host using appropriate secret handling. Never paste a credential-bearing FFmpeg command into a shared log or issue.
References: FFmpeg input devices, noVNC API, Proxmox API, MediaMTX WebRTC/WHEP.
Browser dependencies are bundled locally: noVNC (MPL-2.0), hls.js (Apache-2.0), esbuild (MIT). Their upstream license notices remain in the installed packages and bundle.
Hardware Controller Consoles
Choose Dell iDRAC, HPE iLO or Supermicro in Media Sources. Enter the visible HTTPS controller URL, management credentials and any manager-path override. Dell also requires the separately configured VNC password and an already enabled VNC service. It appears in ordinary movable playback windows and can route through a site collector. TLS remains verified when enabled by iDRAC.
HPE and Supermicro use an Open Native Console button. These open the vendor viewer in a new tab; the browser must reach the controller. HPE requires its native login. Supermicro obtains a fresh launch token; use Retry to request a new link if it expires. Selecting a collector obtains the session through that collector but does not proxy the vendor web UI. Native launch sources are not live in-grid video. See Vendor Console Adapters.