Release Date: March 8, 2018
- The SDK will now be conservative over manifests loading the first time to ensure the startup time will be equal to vanilla for high DVR streams.
Release Date: March 5, 2018
- Startup time reduced and now behave as Vanilla.
- New adaptive resource usage for better stability.
- Reduce the SDK impact on the Java Heap.
- Better Fire TV support.
- This SDK is now compatible with DNA 2.0 (see new documentation). rangeRequest as been deprecated and should not be used anymore.
Release Date: February 8, 2018
- Manifest URLs containing
../..are now correctly supported.
Release Date: February 7, 2018
- HLS streams stability and rebuffering.
- SDK stability by reducing the global number of threads used by HTTP request.
- Some improvement have been made regarding Dependency Management:
- The groupeId to use is now 'io.streamroot.dna' to better match the company strategy.
- The artifacts were split for better management. Now we have the artifact dna-core, that contain our core library, and the artifact dna-utils, that contain helper classes.
- StatsView is now in dna-utils.
- We hare now compatible with Youbora 6.1.0.
- The NullPointerException that occurred on negative answer during pairing negotiation is now fixed.
- The onProgress event during HTTP request is fixed and improve bandwidth detection in ABR.
Release Date: January 15, 2018
- The SDK is now able to communicate with latest versions of our DNA™ web library, starting from v4.12.1. Peers are now connecting each other faster than before and are able to connect again to other peers on long sessions run
- The HTTP request for activation is now correctly closed
- The contentId field is now correctly taken into account
- A stream which leads to a redirection is not anymore sent by its redirected URL to our backend
- The StatsView helper is no more printing negative values after 2.2GB
- Some rebuffering occurring at the start of the SDK are now gone
- We do not pass anymore query parameters when the player is not explicitly setting it to avoid breaking strict server implementations which leaded to either
404 Not foundor
403 forbidden errors