Google’s Accelerated Mobile Pages (AMP) have become ubiquitous for digital publishers, which is why we’re excited to release AMP improvements in JW 8.15 and to our official AMP component, amp-jwplayer. AMP is an open source HTML-based web component framework that enables media companies to easily create web pages that are “compelling, smooth, and load near instantaneously.” Developers will find that amp-jwplayer is now compatible with other AMP components, including amp-analytics, which allows video player data to be sent to any supported analytics platform, and amp-video-docking, which allows the player to stick to the page.
Release Date: June 11, 2020
To the VAST ad client, added support for the jwpseg macro from within VAST tags contained within a wrapper.
Improved playback resilience and error handling with some bad VPAID ad creatives.
Fixed an issue in the VAST client preventing some ad creatives from properly timing out.
Fixed a bug causing captions in some DASH streams to abruptly stop displaying.
Fixed an issue in the VAST client where the player would not request additional ads after one ad in a pod timed out.
Release Date: June 3, 2020
Service release, no new features.
Release Date: May 28, 2020
Improved compatibility with the AMP framework and quality assurance capabilities of our amp-jwplayer component.
Added a configuration option, playlistIndex, which enables a playlist to be loaded and start playback from any item within it, not just the first. The default of this option is a 0 index.
Fixed a bug preventing captions from working on some live streams.
Fixed a problem with Chromecast where captions were not casting.
Fixed an issue where the wrong captions track appeared to be selected if both in-manifest and side-loaded captions tracks are present.
The video-seconds-played trigger listed for configuration in amp-video-analytics does not work properly in this release. This will be fixed in a future release. All other triggers listed should operate as expected