Known Issues

The current release has the following known issues:

Azure Media Player

  • Incorrectly configured encoders may cause issues with playback
  • Streams with timestamps greater than 2^53 may have playback issues.
    • Mitigation: Use 90-kHz video and 44.1-kHz audio timescales
  • No autoplay on mobile devices without user interaction. It's blocked by the platform.
  • Seeking near discontinuities may cause playback failure.
  • Download of large presentations may cause UI to lockup.
  • Can't automatically play back same source again after presentation ended.
    • To replay a source after it has ended, it's required to set the source again.
  • Empty manifests may cause issues with the player.
    • This issue can occur when starting a live stream and not enough chunks are found in the manifest.
  • Playback position maybe outside UI seekbar.
  • Event ordering isn't consistent across all techs.
  • Buffered property isn't consistent across techs.
  • nativeControlsForTouch must be false (default) to avoid "Object doesn't support property or method 'setControls'"
  • Posters must now be absolute urls
  • Minor aesthetic issues may occur in the UI when using high contrast mode of the device
  • URLs containing "%" or "+" in the fully decoded string may have problems setting the source

Ad insertion

  • Ads may have issues being inserted (on demand or live) when an ad-blocker is installed in the browser
  • Mobile devices may have issues playing back ads.
  • MP4 Midroll ads aren't currently supported by Azure Media Player.

AzureHtml5JS

  • In the DVR window of Live content, when content finishes the timeline will continue to grow until seeking to the area or reaching the end of the presentation.

  • Live presentations in Firefox with MSE enabled has some issues

  • Assets that are audio only will not play back via the AzureHtml5JS tech.

    • If you’d like to play back assets without audio, you can do so by inserting blank audio using the Azure Media Services Explorer tool
    • Instructions on how to insert silent audio can be found here

Flash

  • AES content does not play back in Flash version 30.0.0.134 due to a bug in Adobe's caching logic. Adobe has fixed the issue and released it in 30.0.0.154
  • Tech and http failures (such as 404 network timeouts), the player will take longer to recover than other techs.
  • Click on video area with flashSS tech won't play/pause the player.
  • If the user has Flash installed but doesn't give permission to load it on the site, infinite spinning can occur. This is because the player thinks the plugin is installed and available and it thinks the plugin is running the content. JavaScript code has been sent but the browser settings have blocked the plugin from executing until the user accepts the prompt to allow the plugin. This can occur in all browsers.

Silverlight

  • Missing features
  • Tech and http failures (such as 404 network timeouts), the player will take longer to recover than other techs.
  • Safari and Firefox on Mac playback with Silverlight requires explicitly defining "http:// or https:// for the source.
  • If an API is missing for this tech, it will generally return null.
  • If the user has Flash installed but doesn't give permission to load it on the site, infinite spinning can occur. This is because the player thinks the plugin is installed and available and it thinks the plugin is running the content. JavaScript code has been sent but the browser settings have blocked the plugin from executing until the user accepts the prompt to allow the plugin. This can occur in all browsers.

Native HTML5

  • Html5 tech is only sending canplaythrough event for first set source.
  • This tech only supports what the browser has implemented. Some features may be missing in this tech.
  • If an API is missing for this tech, it will generally return null.
  • There are issues with Captions and Subtitles on this tech. They may or may not be available or viewable on this tech.
  • Having limited bandwidth in HLS/Html5 tech scenario results in audio playing without video.

Microsoft

  • IE8 playback does not currently work due to incompatibility with ECMAScript 5
  • In IE and some versions of Edge, fullscreen cannot be entered by tabbing to the button and selecting it or using the F/f hotkey.

Google

  • Multiple encoding profiles in the same manifest have some playback issues in Chrome and is not recommended.
  • Chrome cannot play back HE-AAC with AzureHtml5JS. Follow details on the bug tracker.
  • As of Chrome v58, widevine content must be loaded/played back via the https:// protocol otherwise playback will fail.

Mozilla

  • Audio stream switch requires audio streams to have the same codec private data when using AzureHtml5JS. Firefox platform requires this.

Apple

  • Safari on Mac often enables Power Saver mode by default with the setting "Stop plug-ins to save power", which blocks plugins like Flash and Silverlight when they believe it is not in favor to the user. This block does not block the plugin's existent, only capabilities. Given the default techOrder, this may cause issues when attempting to play back
    • Mitigation 1: If the video player is 'front and center' (within a 3000 x 3000 pixel boundary starting at the top-left corner of the document), it should still play.
    • Mitigation 2: Change the techOrder for Safari to be ["azureHtml5JS", "html5"]. This mitigation has implication of not getting all the features that are available in the FlashSS tech.
  • PlayReady content via Silverlight may have issues playing back in Safari.
  • AES and restricted token content does not play back using iOS and older Android devices.
    • In order to achieve this scenario, a proxy must be added to your service.
  • Default skin for iOS Phone shows through.
  • iPhone playback always occurs in the native player fullscreen.
    • Features, including captions, may not persist in this non-inline playback.
  • When live presentation ends, iOS devices will not properly end presentation.
  • iOS does not allow for DVR capabilities.
  • iOS audio stream switch can only be done though iOS native player UI and requires audio streams to have the same codec private data
  • Older versions of Safari may potentially have issues playing back live streams.

Older Android

  • AES and restricted token content does not play back using iOS and older Android devices.
    • In order to achieve this scenario, a proxy must be added to your service.