Releases: muxinc/mux-stats-sdk-exoplayer
Releases · muxinc/mux-stats-sdk-exoplayer
v2.0.0
This is a major release, including a number of fixes and changes:
- Bump to v5.0.0 of MuxCore
- Update ad handling logic to ensure that ad metrics and dimensions are tracked correctly
- Retry sending failed beacons, rather than letting them drop
- Fix issue where we were incorrectly calculating scaling metrics when screen or video resolution was negative
- Fix an issue where watch time is incorrectly increasing after certain events
- Make sure that time to first frame is not tracked for views that result from
programchange
- Add support for
viewer_connection_type
, which is a breaking change forIDevice
, as it adds another method that must be implemented - Add support for
view_session_id
, which includes an additionalCustomerViewData
class. This changes the constructor for creating aMuxStats
instance
- Drop support for ExoPlayer r2.7.x and r2.8.x
- Implement SeekingEvent directly in
MuxStatsExoPlayer
- Fix issue where source type could be null and cause a crash
- Fix an issue where ad events are sent out of order in some cases
- Add connection type detection
- Report logical sizes for player size, rather than physical size
- Fix an issue where time to first frame was incorrectly measured in some cases, such as mid- or post-roll ad playback without a pre-roll
- Add support for
CustomerViewData
, includingsetViewSessionId
v1.5.0
v1.4.0
v1.3.0
- Support
MuxStatsExoPlayer.orientationChange()
to indicate orientation changes during playback - Support firing
RenditionChange
events as playback renditions change (including bitrate, frame rate, and resolutions) - Fix an issue where full screen is not reported correctly
- Clean up debug logging slightly
v1.2.0
v1.1.0
This release includes quite a few fixes and enhancements.
- add support for additional debug logging. See
muxStatsExoPlayer.enableMuxCoreDebug(Boolean enable, Boolean verbose)
- add the ability to update customerVideoData and customerPlayerData mid-stream, in cases that certain metadata may not be available at the beginning of playback. See
muxStatsExoPlayer.updateCustomerData(CustomerPlayerData customerPlayerData, CustomerVideoData customerVideoData)
- fix an issue where if
MuxStatsExoPlayer
is initialized too late, the stream is not tracked correctly - fix an issue where Mux Plugin Version is reported incorrectly
- fix an issue where the
EndedEvent
is not sent to the backend - fix an issue where tracking playback is not correct when
playWhenReady
is set to false (i.e. non-autoplay playback) - fix an issue where events could be sent after playback completes, forcing the view to be active for longer than it actually was
v1.0.0
This is a major release of our ExoPlayer integration, including the following fixes and changes:
- Add support for ExoPlayer 2.9.x
- Add support for ExoPlayer 2.10.x
- Fix issue where ExoPlayer versions 2.9.x and greater would log messages about accessing the player on the wrong thread
- Removed support for ExoPlayer 2.6.x and older (due to changes in build pipeline and Gradle configurations)
- Support Gradle 3.5.2
v0.5.1
v0.5.0
- Deprecated method
muxStatsExoPlayer.getImaSDKListener
in favor ofmuxStatsExoPlayer.monitorImaAdsLoader(adsLoader)
. The previous method will still work, but you should migrate to the new method as the deprecated method will be removed with the next major version. - Fix an issue where Google IMA SDK was a hard requirement unintentionally.