| Expand | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||
|
...
See this page for more information about modifying the latency of audio or video streams.
WebRTC
...
Native Chrome Media Player
Series 5 players support selecting native Chrome for video playback with hardware acceleration or using the default BrightSign Media Player for video playback. You can pick which option is best for your use case (see HTML Playback Options on Series 5 Players). Note that hardware accelerated video for native chrome playback is not yet available on any Series 5 player other than the XC5.BrightSign does not support hardware-accelerated decode of WebRTC on Series 4 or lower
WebRTC
For WebRTC, BrightSign OS always uses native Chrome video playback.
Series 5 players, running OS 9.0.115 and later, will automatically use hardware-accelerated decode in this case.
Series 4 and older players do not support hardware-accelerated decode with native Chrome video playback. As such, the decode will be done in software, and we only recommend trying this approach with XT4 players.
Intrinsic Video Size
...
| Code Block |
|---|
registry write html mse-support 1 |
HLS Live Streaming
BrightSign players support HLS live streaming, but large playlists (which usually result from the server delivering a DVR playlist rather than a LIVE playlist) will cause performance issues.
...
auto: If the video player is currently not showing anything (i.e. it hasn't played anything yet or the previous loaded video was cleared), the next video will fade in. If the video player is currently playing video, is paused, or is stopped without being cleared, the next video will not fade in. This is the default behavior.always: When a video ends, the video window will go black. The new video will then fade in.never: Videos transition without fade effects.
HWZ Video Transparency Extensions
If "hwz" is enabled for a <video> element, the video window can also support luma and chroma keys for video transparency. The z-index: parameter must also be specified for transparency to work. The luma and chroma keys are specified as follows:
luma-key:[HEX_VALUE]cr-key:[HEX_VALUE]cb-key:[HEX_VALUE]
Example
| Code Block |
|---|
// Video on video layer, in front of graphics layer, with luma keyed video. <video src="example_movie.mp4" hwz="z-index:1; luma-key:#ff0020;"> |
...
To select a decoder in BrightScript, pass an associative array to the roVideoPlayer.PlayFile() method containing the decoder:[friendly_name] parameter:
|
To select a decoder for HTML video, include the decoder:[friendly_name] property with the hwz attribute:
|
The max_usage of a decoder determines how many video players can be assigned to the decoder using the system software algorithm described above—video players beyond the max_usage limit may be assigned to another decoder or not displayed at all. On the other hand, if you manually assign video players using the friendly_name of the decoder, you can assign more video players to the decoder than the max_usage limit, but this may cause unpredictable video-display behavior.
...