How to configure error correction and calculate bandwidth on the MPX Node
This document covers how to configure error correction on the Omnia MPX Node Encoder and calculate the total amount of bandwidth required to use it.
Configure Error Correction
How to set error correction controls
MPX Node Encoder has two controls to adjust error correction. (The Decoder is a follower, and has no error correction settings of its own). "Error Correction size/delay" defines the span over how many packets the recovery data will be sent, and "Error Correction Overhead" sets the number of error correction packets that are sent for a given "Error Correction Size/Delay" value. As an example, if we set the "Error Correction Size/Delay" to 64 packets, and the "Error Correction Overhead" to 8 Packets, we could lose 8 packets without an audible problem. As a rule, Overhead packets should never exceed Size/Delay and the sum of both fields should never exceed 255.
What is the proper amount of error correction?
How much error correction depends on the quality of the link the stream is trying to traverse. Ultimately the goal is to use as little error correction as possible while maintaining seamless audio playback. Some common settings we have found to work well are listed below.
Error Correction Size/Delay
Error Correction Overhead
Error correction's effect on bandwidth
Utilizing the advanced error correction found in the Omnia MPX Node requires additional bandwidth. The amount of additional bandwidth needed by error correction is a percentage of the bitrate in use. Adjusting "Error Correction size/delay" and "Error Correction Overhead" dynamically affects this percentage. Below is a calculator to determine how much bandwidth is required to pass a stream, and how much data a stream consumes over time. For more information, refer to the user manual.
|MPX Node Bandwith Calculator|
|Error Correction Span|
|Error Correction Overhead|
|Bandwidth required for transmission||...|
|Data utilized (per MPX Node Decoder)|
Let us know how we can help
If you have further questions on this topic or have ideas about how we can improve this document, please contact us.