Introduction
1. Terminology
| Term | Definitions |
|---|---|
| WebAssembly | WASM is a new format that is portable, compact, fast-loading, and web-compatible. It allows native code (e.g., C, C++) to run in the browser. |
| HTTP-FLV | Short for Flash Video Over HTTP, it is a protocol for transmitting FLV audio and video data over HTTP. |
| MSE | Short for Media Source Extensions, it is a new web interface supported by major browsers like Chrome, Safari, and Edge. It allows JavaScript to play media streams. |
| WEBCODECS | WEBCODECS is an API that provides video encoding and decoding capabilities in web browsers. Proposed by the W3C, it aims to simplify video processing tasks on the web, such as post-processing and video editing. |
2. Features
- It is a pure HTML5 player. No plugins are required.
- It supports MSE, WASM, and WEBCODECS decoding methods, with dynamic switching based on browser support.
- It supports media stream AES encryption play.
- It is compatible with H264 and H265 encoding formats.
- The built-in plugin mechanism allows for features like electronic zoom-in, intelligent mosaic, and AI capability display to be enabled freely.
3. Function List
3.1. Live View
Play, destroy, switch between main and sub-streams, and reconnect after disconnection.
3.2. Playback
Play (multi-channel/single-channel), destroy (multi-channel/single-channel), stop, replay, switch between main and sub-streams, speed (0.25, 0.5, 2, 4, 8), and seek.
3.3. Video Functions
Volume control, aspect ratio, full-screen channel, electronic zoom-in, AI mosaic, AI information display, video information display, screenshot, and more.
3.4. Intercom
Start, stop, retrieve intercom duration information, and control play volume.
3.5. Listening
Start, stop, obtain listening duration information, and control play volume.
4. Compatibility
H5Player uses MSE, web worker, WebGL, and canvas technologies, which require modern browsers. Supported browser versions include:
- chrome 97+
- firefox 100+
- safari 13.1+
Note: Mobile and tablet adaptations are not yet available.
5. Performance
5.1. Test Data
Test environment: Win10 Professional
Test host: 12th Gen Intel(R) Core(TM) i7-12700F 2.10 GHz
Test scenario: The number of channels supported in a single device (up to 32 channels).
| Business Items | Special Conditions | Test Results |
|---|---|---|
| First screen delay | Less than 500 milliseconds (LAN) | |
| Play delay | WEBASSEMBLY/WEBCODECS modes | Less than 500 milliseconds (LAN) |
| Play delay | MSE mode | Less than 1 second (LAN) |
| Concurrent channels (H.264) | WEBASSEMBLY mode (image quality 1, 25 FPS, CPU usage under 85%) | 16 CIF channels, 16 D1 channels, 12 720P channels, 8 1080P channels |
| Concurrent channels (H.264) | MSE mode (image quality 1, 25 FPS, CPU usage under 85%) | 32 CIF channels, 32 D1 channels, 32 720P channels, 26 1080P channels |
| Concurrent channels (H.264) | WEBCODECS mode (image quality 1, 25 FPS, CPU usage under 85%) | 32 CIF channels, 26 D1 channels, 32 720P channels, 22 1080P channels |
| Concurrent channels (H.265) | WEBASSEMBLY mode (image quality 1, 25 FPS, CPU usage under 85%) | 16 CIF channels, 16 D1 channels, 10 720P channels, 7 1080P channels |
| Concurrent channels (H.265) | MSE mode (image quality 1, 25 FPS, CPU usage under 85%) | 32 CIF channels, 30 D1 channels, 32 720P channels, 24 1080P channels |
| Concurrent channels (H.265) | WEBCODECS mode (image quality 1, 25 FPS, CPU usage under 85%) | 32 CIF channels, 24 D1 channels, 32 720P channels, 18 1080P channels |
For detailed performance information, please refer to: V2.0.0 Performance Test.
5.2. Decoder Comparison
| Decoder | Delay | Performance | Compatibility | Mosaic Security |
|---|---|---|---|---|
| WEBASSEMBLY | Low | Low | High | High |
| MSE | High | High | Medium | Low |
| WEBCODECS | Low | Medium | Low (Chrome v1.0.9 and above) | High |
6. Installation and Deployment
Internal users: Use the CICD management system for installation and deployment.
External users: Please contact the relevant technical support services and apply for external release through the internal OA system.
Note: When external customers connect to H5Player, the technical support should consider the following points:
-
The industry needs to provide the token obtaining method or customer sign information, which must be passed in the header for authentication
-
Customers integrating H5Player need to use devId, and the industry needs to provide a way to obtain devId
-
the user needs to provide their own domain name to inform the industry to allow cross-domain