...
1.1. If there is the stream with such name on Transcoder node in the same group with Edge:
1.1.1. If the strea, stream is already transcoded by this profile, Edge pulls the stream from Transcoder
...
- stream1, stream2, stream3 – streams published to Origin server
- stream1-P1 – stream1 stream transcoded by settings profile P1
- stream2-P1 – stream1 stream transcoded by settings profile P2
Node groups and transcoding
By defautl, Edge will choose Transcoder in the same group to transcode the stream by profile. For example, if CDN has two segments grouped by location: in Europe and USA, then stream translation for the stream by one profile from every group looks as follows:
In this case, only one stream will be broadcast from Origin to each group, this decreases intergroup channels load, but stream will be transcoded in every group independantly.
This behaviour can be changes with the following parameter
Code Block | ||
---|---|---|
| ||
cdn_group_origin_to_transcoder_relation=true |
Then Transcoder in the same group with Origin will be chosen promarily to transcode the stream, and stream translatiion will look as follows:
In this case, the stream is transcoded one time for all location groups, but as many streams will be broadcast to each group as requested by Edges for playback. This inscreases intergroup channels load.
Getting stream routes information with REST API
...