Skip to content

Releases: asrashley/dash-live

Migrated to Python 3 and Flask

18 Feb 16:47
Compare
Choose a tag to compare

This code was using an obsolete version of Google App Engine that is based upon Python 2. This is the first release to use Python 3, with Flask and SQLAlchemy to provide the web framework and database.

This is a breaking change that requires all data to be manually migrated from the v1.6

Last Python 2.7 release

18 Feb 16:46
Compare
Choose a tag to compare

The Python 2.7 code is now feature-frozen

H.265 Support

18 Feb 16:45
Compare
Choose a tag to compare

Added:

  • support for h.265 (HEVC) fragments that have been encoded using the "hevc" or "hvc1" schemes.

Enhanced DASH event support

18 Feb 16:44
Compare
Choose a tag to compare

Added:

  • inband and inline DASH event support to views
  • support for scte35 events
  • another manifest example - manifest_n.mpd
  • support for xsd:dateTime that includes days, months and years
  • pure python fallback for CRC32 calculation
  • support for multi-period DASH streams
  • tests for correct encryption information in an encrypted stream

Changed:

  • only test options used by a manifest in exhaustive tests
  • removed API tests from views_test
  • split views.py in to multiple separate file
  • converted manifest context from a dictionary into objects
  • code refactor to move module locations
  • moved playready tests from views_test into playready_test
  • remove use of eval for evaluating MP4 boxes

Fixed:

  • return 404 error if invalid mediafile key is used
  • legacy manifest requests

CORS configuration

18 Feb 16:43
Compare
Choose a tag to compare

CORS configuration

Rather than hard-coding the list of allowed domains for CORS requests, this release allows settings.py to specify the allowed list of domains in an allowed_domains variable. This can either be a compiled regex or a string.

DASH event boxes

18 Feb 16:42
Compare
Choose a tag to compare

DASH event boxes

Added

  • DASH emsg box parser
  • Creating DASH event boxes

PlayReady v1.0 support

18 Feb 16:41
Compare
Choose a tag to compare

PlayReady v1.0 support

In some situations it is useful to be able to limit the PlayReady features to be compatible with a particular version of PlayReady. This release adds a "playready_version" CGI parameter that is used to set the version parameter in the PlayReady class. It must be set to a floating point number in the range 1.0 to 4.0.

When playready_version is set to 1.0 the schemeIdUri field in the ContentProtection element will be set to the PlayReady v1.0 UUID rather than the normal PlayReady UUID.

Added

  • PlayReady v1.0 UUID
  • "playready_version" CGI parameter

v1.0

18 Feb 16:40
Compare
Choose a tag to compare

LA_URL override support

Added

  • override the LA_URL specified in the stream settings.