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.
Known playback issues in Wowza Streaming Engine
License key and playback URL aren’t pre-populated in Wowza Player Builder
SolutionThis is a temporary regression of functionality that we intend to fix in a future release of Wowza Player Builder. Until then, you can manually enter your license key and playback URL in Player Builder. For more information, see Issues with Wowza Player Builder functionality and access.
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.
- Open the Chrome browser and enter chrome://flags/#enable-npapi.
- Under Enable NPAPI, click Enable.
- Relaunch the Chrome browser.
iOS 7 and iOS 8 native players incorrectly display CEA-608 captions that have 32 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
This issue is fixed in iOS 12.
Playback issues with MPEG-DASH streams
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 or the MPEGDASHPlayer examples included with your Wowza Streaming Engine software installation 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 or the MPEGDASHPlayer examples in Wowza Streaming Engine software, be sure to use Wowza Streaming Engine 4.3.0 or later. The players in this software are based on the open source Shaka Player project, and should give better playback results.
Live DVR streams won't start on iOS 8
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.
RTMP playback fails on VLC media player 2.2
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 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
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
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
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
Users have the ability to modify their autoplay preferences. For more information about the browser policies and user options, see Browser autoplay policies.