Important encoding issues that affect Wowza Streaming Engine software

This article describes important encoding issues that may affect your deployment and management of Wowza Streaming Engine™ software. If available, workarounds for these issues are described. Check back often as this article will be updated as new developments occur.
 

Note: Where a third-party issue affects Wowza Streaming Engine software, it's the responsibility of the third-party to fix the problem. Wowza Media Systems works with these companies to help address the issue as soon as possible.

Contents


Known encoding issues in Wowza Streaming Engine More resources

Known encoding issues in Wowza Streaming Engine


Memory leak when transcoding with transparency overlays (Wowza Streaming Engine 4.5.0.01 and 4.5.0.02)

If you include graphic overlay images when transcoding streams and you set the overlay opacity value to less than 100 (completely opaque), or you use a file for your overlay image that was originally created with less than 100 percent opacity, a memory leak occurs. Our findings also show that the memory leak is larger for larger overlay image files.
 

Solution


We hope to have a fix for this issue in the next Wowza Streaming Engine software update.

Metadata from Matrox Monarch HD encoders can't be processed by Akamai stream targets

The Matrox Monarch HD encoder sends metadata with encoded streams that goes through Wowza Streaming Engine but can't be processed when received by an Akamai RTMP CDN endpoint.
 

Solution


Add a custom property to the stream target that instructs the target to to ignore the problematic metadata.
 
Note: Creating custom properties for a stream target requires an administrator user with advanced permissions.
  1. In Wowza Streaming Engine Manager, select the live application that uses the Matrox Monarch encoder and the Akamai RTMP stream target.
     
  2. In the contents panel, click Stream Targets.
     
  3. Select the stream target that's sending the stream to Akamai.
     
  4. Click the Custom tab, click Edit, and then click Add Custom Property.
     
  5. In the Add Custom Property dialog box, specify:
     
    • Name - removeMetadataObjects
    • Type - Boolean
    • Value - true
  6. Click Add and then click Save.

GOP size limitation for encoding presets when using default (software) encoder (Wowza Streaming Engine 4.4.1 and later)

In Wowza Transcoder, an encoding preset option you can specify is to align the keyframes in the transcoded output rendition with the keyframes in the incoming source stream (this is required for transrating an incoming source stream). In Wowza Streaming Engine Manager, you do this by setting the Key Frame Interval option to Same as source (required for transrating) for an encoding preset. In the template XML file, this setting is configured by the <Video>/<KeyFrameInterval> setting with <FollowSource> set to true for the encode block.
<KeyFrameInterval>
    <FollowSource>true</FollowSource>
    <Interval>0</Interval>
</KeyFrameInterval>
In Wowza Streaming Engine 4.4.1 and later, if you set the keyframe interval of the transcoded video to be the same as the source video, and you select the Default Encoding Implementation to use the built-in MainConcept software encoder, the Transcoder will add extra keyframes to the output rendition that don't match the incoming stream IF the incoming stream's GOP (number of frames between keyframes) size is more than 300. This issue occurs for both H.264 and H.265/HEVC incoming streams with encoded keyframe intervals greater than 300.
 

Solution


We hope to address this issue in a future Wowza Streaming Engine software update.

Potential SEGV crash on Linux with the H.265/HEVC default (software) decoder

An issue on Linux with the H.265/HEVC default (software) decoder (part of the Transcoder) can lead to an SEGV crash. The issue is caused by the order in which shared libraries are loaded when the Transcoder starts.
 

Solution


You can address the issue by forcing the Java signal handler to be loaded on Java startup. To do this, open the /usr/local/WowzaStreamingEngine/bin/setenv.sh file in an editor, and then near where the _EXECJAVA variable is set, add a line setting the LD_PRELOAD environment variable to the full path to the $JAVA_HOME/lib/amd64/libjsig.so file. For example:
if [ -d /usr/local/WowzaStreamingEngine/java ]; then
    WMSJAVA_HOME=/usr/local/WowzaStreamingEngine/java
    _EXECJAVA=$WMSJAVA_HOME/bin/java
    export LD_PRELOAD=$WMSJAVA_HOME/lib/amd64/libjsig.so
else
    _EXECJAVA=java
fi

Wowza Streaming Engine generates malformed XML encoding profile for integrated encoders

The XML encoding profile that Wowza Streaming Engine generates is missing the outer wrapper element (<encoder_profile>). This can cause to the following integrated encoders to fail to parse the file:
 
  • Epiphan Pearl
  • Hauppauge StreamEez-Pro
  • Matrox Monarch HD
  • NewTek TriCaster
  • Telestream Wirecast
 

Solution


Wowza has fixed this issue in the latest Wowza Streaming Engine software update. To get this update, sign in to your Account Management page using your Wowza account and then check the My Downloads tab. You must have an active Maintenance and Support contract to receive updates.

Streams delivered from JVC camcorders over RTSP may not work properly

JVC camcorders that connect to Wowza Streaming Engine using RTSP/RTP transport mode either can't deliver live streams or deliver live streams with poor quality.
 

Solution


This problem is due to an issue in JVC camcorder firmware. We recommend that you configure your camcorder and the JVC source page in Wowza Streaming Engine Manager to use the MPEG-TS/UDP connection type. We will replace the RTSP/RTP connection type option in the manager with a new connection type option in a future release of the Wowza Streaming Engine software.

NVIDIA NVENC hardware-accelerated encoding doesn't work with Wowza Streaming Engine 4.2.0

An issue in Wowza Streaming Engine 4.2.0 software prevents NVIDIA hardware from being recognized; therefore, NVIDIA NVENC hardware-accelerated encoding can't be enabled for Wowza Transcoder.
 

Solution


Wowza has fixed this issue in the latest Wowza Streaming Engine software update. To get this update, sign in to your Account Management page using your Wowza account and then check the My Downloads tab. You must have an active Maintenance and Support contract to receive updates.

NVIDIA hardware-accelerated decoding doesn't work with Wowza Streaming Engine on Windows 10 with Java 8

NVIDIA accelerated decoding fails on windows 10 with Java 8. The failure occurs when you use CUDA or NVCUVID acceleration for decoding (NVENC acceleration seems to work).
 

Solution


Use Java 7 on Windows 10 to avoid this issue. For information on installing Java, see How to manually install and troubleshoot Java on your Wowza media server. NVIDIA is investigating this issue.

More resources



Originally Published: For Wowza Streaming Engine on 05-20-2015.
Updated: 10-12-2016.