Wowza Streaming Engine 4.7.7 Release Notes

Important: A newer version of Wowza Streaming Engine is available. For more information, see Latest software updates for Wowza Streaming Engine.

Version: Wowza Streaming Engine™ 4.7.7 build 20181108145350 released on November 13, 2018.
Note: For step-by-step instructions on how to update your Wowza Streaming Engine media server software, see Update your Wowza Streaming Engine installation.


New features and functionality in Wowza Streaming Engine 4.7.7
Detailed list of changes in Wowza Streaming Engine 4.7.7
Detailed list of changes in Wowza Streaming Engine updater

New features and functionality in Wowza Streaming Engine 4.7.7

Wowza Streaming Engine is robust, customizable, and scalable media server software that powers reliable streaming of high-quality video and audio to any device, anywhere. Wowza Streaming Engine 4.7.7 contains several fixes and enhancements that help to improve the functionality of the media server software.

Support for WebRTC

WebRTC is an open-source real-time communication project. In earlier versions of Wowza Streaming Engine, WebRTC support was considered a preview feature and had limited functionality. With Wowza Streaming Engine 4.7.7 and later, WebRTC is fully supported and includes significant enhancements to the preview functionality. For more information, see Use WebRTC with Wowza Streaming Engine.

nDVR enhancements for MPEG-DASH 

Wowza Streaming Engine 4.7.7 provides a variety of fixes and performance improvements for nDVR support of MPEG-DASH. For more information, see Get started with Wowza nDVR.

Detailed list of changes in Wowza Streaming Engine 4.7.7

Changes since 4.7.6 release

  • Fixed an issue where content in DVR stores that use custom chunk ID handlers was not being purged correctly.
  • Updated AAC type detection to use extended flags when present.
  • Added a detectAACExtension field (default = true, meaning extended detection is enabled).
  • Updated OPTIONS to send the Content-Length header for all requests.
  • Updated RTP ingestion to support PCMA 8kHz audio.
  • Fixed an issue where Media Cache could not handle large files hosted on Google Cloud Storage.
  • Replaced the log4j file appender DailyRollingFileAppender with WowzaDailyRollingFileAppender (now the default appender). The new appender preserves the .log file extension when appending the DatePattern (for example: wowzastreamingengine_access.[date].log instead of wowzastreamingengine_access.log.[date]).
  • In the Wowza Streaming Engine Server-side Java API Reference, updated the description of the getPublishFramerateVideo(int source) method in IMediaStream.

Stream Targets (Push Publishing)

  • Akamai stream targets
    • Fixed an Akamai DASH stream target issue where chunk file pushes fail when multiple sessions push the same MPEG DASH stream, such as when a single Akamai DASH target pushes redundantly or when multiple Akamai DASH targets push the same stream to different Akamai stream IDs.
    • Fixed an issue with the legacy adaptiveGroups Akamai stream target parameter that prevented adaptive group playlists/manifests from being pushed to Akamai.
    • Fixed an issue with Akamai HLS stream targets that prevented audio-only and video-only streams from working properly when the "audioonly" or "videoonly" options are used in the cupertino.renditions target parameter.

Live Stream DVR Playback (Wowza nDVR)

  • Improved nDVR time index search to compensate for irregular time gaps.

Live Stream Encoding, Transcoding, and Transrating

  • Updated the MediaReaderH264 class to correctly generate codec information for Opus when using the transcoder.

MPEG-DASH Streaming

  • Significantly improved response times for MPEG-DASH DVR segment and Media Presentation Description requests.
  • Changed the default video timescale for MPEG-DASH DVR to 1000 milliseconds to eliminate rounding errors in the MPD segmentTimeline and in the earliestPresentationTime in the DASH video segments.


  • Updated WebRTC configuration to have its own block inside of Application.xml.
  • Fixed an issue where WebRTC UDP session objects were not being destroyed correctly.
  • Added a WebRTC configuration REST API endpoint:
    • Basic configuration endpoint: /v2/servers/{serverName}/vhosts/{vhostName}/applications/{appName}/webrtc
    • Advanced configuration endpoint: /v2/servers/{serverName}/vhosts/{vhostName}/applications/{appName}/webrtc/adv

Detailed list of changes in Wowza Streaming Engine updater

Between server software builds, Wowza produces incremental updaters so you can get the latest bug fixes and improvements for Wowza Streaming Engine. The following improvements were made in Wowza Streaming Engine build 20190222144406 released on March 4, 2019.

Changes (since 4.7.7 server release)

  • Removed support of events for Facebook Stream Targets because Facebook has deprecated the ability to live stream to events
  • Deprecated the PushPublishMap properties facebook.eventSourceType and facebook.eventSourceName. The property facebook.destType no longer supports the value "event"
  • Removed request for user_events Facebook permission
  • Removed support for configuring Facebook Stream Targets for events in Wowza Streaming Engine Manager
  • Removed request for user_managed_groups Facebook permission when using Facebook Stream Target
  • Fixed bug where segments were not returned correctly when using adaptive bitrate HTTP Smooth Streaming with similar multiple audio tracks
  • Updates and fixes for group-manager stream target
  • Changes to Akamai HLS, DASH, and HDS stream targets:
    • Fixed processing of the host parameter so that redundant streaming works on the Akamai MSL 4.x network
    • Added a playbackHost parameter to the PushPublishMap.txt file and in the push publishing REST APIs to allow absolute stream URLs to work on the Akamai MSL 4.x network
    • Added the Playback Host option to the Akamai stream target configuration in Wowza Streaming Engine Manager to define the playbackHost stream target parameter
    • Added the inclusion of both the event and adaptive group names in stream target URLs if both are defined by the user. For example, http://[domain]/[akamai_stream_id]/[eventName]/[adaptiveGroupName]/playlist.m3u8/. Previously, only the adpative group name was included
    • Fixed logging of the DASH/HDS playbackURL
  • Fixed bug where WebRTC DTLS sessions did not close properly
  • Added support for the property webRTCIdleTimeout in Application.xml for WebRTC connections. Property name is webRTCIdleTimeout; type is Integer; location is Application/WebRTC/Properties
  • Fixed issue where Live Stream Recorder did not record to the correct output file type
  • Fixed issue where Live Stream Recorder state was not accurately reflected in Wowza Streaming Engine Manager
  • Fixed an issue where video-only HLS nDVR streams returned an invalid playlist when attempting to play at the beginning of the stream
  • Added support on Windows and Linux for IGMPV3 with IPV4 IP addresses for MPEG-TS sources using a key-value pair on stream files for multicast source address filtering. The key is igmpV3IPV4SourceAddress; the type is String; the value must be a valid IPV4 source address. The value of accepts all MPEG-TS multicast streams from all sources. The igmpV3IPV4SourceAddress property can be configured in the REST API or in the Wowza Streaming Engine Manager on the stream file's Properties page
  • Added support on Windows and Linux for IGMPV3 with IPV4 IP addresses for native RTP sources by adding the property igmpV3IPV4SourceAddress for multicast source address filtering. The property is igmpV3IPV4SourceAddress; the type is String; the location is Application/RTP/Properties
  • Added support for returning static and dynamic MPEG-DASH nDVR manifests while using nDVR query parameters
  • Added transcoder parameters for the MainConcept H.264 encoder to specify color primaries, transfer characteristics, and matrix coefficients
  • Added transcoder parameters for the NVENC H.264 and H.265 encoder to set minimum, maximum, and constant quantization parameters
  • Fixed an issue that caused green frames when using the NVIDIA decoder and CUDA scaler when the source frame height didn't match the display height