Skip to main content
Sign in

On-Premise Streaming - Troubleshooting Video Playback Errors

Dwaine Webb
  • Updated

626, 699 or 620 Errors for All Titles 

Issue: Required network end points may not be reachable. Video playback errors (such as 626, 699 or 620 errors) most commonly occur when a playback device is having difficulty communicating with our licensing servers.  This licensing process takes place when a user selects a movie to view.

In certain environments, it is common to have strict network rules that can interfere with normal network traffic.  In order for the cloud streaming service to function properly, a number of network endpoints must be reachable.

 

Resolution: The On-Site Devices Requirements found here (Technical Requirements) must be reachable by the playback device. This information should be brought to the attention of your institution's network administrators as well as the administrators for any managed devices (such as Chromebooks). 

If this is occurring intermittently, it may not be an outright network ban or block. Instead, these kinds of errors can sometimes be caused by something more subtle such as SSL Inspection rules or rules governing JavaScript behavior. 

License server communication can be confirmed by having a user experiencing this issue attempt to reach the appropriate URL for their browser listed below. This will determine if they can indeed reach the license server.

It might also be helpful to have the user capture an http archive of the error as it occurs.  Instructions on how to do that can be found here - How to capture an http archive (HAR) file

 

Note: For Customers Using a Swank Cached License Server, your DRM license endpoint would be to your Cached License Server.

 

699 or 626 Error for Specific Titles

Issue: There is an error that can occur on a MacOS/IOS device when viewing foreign language films that appears to be a 699 or 626 error. When a MacOS or IOS device has a default system language that does not match the default language of the content the Shaka player returns a 699 or 626 error.

Resolution: The issue must be fixed on the Shaka player side by Google. A ticket has been opened with the Shaka Project Team and we are currently waiting for a fix. We have found success using the Google Chrome desktop browser on non-MacOS/IOS devices, but we are still waiting for the root cause to be addressed by the Shaka Project Team.

 

Browser Plug-Ins

Issue: If your browser is utilizing plug-ins such as ad blockers, these can sometimes interfere with video playback. 

Resolution: Try disabling any browser plug-ins that might be interfering with network connectivity.  If possible, try an alternate browser.

 

Update Browser

Issue: Currently supported browsers are Firefox, Chrome, Safari and Edge.  If a browser is too far out of date, the Content Decryption Module (CDM) bundled with the browser may no longer be compatible with our streaming server content. 

Resolution: Please ensure your browser is up to date and try again.  If possible, try an alternate browser.

  • Firefox has a Digital Rights Management Content setting that must be enabled. Once this is enabled it might take a minute for the additional DRM component to be installed.

 

Digital Rights Management (DRM)

Issue: Swank Motion Picture video streams require that the playback devices support Digital Rights Management (DRM). Some playback hardware (such as Android OS based Promethean boards or ViewSonic displays) may not include support for DRM.

Resolution: We suggest using another device such as a laptop or desktop computer as a streaming source and using the external video input on the equipment to facilitate playback. This should bypass the internal operating system and use the board simply as a monitor. 

 

HDCP - Black/Blank Video with Audio

Issue: You may encounter issues relating to HDCP. For example, you may see a black square where video should appear. HDCP ensures that any connection between a playback device and a display device is secure.

Resolution:

  • Wired Playback: If you are using a laptop and the output is still an issue or you are getting an HDCP error, you can change your monitor settings from "mirror" monitors to "extend" monitors and drag the playback window to the external screen. This should allow playback without error. 

    For further information, we suggest contacting the manufacturer of the equipment. 

    • Users of Vivi systems report that video playback works through Vivi Screen Sharing, but not the Play Video feature.
    • Users of Newline displays report that playback works when used with HDMI connected Chromebooks
  • Wireless Playback: In our experience, wireless displays/projectors typically do not support HDCP. For that reason, we always recommend using a wired connection to an HDCP compatible display. If you are attempting to wirelessly connect to a display, you may be able to work around this limitation by turning off graphics acceleration support within the settings of Chromium-based browsers.  In the latest version of Chrome, that setting can be found here:
    • chrome://settings/?search=acceleration
      • However, please be aware that this work-around may change or be removed as browsers are updated by their publishers.
    • AppleTV: If you are using an AppleTV, please be aware you have the option of either:
      • Mirroring their display to an AppleTV
      • Casting the video stream to an AppleTV via AirPlay
      • If you’re using an Apple device, we recommend using the Safari browser and the AirPlay casting process if possible as this usually provides a more reliable result.  For full details, please refer to the following document - Apple AirPlay, AppleTV Casting

 

 

 

 

Related articles

Comments

0 comments

Please sign in to leave a comment.

Powered by Zendesk