Important playback issues that affect Wowza Streaming Engine

This article describes important stream playback issues that may affect the deployment and management of Wowza Streaming Engine™ media server 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, 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.

Known playback issues in Wowza Streaming Engine

Silverlight plugin can't be installed in Chrome browser

In Google Chrome browsers (version 42 and later), the Netscape Plugin Application Programming Interface (NPAPI) is disabled by default, which prevents Silverlight plugin installation. Users see the Silverlight installation prompt after proceeding through the Silverlight plugin installation process and restarting the browser.


  1. Open the Chrome browser and enter chrome://flags/#enable-npapi.
  2. Under Enable NPAPI, click Enable.
  3. Relaunch the Chrome browser.

iOS 7 and iOS 8 native players incorrectly display CEA-608 captions that have 32 characters

A CEA-608 caption that has exactly 32 characters and is sent as part of the video NAL units is displayed incorrectly. This doesn't occur if the caption has 31 or 33 characters.


There's no fix at this time. Bug 19179149 is open in the Apple Radar bug reporting tool. Last tested with iOS 8.3.

Safari video player in iOS 8 doesn't handle UTF-8 closed-caption characters

Garbage characters are inserted during playback of video that have UTF-8 closed captions.


This issue is fixed in iOS 12.

Playback issues with MPEG-DASH streams

When using the DASH-IF reference player (dash.js) and Google Chrome, DASH streams may play for a while and then start looping on a single media segment.

If you're running Wowza Streaming Engine software version 4.2.0 and earlier, and if you use the MPEG-DASH test player in Wowza Streaming Engine Manager to play a DASH steam, the stream may not start. These players are based on an older dash.js version.


We recommend that you use either the Google Shaka player or the Bitmovin Adaptive Streaming Player to play DASH streams. These players seem to have better compatibility with Wowza Streaming Engine MPEG-DASH streams.

If you want to use the MPEG-DASH test player in Wowza Streaming Engine Manager, be sure to use Wowza Streaming Engine 4.3.0 or later. The player is based on the open source Shaka Player project, and should give better playback results.

Live DVR streams won't start on iOS 8

Live streams with DVR enabled by Wowza nDVR may not start playback on iOS 8 devices.


This issue is fixed on iOS 12. If you encounter this issue on your iOS 8-based player, you can either touch and hold the Rewind button to start playback immediately or wait for about 30 seconds for playback to start. 
Note: This problem doesn't occur on iOS 7 (or earlier).

RTMP playback fails on VLC media player 2.2

When loading an RTMP stream in VideoLAN VLC media player 2.2.x, the stream stalls continuously.


Use VLC media player 2.1.5, which doesn't exhibit this issue during RTMP playback.

Problems with WebVTT closed captions in JW Player 7

JW Player has confirmed that a problem in their JW Player 7 software may prevent WebVTT closed captions in live streams from being displayed during playback.


JW Player addressed the issue in JW Player 8. You can also use JW Player 6 or CEA-608 captions.

Apple HLS playback issues using the Microsoft Edge native player

In the Microsoft Edge native player, you can play Apple HLS streams, but artifacts appear across the lower part of the video.


This issue was reported with Edge version 20.10240.16384.0 on Windows 10 (build 10240). The issue doesn't occur with with Edge version 25.10586.0.0 on Windows 10 (version 1511 - OS build 10586.3).

FLV file playback issue in JW Player

JW Player can't play FLV files from Wowza Streaming Engine using the regular playback URL, for example:



To enable JW Player to play files, include the flv: stream prefix twice in the playback URL, for example:


WebVTT closed captions dropped from long-running live streams on iOS 9

On iOS 9-based players, after a live stream with WebVTT captions runs for over 12 hours, the captions no longer appear in the player.


This issue is fixed in iOS 12-based players. It also doesn't occur with iOS 8 and iOS 7 players.

Problems with origin/edge playback of .stream file sources

When Wowza Streaming Engine is configured as a live stream repeater (origin/edge), the .stream file used as a source must be stored on the origin server. If the origin and edge applications are located on a single Wowza Streaming Engine instance, playback on the edge fails. Additionally, playback on the edge server fails if a .stream file on the edge server has an identical name to the source .stream file on the origin server.


Ensure that the origin and edge applications are located on separate Wowza Streaming Engine instances and that there are no .stream files on the edge server with the same name as .stream files on the origin server.

Autoplay disabled in Chome, Firefox, and Safari

Google Chrome version 66 and later, Mozilla Firefox version 66 and later, and Safari version 11 and later have disabled default support for automatically playing video content with audio.


Users have the ability to modify their autoplay preferences. For more information about the browser policies and user options, see Browser autoplay policies.

Transcoded WebRTC source streams with passthrough video fail to play over MPEG-TS HLS

WebRTC source streams, including those with H.264 video, that are transcoded for adaptive bitrate streaming with Video Codec set to Passthrough encounter playback issues over MPEG-TS HLS (cupertinostreamingpacketizer).


There is no fix available at this time, but you can transcode the video by setting Video Codec to another codec, rather than Passthrough, to avoid this issue.

More resources