...
In this case, if the stream is transcoded at the same Transcoder node by those two profiles, only one video encoder and two audio encoders will be used.
Transcoding to higher resolutions prevention
Since build 5.2.607, stream transcoding to higher resolutions can be escaped. The feature can be enabled with the following parameter
| Code Block | ||
|---|---|---|
| ||
cdn_strict_transcoding_boundaries=true |
In this case, if a stream is published to Origin with resolution 640x480, and Edge server tries to request playback by 720p profile, Edge will receive an original stream directly from Origin without transcoding. Resolutions are compared by height.
Stream requesting by higher resolution profiles can be strictly forbidden with the following parameter
| Code Block | ||
|---|---|---|
| ||
cdn_strict_transcoding_throws_exception=true |
When, if a stream is published to Origin with resolution 640x480, and Edge server tries to request playback by 720p profile, Edge can not choose stream playback route and will return error to a client.
These parameters should be set on Edge server.
Known limits
1. If stream transcoding to higher resolutions is disabled, a stream height must be set for every profile.
Choosing a route for stream playback
...
In these cases transcoding works according to codecs and SDP setup as defined for CDN 2.0.
Known limits
1. It is strongly not recommended to publish streams with same name to two Origin servers in the same CDN.
...