FAQ: Why aren't all HLS.js or Shaka features supported by JW Player?

JW Player aims to maintain a player library that is small and robust and requires minimal implementation code.

JW Player uses two open-source projects to provide playback for streams:

  • HLS.js (HLS)
  • Shaka (DASH)

Some of the features in these project support a broader set of use cases than our customers require. JW Player aims to maintain a player library that is small and robust and requires minimal implementation code.


Size and Performance

A player library should be small. Each new feature we add to the player has the following impacts:

  • Increases the size of the player library
  • Increases the number of resources to load the player
  • Increases the load time of the player

Because we understand that developers like you seek a high performing player, we strive to keep the size of the player library small.


Ease of Use

A player library should be easy to implement and use. The HLS.js and Shaka open-source projects include many great features. Our engineers carefully evaluate and select the HLS.js and Shaka features that support our customers' needs.

We have discovered that some HLS.js and Shaka features require additional implementation code and configuration. You should not have to tweak your code to get the best results, so we prefer to add features that work out-of-the-box. We seek to maintain a balance between enabling customization and ease of use.


📘

NOTE

If there is an HLS.js or Shaka feature that you need to ensure the monetization of or the optimal playing of an external stream, contact your JW Player representative. Be sure to provide your JW Player representative with a test stream and a full explanation of the expected behavior.


We will try to find an appropriate solution for you.



Did this page help you?