We’ve fixed a crash occurring when monitoring playback on an iOS or tvOS device with AirPlay enabled. We’ve simplified the error information the SDK emits to no longer include AVPlayer-specific data that wasn’t used or persisted after receipt by Mux.
We’ve included a privacy manifest file in our SDK for monitoring Kaltura player performance analytics on iOS and tvOS. This satisfies Apple’s new requirements for third-party SDKs to outline privacy practices associated with their use. We’ve also updated Kaltura player and Mux Core dependencies to more recent versions.
We’ve included a privacy manifest file in our SDK for monitoring AVPlayer performance analytics. This satisfies Apple’s new requirements for third-party SDKs to outline privacy practices associated with their use. Customers who export data from Mux for additional processing may need to include additional privacy manifest entries with their application subject to their specific practices.
We’ve added support for monitoring AVPlayer when using AVPlayerViewController on visionOS. We also fixed a potential memory leak that can occur when monitoring AVPlayer with a fixed player size.
We’ve added referential safety checks when the SDK processes SESSION-DATA tags intended for Mux Data. This fixes a crash that may be triggered in v3.5.0 of the SDK earlier.
The Mux Data Metrics EBVS calculation has been updated to consider views that end while in a paused state and have never played content as an exit before the video was started. This update restores the previous behavior that was changed on February 28th, 2024.
We have added two new metrics, viewer_experience_score
and watch_time
, to the List Video Views API response.
https://docs.mux.com/api-reference#data/operation/list-video-views
The Mux Data Overview, Metrics, Errors, and Views pages - and the Mux Data Metrics APIs - now support one-minute granularity for chart aggregations and custom time range selection. The chart data will be aggregated at one-minute intervals for any time range that is less than 90 minutes. The custom range time picker has been updated to support one-minute time intervals along with other improvements.
One-minute granularity is available to all Mux Data users.
Mux Data has rolled out fixes and improvements for counting views that paused for an hour without sending any heartbeat. This fixed a double-counting issue on the pre-paused section of the view which later paused more than an hour and then resumed. The improvement also allows you to gain access to the pre-paused section of the view, which previously was not possible.
As a result of this roll-out, you may notice that the total view count has a 0.5% - 1% decline, and the Playback Failure Percentage will have a small decline, typically in the range of 0.03 to 0.3 points, thanks to eliminating the double counting issue. Other metrics will be slightly impacted too for the same reason. The changes to the metrics are available in the Mux Dashboard and View Streaming Export.
Most views that resume after an hour should now be considered new views and have different view_ids associated with them if you are on the latest SDKs.
This update adds the `viewDrmType` property to `CustomerViewData`, allowing you to provide your own values if that fits your use case. There’s also been a few under-the-hood improvements around event handling.
Mux Data now supports exporting data for View Streaming Exports in JSON format. This makes it much easier to connect the data stream with data stores such as BigQuery and Snowflake. Customers can easily set it up by going to Mux Dashboard -> Settings -> Streaming Export -> New streaming export -> make sure to select “JSON” as the export format.
The fields that are included in the streaming export’s JSON format are identical to what we support in the protobuf format, which can be found in this repo. When new fields are made available, the export needs to be upgraded to receive new fields: Mux Dashboard -> Settings -> Streaming Export -> Click Upgrade to receive the new fields. For more schema management information, check out this guide.
The Mux Dashboard will now format date timestamps in the localized format of the Dashboard user. Previously, date timestamps would be translated to the localized timezone but displayed in the US-en format. Dates will continue to be translated to the localized timezone and will now be shown in the local format as well. There is no change to API responses.
You can now collect and see additional information for each view in Mux Data. This information can be found via Mux Dashboard, Mux Data API, or View Streaming Exports. The full list of changes include the following:
view_dropped_frame_count
.view_drm_type
metadata. The value is found in the Mux Dashboard by going to a View page and looking for “DRM Type” in the “Video Metadata” section. It is available from the API in the Video View properties as view_drm_type
.player_error_context
to provide additional error instance-specific information that will not impact the default error aggregation. The data can be found in the API, exports, and the Mux Dashboard by going to a View page and it will be shown in the error box on the top of the page.These properties are available for collection in the newest SDKs for Mux-Embed Player, Shaka Player, AVPlayer, HLS.js Player, Dash.js Player, and Roku. The updates for ExoPlayer will be available soon!
Additional Links:
Details of each rendition change event are now reported, when they occur during a view. The information provided in each rendition change includes: rendition width, height, fps, codec, and rendition name. You can also find the playhead time and wall clock time when these changes happen. The rendition change is surfaced through the Mux Dashboard, Data API, and the streaming exports for raw view data. Note that not all data is available from every player, the specific metadata reported will depend on player API support.
Full renditionchange
metadata is collected on the latest version of the following SDKs:
An updated ExoPlayer SDK will be available soon.
Version 3.1.0 of the Mux Data SDK is now available. This update adds APIs to override the detected category of a user’s device (phone
, tablet
, kiosk
, drone
, or anything
), as well as things like OS version or device manufacturer. This version also includes a fix for renditionchange
events on ExoPlayer r2.11.x, as well as a fix related to verbose beacon logging.
See our release notes for more information! Full changes can be found here as well.
Version 3.0.0 of the Mux Data SDK for AVPlayer is now available on SwiftPM and Cocoapods. This version adds support for overriding device-related metadata, such as OS name and version, device type, and so on. This update also adds official support for iOS 16, although apple updates have forced us to remove support for iOS versions 9 and 10.
For more information, see our release notes and our development guide
Version 0.9.0 of the Mux Data SDK for IMA Ads is now available. This update also adds official support for iOS 16, although recent updates to Google’s IMA SDKs have removed support for all iOS versions before 12.0
For more information, see our release notes and our development guide, and full changes.
The Mux Data View Details page has been enhanced to show the detailed metadata in the view timeline for renditionchange
events. See here for information on the metadata that may appear: https://docs.mux.com/guides/data/mux-playback-events#renditionchange-optional
This update fixes player size and full-screen detection for users who are using MuxStatsExoPlayer.setPlayerSize()
to manually override the detected size of their player. The method now takes physical pixels, as documented. If you are using MuxStatsExoPlayer.setPlayerSize()
, you may need to update your code to supply physical pixels instead of density-independent pixels.
This release of the Mux Data SDK for ExoPlayer adds support for ExoPlayer v2.18.1 and a couple of bug fixes related to uncommon use cases. The SDK should be more stable when used with custom builds of ExoPlayer. We also fixed a data integrity issue related to views with very long periods of user inactivity.
This update of the Mux Data SDK for Exoplayer fixes some build issues experienced by customers that are using custom ExoPlayer builds, or are only using exoplayer-core
. If you’re using the full ExoPlayer library and getting it via Maven Dependency, then your build should be unaffected. For more information, see the Github Issue regarding this issue, the Github Release for v2.7.2, the Github repo: mux-stats-sdk-exoplayer, and the Guide: Monitor Exoplayer.
We have fixed an issue that could cause missing seek events in Mux Data when seeking in a video using the player API in iOS 15. Read the Release Notes for more information and a list of additional fixes.
We have fixed an issue that could cause missing seek events in Mux Data when seeking in a video using the player API. Read the Release Notes for more information.
We've fixed an issue where playerID
is null
when the react-native-video
component is wrapped with react-native-video-controls
, which caused an error during video playback. Read the Release Notes for more information.