This article describes important issues that may affect your deployment and management of Wowza™ Player. If available, workarounds for these issues are described. Check back often as this article will be updated as new developments occur.
Autoplay playback issue for non-muted streams using Safari 11 and 12
For streams with autoplay enabled and mute set to false, playback in the Safari browser falls back to manual playback settings as expected, but playback freezes after manual playback is initiated.
To automatically play streams on Safari, set autoPlay to true and set mute to true. For more information about browser autoplay policies, see Use autoplay with Wowza Player.
Issue for ultra low latency stream HLS fallback on iOS
For Wowza Streaming Cloud ultra low latency streams that have HLS enabled as a fallback, the ultra low latency stream does not fall back to HLS as expected on mobile devices with iOS.
This was fixed in Wowza Player version 1.1.14.
Audio-only playback issue using Safari
Audio-only stream playback with the audioOnly configuration property set to true does not work as expected in the Safari browser.
To play audio-only streams on Safari, set audioOnly to false. This workaround shows the standard Wowza Player interface instead of the audio-only Wowza Player interface.
Issue for ID3 tag listener on iOS browsers
This was fixed in Wowza Player version 1.1.12.
Video-only streams pause during playback in Chrome desktop
In Chrome 63/64 and later, video-only streams played in Chrome desktop on Windows, Mac, Linux, and Chrome OS automatically pause when played in the background in a non-visible tab. For more information, see Audio/Video Updates in Chrome 63/64.
Add a silent audio track using the AAC codec to a video-only stream to prevent Chrome from pausing the video.
No autoplay in Wowza Player
The autoplay feature in Wowza Player has been disabled to prevent playback issues in some web browsers. Viewers must manually start playback on all platforms.
Autoplay was enabled again in Wowza Player version 1.1.14. See Use autoplay with Wowza Player for more information.
Character encoding errors in Wowza Player Builder 1.1.06
The title and description in Wowza Player Builder version 1.1.06 may contain character encoding errors. The generated embed code is not affected by this.
There's no solution at this time.
Playback issues using Safari 11
Some streams may not play correctly in the Safari 11 browser on OS X.
This was fixed in Wowza Player version 1.1.06.
"'JSON' is undefined" error occurs when using Internet Explorer
The error "SCRIPT5009: 'JSON' is undefined" occurs while running Wowza Player in Internet Explorer.
Either don't run in Compatibility Mode or include the JSON library in your web page. For more information, see the Stack Overflow thread SCRIPT5009: 'JSON' is undefined.
No autoplay on mobile platforms
There's no solution at this time as this is a feature of Android and iOS operating systems.
Inconsistent playback on Edge in Windows 10
Turn off developer tools in the Edge browser during playback.
Install the Media Feature Pack for Windows 10 N and Windows 10 KN.
Buffering issues during playback on Chrome for Android
This was fixed in Wowza Player 1.0.01.
Playback errors using Internet Explorer 11
Use the useFlash configuration setting to force Internet Explorer to load the Flash version of Wowza Player.
Playback issues in full screen mode using Internet Explorer 11
If you need to use full screen mode, use the useFlash configuration setting to force Internet Explorer to load the Flash version of Wowza Player.
Playback errors using load balancing and Internet Explorer 11
There is no solution at this time. We recommend using Google Chrome, Safari, or Firefox instead.
Playback issues using Safari 10.1.2
This was fixed in Wowza Player 1.1.02.
Green video playback using Safari
This was fixed in Wowza Player 1.0.04.