Wowza Streaming Engine™, formerly Wowza Media Server™, is robust, customizable, and scalable media server software that powers reliable streaming of high-quality video and audio to any device, anywhere.
Wowza™ Player is our new HTML5 player for Apple HLS video and audio streaming from Wowza Streaming Engine and Wowza Streaming Cloud. Wowza Player comes with a Player Builder that you can use to customize a player and generate HTML embed code. In Wowza Streaming Engine 4.6.0, you can use the new Wowza Player page in Wowza Streaming Engine Manager to launch and pre-populate Wowza Player Builder with a source stream URL that you create. For more information about playing your streams in Wowza Player and creating custom embed code in Wowza Player Builder, see How to get started with Wowza Player.
By default in Wowza Transcoder, video scaling is done using CPU resources. Now in Wowza Streaming Engine 4.6.0, you can offload transcoder video scaling to NVIDIA CUDA-based GPUs. This reduces the overall CPU usage of a given set of transcoder sessions. CUDA scaling works on all NVIDIA CUDA cards that are Tesla technology or greater. For more information, see Template details - Scale.
Wowza Streaming Engine 4.6.0 also includes a new transcoder ITranscoderVideoLoadBalancer interface that enables you to balance NVIDIA CUDA accelerated transcoding across multiple GPUs. For more information, see How to load balance NVIDIA CUDA accelerated transcoding across GPUs.
Wowza Streaming Engine 4.6.0 enables you to include multiple audio and video tracks in an MPEG-DASH presentation (MPD). Including multiple tracks lets viewers select between multiple languages or aspect ratios during stream playback. For more information, see How to use alternative audio or video tracks with MPEG-DASH streams.
Wowza Streaming Engine 4.6.0 has new MediaCaster types to enable live applications to ingest Apple HLS and MPEG-TS (TCP/IP) source streams and make them available to all player technologies supported by the Streaming Engine software. To learn how to set up live applications to ingest Apple HLS source streams (applehls MediaCaster), see How to publish and play a live stream (Apple HLS). To learn how to ingest MPEG-TS (TCP/IP) source streams (mpegtstcp MediaCaster), see How to publish and play a live stream (MPEG-TS over TCP/IP).
Wowza Streaming Engine 4.6.0 can ingest MPEG-TS DVB Teletext subtitle data in live streams as closed captions. The Teletext data is injected into the Transport Stream (TS) packets as onTextData AMF events and then translated to the supported closed-captioning formats for live stream playback. For more information, see How to ingest MPEG-TS DVB Teletext subtitle data for closed captioning.
In Wowza Streaming Engine 4.6.0, you can now configure your Facebook stream target to send a stream of unlimited length to Facebook. For more information, see "Create a stream target to send the stream to Facebook" in How to stream to Facebook Live using Wowza Streaming Engine.
Wowza Streaming Engine media server software can only be used on the following operating systems:
Install the Wowza Streaming Engine software on a clean operating system. Upgrading from a previous version of the software isn't supported. If you want to update your earlier version of Wowza Streaming Engine software to Wowza Streaming Engine 4.6.0, see How to update your Wowza Streaming Engine installation for instructions.
Note: To use the Transcoder feature in Wowza Streaming Engine, you must install the software on a 64-bit Windows or Linux operating system that has a 64-bit version of Java.
Wowza Streaming Engine is a Java application. The installation wizard for the Wowza Streaming Engine 4.6.0 software automatically installs a server version of the Java Runtime Environment (JRE) that is required by Wowza Streaming Engine, making it easier to get your media server up and running.
If you can't or don't want to use the version of Java that installs with the Wowza Streaming Engine software, you can use a different JRE. Wowza Streaming Engine software requires a JRE that supports deploying Java in server environments. Java 6, 7, and 8 are all supported but Java 8 is recommended. For information on how to install a different, supported version of Java and how to instruct the Wowza Streaming Engine installation to use it, see How to manually install and troubleshoot Java with Wowza Streaming Engine.
You can use Wowza Streaming Engine Manager with the latest versions of most modern web browsers that support HTML5 and Cascading Style Sheets level 3 (CSS 3). We recommend that you use the latest version of the Chrome browser for best results.
Note: Wowza Streaming Engine Manager was tested extensively using the Google Chrome web browser. Manager functionality and performance may vary on other web browsers. Browser updates that occur after this release of the Wowza Streaming Engine software may also impact functionality and performance and Wowza will work to address any new issues as quickly as possible.
In Wowza Streaming Engine Manager, most application and feature pages have a Test Players button in the upper-right corner that provides access to built-in test players. The test players enable you to playback streams from your application to verify its configuration.
The MPEG-DASH, Adobe RTMP, Adobe HDS, MS Smooth, and Mobile test players have been tested and are supported on the Google Chrome web browser on all supported operating systems.
The Apple HLS test player has been tested and is supported on the Safari web browser on the OS X operating system.
If you run Wowza Streaming Engine Manager in a web browser where the test players aren't supported, they may not work or may not work as expected.
When using the test players, be aware of the following issues:
Wowza Streaming Engine software features automated tuning for the server and virtual hosts (VHosts), with the ability to manually adjust the settings as needed. The Java heap size, garbage collection (GC) settings, and thread counts are properly set on startup. To make adjustments to these and other settings, go to the Server > Performance Tuning page in Wowza Streaming Engine Manager.
If you encounter OutOfMemory errors while running the server, you may want to increase the maximum size of the Java heap. To do this, go to the Server > Performance Tuning > Java Settings page in Wowza Streaming Engine Manager.
Restarting Wowza Streaming Engine
You may need to restart the Wowza Streaming Engine instance to effect changes, for example to apply sign in credential changes for a user. The feature page will display a message with a Restart button if the server must be restarted for the changes to take effect. On Windows and OS X platforms, you can click the button to apply the changes; however, Linux users must restart the server using the standard Linux service control interface. To control the Wowza Streaming Engine instance from a command shell, type service WowzaStreamingEngine start | stop | restart.
By default, the Wowza Streaming Engine software requires that RTMP-based and RTSP-based encoders that initiate connections to live applications provide a user name (source name) and password. You can set up and manage source credentials in Wowza Streaming Engine Manager on the Source Authentication page (click Server > Source Authentication). You can manage the authenticated connection requirement for live applications on the Source Security page (click Applications, click the live application name in the contents panel, and then click Source Security.)
Wowza Streaming Engine is configured to only listen on port 1935 by default. This is the default RTMP port. To connect to the server over RTMPT, go to the Server > Virtual Host Setup page in Wowza Streaming Engine Manager and update the Default Streaming host port setting to use port 80 or connect over RTMPT using port 1935 (example: rtmpt://localhost:1935/[application-name]).
The JMX interface isn't available unless the Wowza Streaming Engine 4.6.0 service is running as a named user. To configure the service to run as a named user, do the following:
When running on a Windows 64-bit OS, the Intel Quick Sync hardware acceleration used by Wowza Transcoder is only available when running Wowza Streaming Engine software as a standalone application. When running as a Windows service, the hardware acceleration isn't available due to driver accessibility restrictions and only software encoding is invoked.
OS X and Linux installers don't provide an option to choose where the base Wowza Streaming Engine files are installed. For OS X, the location is /Library/WowzaStreamingEngine-4.6.0. For Linux, the location is /usr/local/WowzaStreamingEngine-4.6.0. All of the server startup scripts locate the server files through a symbolic link named /Library/WowzaStreamingEngine (OS X) and /usr/local/WowzaStreamingEngine (Linux). If you relocate the base server files, be sure to update the symbolic link using the ln -sf command.
The Wowza Streaming Engine software includes example applications that highlight the server functionality. The examples are located in [install-dir]/examples. The [install-dir]/examples/README.html file describes the available examples and how to install them.
When you run the examples installation script, some example applications won't be installed if an application of the same type is already configured on the server. If you run the examples installation script while Wowza Streaming Engine Manager is running, you must restart the server after the installation is completed (in Wowza Streaming Engine Manager, click Server > Server Setup > Restart). To view the installed example applications, click the Applications tab in the manager.
Here are a few direct links to help you get started using the Wowza Streaming Engine software:
Support is available in the following ways: