Migrating to 5.17.0 onwards from earlier releases

Changes are being introduced from version 5.17.0 onwards, improving performance on some platforms but may impact customer applications.

player.reset() not recommended before zapping

In previous versions, it was recommended that player.reset() was run before zapping (changing content using player.src()). For best performance, we now recommend that player.reset() is not called when zapping. The only time it is envisaged that player.reset() would be required is to stop playing content without zapping to new content. This may be necessary due to an error or to free an SSM session without zapping.

No ready event during zapping

In version 5.16.1 and earlier, the player tech is regenerated on each zap, and multiple ready events would be generated as the player tech was created. From version 5.17.0, the player tech will be created at the same time as the player and maintained throughout the player's lifetime. There will be a single ready event when the player is first created and no ready events during zapping.
In the rare occasions where a call to player.reset() is necessary, there will be one ready event after the reset.

DASH tech configurations

Shaka-player is used as the player tech when playing DASH streams. The Shaka-player configuration will be available to read using player.otvtoolkit().getConfiguration() as soon as the player is ready. Any changes made to the configuration using player.otvtoolkit().configure() will be maintained throughout the life of the player. Any configurations made directly to the tech (for example, listeners on tech events) will be maintained through zapping but not through player.reset(). These will have to be reapplied in a ready event listener.