Applies to Models: Wave external API usage
Transcoding is taking compressed or encoded content, decompressing or decoding it, modifying it somehow, and re-compressing or re-encoding it. The most common scenario is decreasing the resolution and bitrate/framerate. Sometimes this can include changing a video or audio format from one to another (e.g, MJPEG to H264), or adding watermarks to the video.
Note: Please be aware of the potential CPU overload. We don't recommend
increasing this value unless your hardware is suitable for the task.
Explanation of Behavior:
- A transcoding session is one instance of this process, so when you need to transcode multiple things, you can have multiple sessions to transcode simultaneously
- This session is initiated when the GET/media/<cameraId>.<format> API call is made with WEBM and MPJPEG format AND links with a custom resolution parameter
- Since Wave 4.0, a default limit has been put in place of no more than two simultaneous transcoding sessions.
- The two transcoding limits were put in place to avoid CPU overload issues often observed at sites with progressive download enabled
- As a result, this change may break some integrations which relied on more than two simultaneous transcoding sessions
Administrator-level permissions are required to make the change
- Modify the following address and enter it into your browser:
- To increase this limit, on the advanced settings page, search for (See Figure 1)
Modify the value of the maxHttpTranscodingSessions parameter
Click Save to confirm your changes
Restart the Wave server