As a reader may know UDP network protocol does not support either message retransmission or acknowledge. It means that all these problems are supposed to be handled at the application level. In audio/video transmission domain the problem is usually solved with forward error correction technique. The idea is to add some redundant data to a message or messages so that if one of the messages is lost, a receiver could replicate it form combination other messages and the redundant data. This redundant data is called FEC.
A developer is supposed to decide how much FEC to add to the messages at the encoder side and how to decode it at the decoder side. It sounds like a piece of work! So Opus codec developers decided to make our life easier and added in-band FEC support to the codec.
In order to make OPUS encoder to add FEC a user has to set the following configuration:
- Packet time(
ptime) has to be not less than 10ms otherwise OPUS works in the CELT mode and not in SILK.
- Don’t use very high bitrates. For example, I use 24 kbps.
- In order to use FEC, your bitrate should be higher. For example, if sample rate is 8kHz then bitrate has to be 12 kbps or 24 kbps. The encoder needs higher bitrate to have a room for LBRR packets containing FEC.
- FEC must be enabled via
- The encoder must be told to expect packet loss via
Here is the example of configuring OPUS encoder.
1 2 opus_encoder_ctl(encoder, OPUS_SET_INBAND_FEC(TRUE)); opus_encoder_ctl(encoder,OPUS_SET_PACKET_LOSS_PERC(opus_packet_loss));
opus_packet_loss via config file but it may be configured in realtime.
For example, you can update OPUS according to RTCP
Now, after the encoder is ready, let’s configure the decoder. First of all, you need to know if a packet is lost. The most natural way to know it is to check the sequence number of RTP packets. When you know that the previous packet is lost you are supposed to decode the current packet twice: first time with FEC turned on to reproduce the lost packet, and then with FEC turned off to decode the current packet.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 /* Decode the lost packet */ opus_decoder_ctl(decoder, OPUS_GET_LAST_PACKET_DURATION(frame_size)); opus_decode( decoder, buffer, /* buffer to decode */, length, /* number of bytes in buffer */ sampv, /* output buffer */ frame_size, 1); /* in-band FEC is turned on */ play_buffer(buffer); /*Decode the current packet*/ opus_decode( decoder, buffer, /* buffer to decode */, length, /* number of bytes in buffer */ sampv, /* output buffer */ frame_size, 0); /* in-band FEC is turned off */ play_buffer(buffer);
We learned how to enable in-band FEC for Opus codec but the last thing to talk about is the pros and cons of using it!
- No need to develop an inhouse mechanism of adding FEC to your packets.
- Most of the third parties like SIP servers(Asterisk) or WebRTC support Opus in-band FEC out of the box.
- FEC may increase the audio quality even when there is a packet loss.
- Tricky to configure.
- There is no obvious way to see if traffic actually carries in-band FEC except generating packet loss and listening to
an audio sample. I used a sine wave generated by:
ffmpeg -f lavfi -i "sine=frequency=1000:sample_rate=8000:duration=5" output.wav.
- Since Opus packet contains information only about the prior packet in-band FEC can replicate only a single packet loss. The problem is that usually packets are lost in a burst.
- Enabling FEC increases bitrate and bandwidth.