To migrate a Wowza Streaming Engine™ media server software encoding configuration with advanced Beamr video encoding parameters (<Encode>/<Video>/<Parameters>) from Beamr to MainConcept, you need to manually update advanced parameter names and values to work with MainConcept.
This article provides a mapping of advanced Beamr encoding parameters to equivalent or similar MainConcept encoding parameters. Details are included to help you adjust your parameter configuration for MainConcept.
Notes:Wowza Streaming Engine 4.8.22 or later is required to use MainConcept as the default encoder and decoder. Advanced MainConcept decoding parameters are available.
Identify Beamr video encoding parameters
First, identify if you have any advanced Beamr video encoding parameters configured. Open your Transcoder template and look for parameters beginning with beamr within the <Video>/<Parameters> container element in all H.264 or HEVC/H.265 encoded output renditions (<Encodes>/<Encode>) that you want to migrate to using MainConcept. For example, you may see a similar setup:
<Encode>
...
<Video>
...
<Parameters>
<Parameter>
<Name>beamr4.bframes</Name>
<Value>1</Value>
<Type>Integer</Type>
</Parameter>
</Parameters>
</Video>
...
</Encode>
Replace Beamr parameters with MainConcept parameters
The following table maps some common Beamr H.264 encoding parameters to equivalent or similar MainConcept H.264 encoding parameters.
This is not a complete list of advanced Beamr encoding parameters. If your Transcoder template includes Beamr encoding parameters that are not listed in the table, we recommend logging available MainConcept encoding parameters to identify possible replacements according to the instructions in Use video encoding parameters with the Transcoder in Wowza Streaming Engine.
To replace an existing Beamr parameter with a MainConcept parameter, edit the parameter name (<Name>) to use the MainConcept name. For some parameters, you also need to update the parameter value (<Value>).
Wowza Streaming Engine 4.8.22
With Wowza Streaming Engine 4.8.22, you need to manually update your encoding configuration for MainConcept if it uses any advanced Beamr parameters. Refer to the following notes for information about when and how to update each parameter's values.
| Beamr name | MainConcept name | Notes |
|
beamr4.kbps |
mainconcept.bit_rate |
Multiply the value used for beamr4.kbps by 1000 to get the equivalent value for mainconcept.bit_rate (mainconcept.bit_rate = beamr4.kbps x 1000).Note: The bitrate can also be configured using the Bitrate property (bps) within <Encode>/<Video> instead. This parameter overrides the value of Bitrate. |
|
beamr4.rc_type |
mainconcept.bit_rate_mode |
|
|
beamr4.keyframes |
mainconcept.idr_interval |
No change to <Value> needed.Note: The keyframe interval can also be configured using the KeyFrameInterval properties within <Encode>/<Video> instead. This parameter overrides the value of the KeyFrameInterval properties. |
|
beamr4.level_idc |
mainconcept.level_id |
No change to <Value> needed.Note: The H.264 level can also be configured using the Profile property within <Encode>/<Video> instead. This parameter overrides the value of Profile. |
|
beamr4.max_kbps |
mainconcept.max_bit_rate |
Multiply the value used for beamr4.max_kbps by 1000 to get the equivalent value for mainconcept.max_bit_rate (mainconcept.max_bit_rate = beamr4.max_kbps x 1000). |
|
beamr4.max_refs |
mainconcept.num_reference_frames |
No change to <Value> needed. |
|
beamr4.bframes |
mainconcept.reordering_delay |
Add one from the value used for beamr4.bframes to get the equivalent value for mainconcept.reordering_delay (mainconcept.reordering_delay = beamr4.bframes + 1). Note: By default, this value is set to 1, which doesn't allow for the insertion of B-frames. To allow B-frames to fit, a higher value must be configured. For more, see Configure B-frame generation in Wowza Streaming Engine. This parameter only works with AVC/H.264 encoding. |
|
beamr4.aud |
mainconcept.write_au_delimiters |
No change to <Value> needed. |
