If you do not wish send multiple streams via a Media Encoder, you can publish a single high-quality stream to the an autoscale Transcoder node which will handle transcoding the stream into the additional variants.

Once the Provision is posted and stored on the Stream Manager, you will need to request the transcoder endpoint to broadcast the single stream to.

The Stream Manager API to request the transcoder endpoint is the same as the API to request an origin endpoint, with the addition of &transcode=true query parameter. In following with the examples from this document, that would look like:

https://yourstreammanager.com/streammanager/api/4.0/event/live/mystream?action=broadcast&transcode=true

Note that the stream name is the GUID of the stream Provision, and not a stream name of one of the variants. You will broadcast with a variant stream name, but this call to request the transcoder endpoint required the GUID.

The response JSON has the same structure as the response to request an Origin endpoint. You will use the serverAddress and scope of the response to start a publishing session. How that is assigned to each publisher type of the Red5 Pro WebRTC SDK differs in each solution (WebRTC and Flash/RTMP). This is detailed in the following subsections.