Insert a video template from the library and choose its playback type and connection in Template Edit. The runtime must be able to access the media. Playback URLs and host media channel codes serve different purposes.
1. Select a playback type
Choose Video File / Recording (Seekable) or Camera / Live Video under Video Type. On-demand offers duration, seeking, and playback speed. Live playback provides live status, return-to-live, and reconnect controls. HLS and DASH can carry either type; select according to the media service.
- Set X, Y, Width, and Height in Position and Size.
- On-demand options include Autoplay When Opened (Muted) and Loop Playback.
- Live connections start muted and do not use file looping or playback-speed options.
- Pasting a new address does not change the selected playback type.
2. On-demand media and deployment
In File or Playback URL, enter an HTTP / HTTPS media URL accessible to the runtime, such as https://media.example.com/training/pump-operation.mp4. A website player page is not a direct media URL. A local file selected with Browse… is not copied into the screen package and blocks export. Deploy media you are authorized to use to a location accessible from the runtime, then enter its HTTP(S) playback URL before exporting.
3. Use a Mingcedar media channel
Select Camera / Live Video, then Host Camera (Configure or Select) under Playback Source. Click Configure / Select Camera… to configure, check, and select a camera, or enter an existing camera Code in Channel Code. The display name cannot replace the code.
- Channel code example:
camera_line01.
- You may also enter
hqmedia://camera_line01; both forms save the same channel reference.
- No host IP is required in the template. Configure the same channel code when publishing to another host.
- Configure camera RTSP / RTMP URLs and credentials in the host, not in public template examples.
4. Use a direct media URL
For a browser-playable live address, select Direct HTTP(S) Playback URL under Playback Source and enter the media address in HTTP(S) Playback URL. Supported integrations include HLS, MPEG-DASH, HTTP-FLV, WHEP, MJPEG, and browser-native media. Availability still depends on the service, codecs, browser, and network.
- Example URL:
https://media.example.com/line01/live.m3u8.
- Camera administration pages and RTSP or RTMP URLs are not browser-playable media URLs.
- Use HTTPS media on an HTTPS runtime page and meet cross-origin access requirements.
- Example domains illustrate the format. Use the actual address of an authorized project media service.
5. Verify after publishing
In the target Mingcedar environment, verify initial playback, leaving and returning to the page, network recovery, and screen visibility. The runtime releases player connections when leaving a page and creates them again on return. If playback fails, record player messages, channel status, and media request results, then check URL expiry, certificates, connectivity, and codec support.
Configure or select a camera from the add-in
Select Camera / Live Video and Host Camera (Configure or Select), then choose Configure / Select Camera… to open Camera Configuration. Enter an existing Channel Code directly or select a camera in this window.
- Enter Host Address, Host Username and Host Password, then Connect and Load Cameras with a host administrator account. The address, password and session stay in this window and are not written to the PPT or export.
- Selecting an existing camera only reads configuration. New Camera creates one. Camera Code accepts 1–64 letters, digits, underscores or hyphens, beginning with a letter or digit; it cannot change after saving.
- Camera Source URL accepts a device RTSP, RTMP or HTTP(S) media URL, unlike the browser-direct template field. Camera URL Assistant combines a preset, RTSP/RTSPS, address, port, device channel and main/substream; verify the actual device format.
- Enable Camera controls availability; Connect Only While Viewing controls on-demand connection. Save to Host saves, Apply and Check applies and checks, Preview in Browser previews, and Refresh reloads host state.
Camera credentials and commit boundaries
Camera Credentials are separate from the host login. Save the camera, save Camera Credentials, then use Save to Host again to bind them. The PPT stores only the channel reference.
- Save to Host, Apply and Check and Delete Camera submit host changes immediately. Cancelling the template editor does not undo them.
- Use Selected Camera returns the code to the template; Save in the template editor writes that reference to the PPT.
- Delete Camera removes host configuration, so verify its code and impact. Back returns to the template and Sign Out ends the host session.
- Cancel Wait stops waiting; it does not undo a submitted request. If the outcome is uncertain, Refresh and inspect actual state before acknowledging the review prompt and making another change.
