Stream transcoding

Change audio/video codecs, formats and bitrate of streams automatically and by REST request

Video stream transcoding is automatically enabled in one of the following cases:

• The codecs of the streamer and player do not match by name.
• H.264 codecs differ in the packetization-mode parameter.
• The resolution of the player is explicitly indicated.
• Explicitly specified player bitrate.

In addition, transcoding can be forced on the server. Turning off transcoding does not affect the mixer; when using a mixer, transcoding will be turned on.

Transcoding significantly increases the consumption of server resources (processor cores). Therefore, it should be turned on with caution!

Transcoding can be controlled using the REST API.

Specifications

Transcoding Scheme

The WCS server receives the video stream from the video stream source, changes the encoding parameters and transmits the transcoded stream to player (for playback).

Step-by-step diagram of transcoding with REST API control

1. Web Call Server receives audio/video stream
2. REST client makes a request for transcoding the stream with the necessary parameters
3. Web Call Server sends the transcoded stream to browser for playback

For more information on testing transcoding, see page Testing

Download Web Call Server 5

System requirements: Linux x86_64, 1 core CPU, 2 Gb RAM, Java

    Download Now    

Installation:

1. wget https://flashphoner.com/download-wcs5.2-server.tar.gz
2. Unpack and install using 'install.sh'
3. Launch server using command 'service webcallserver start'
4. Open the web interface https://host:8444 and activate your license

If you are using Amazon EC2, you don't need to download anything.

Launch WCS5 on Amazon EC2