• /
  • EnglishEspañolFrançais日本語한국어Português
  • Log inStart now

Streaming Video & Ads for Browser release notesRSS

August 11
Media agent for Video JS v4.2.1

New features

  • Added optional automatic rendition/quality-level change tracking: integrates with the videojs-contrib-quality-levels plugin (when present) to report quality transitions along with the previous and new bitrates, with a graceful fallback when the plugin isn't loaded.

August 6
Media agent for Dash JS v5.0.1

Bug fixes

  • Updated the bundled @newrelic/video-core dependency to v5.0.1, adding Japan(JP) region collector support for Vega/Fire TV tracking.

August 6
Media agent for HTML5 v5.0.1

Bug fixes

  • Updated the bundled @newrelic/video-core dependency to v5.0.1, adding Japan (JP) region collector support for Vega/Fire TV tracking.

August 6
Media agent for Shaka v5.0.1

Bug fixes

  • Updated the bundled @newrelic/video-core dependency to v5.0.1, adding Japan(JP) region collector support for Vega/Fire TV tracking.

July 29
June 29
Media agent for HTML5 v4.1.2

What's changed

New Contributors

Full Changelog: https://github.com/newrelic/video-html5-js/compare/v4.1.1...v4.1.2

June 19
Media agent for Video JS v4.2.0

Highlights

  • Explicit opt-in for AWS MediaTailor, with full support for custom CDN domains.
  • New config.ad.type API to choose between CSAI and SSAI (DAI, MT) ad tracking — no more URL-based guessing for SSAI.
  • End-to-end logging through nrvideo.Log, with active detection mode logged at startup.

Features

MediaTailor custom CDN support

Replaced URL-based auto-detection with explicit opt-in.

  • Enabled the tracker via mediatailor: true (or mediatailor: { trackingUrl, adSegmentPrefix }), supporting both default AWS hostnames and custom CDN domains.
  • Added MT_DEFAULT_AD_SEGMENT_PATH (/tm/) constant for AWS-recommended CDN ad-segment path; ad segments rewritten to a custom CDN domain under /tm/ are detected automatically.
  • Updated isMediaTailorSegment() to check the default AWS segments hostname, the /tm/ path, and an optional customer-supplied adSegmentPrefix.
  • Threaded adSegmentPrefix through HLS (VHS) and DASH manifest parsing.
  • Added explicit session initialization via mediatailor: { trackingUrl } for POST /v1/session/ flows.

Ad tracking configuration

Introduced config.ad.type to control ad tracker selection.

  • Exposed AD_TRACKING constant with CSAI (flat value covering IMA / Brightcove IMA / Freewheel / generic) and SSAI sub-types (DAI, MT).
  • Required an explicit sub-type for SSAI — each platform needs its own SDK and cannot be auto-detected.
  • Mapped SSAI.MT to imply mediatailor: true.
  • Added a fallback to CSAI auto-detection with a warning when config.ad.type is unset (backward compatible for v4.1.2 users).
  • Co-located segmentPrefix and trackingUrl under config.ad.
  • Added DaiAdsTracker to static exports.

Logging improvements

  • Exposed VideojsTracker.Log as a static so UMD callers can set log level.
  • Added logging of the active ad segment detection mode at tracker startup.
  • Added logging of the matched ad segment detection path on the first ad break (once per session).
  • Added logging of which CSAI framework was auto-detected (BrightcoveIma / IMA / Freewheel / generic).
  • Replaced console.log/warn/error with nrvideo.Log across MediaTailor files.

Bug fixes

  • Fixed buffer end handling in tracker.
  • Fixed register-plugin.js silently dropping the options object and not forwarding it to the TrackerJS constructor.

Documentation

  • Updated the README and SSAI docs for custom CDN support, clarified when trackingUrl and adSegmentPrefix overrides are needed, and cleaned up sessionId references.
  • Corrected adSegmentPrefix references to config.ad.segmentPrefix in the SSAI troubleshooting docs.

Upgrade from 4.1.x

  • No breaking changes for CSAI users. If config.ad.type is unset, the tracker still auto-detects CSAI frameworks (with a one-time warning).
  • MediaTailor users must opt in explicitly. Replace any URL-pattern reliance with one of:
    • mediatailor: true (default AWS hostnames + /tm/ path)
    • mediatailor: { trackingUrl, adSegmentPrefix } (custom CDN / explicit session init)
    • config.ad.type: AD_TRACKING.SSAI.MT
  • If you previously passed adSegmentPrefix at the top level, move it to config.ad.segmentPrefix.

May 13
Media agent for Video JS v4.1.2

Highlights

  • Added MediaTailor SSAI tracker initialization on loadstart after source load detection.
  • Added DAI stream manager support through the stream-manager event.
  • Improved bitrate reporting with:
    • Playback bitrate (AVERAGE-BANDWIDTH/BANDWIDTH)
    • Manifest max bitrate
    • Segment download bitrate
    • Network throughput bitrate

Improvements

  • Refined ad and content event handling to avoid duplicate or incorrect content events while ads are active for following events:
    • Pause/Resume
    • Seek Start/End
    • Buffer Start
  • Improved end-of-content handling for ad-enabled playback paths during IMA and Freewheel scenarios.
  • Added safer fallback logic for tech wrappers (Hls.js, Shaka, contrib-hls) when bitrate data is unavailable in VHS.

Technical notes

  • Tracker metadata and playback context methods remain aligned with Video.js/Brightcove integrations:
    • Retrieves the title, ID, and duration from mediainfo when available.
    • Retrieves source and rendition data from the active tech component when available.
  • Updated the Listener registration and unregistration to include ad and stream manager lifecycle events.

April 17
Media agent for HTML5 v4.1.1

What's changed

Documentation

  • README Overhaul: Restructured and expanded README with comprehensive installation guides, usage examples, best practices, configuration options, API reference, and support channels.

Improvements

  • Attributes Validation: Updated validation logic for custom attributes to enforce correctness at the tracker level.
  • Custom Attributes Limit: Added an enforced limit on the number of custom attributes that can be sent per event, preventing unexpected payload sizes.

Installation

bash
$
npm install @newrelic/video-html5@4.1.1

Full changelog

March 9
Media agent for Shaka v4.0.3

This release introduces three new bitrate metrics for granular playback observability, QoE (Quality of Experience) support, and Shaka Player 5.x compatibility while maintaining backward compatibility with Shaka 4.x.

New bitrate metrics

Three new attributes are now available to provide deeper insight into streaming performance:

Attribute

Source

Description

contentManifestBitrate

stats.streamBandwidth

Total variant bitrate (video + audio) as declared in the manifest (Indicated Bitrate).

contentMeasuredBitrate

stats.estimatedBandwidth

Estimated network bandwidth measured by Shaka's ABR algorithm (Observed Bitrate).

contentDownloadBitrate

(bytesDownloaded × 8) / playTime

Effective download throughput across all downloaded media.

Additionally, contentBitrate uses track.videoBandwidth (video-only bitrate) to differentiate it from other metrics that report combined video and audio bandwidth.

Quality of Experience (QoE) support

QoE aggregate events are now supported via video-core. Enable them by setting qoeAggregate: true in the config:

const options = {
info: {
beacon: 'xxxxxxxxxx',
applicationID: 'xxxxxxx',
licenseKey: 'xxxxxxxxxxx',
},
config: {
qoeAggregate: true,
qoeIntervalFactor: 2,
},
};
const tracker = new ShakaTracker(player, options);

The following KPIs are tracked automatically:

KPI

Description

startupTime

Time from content request to content start (ms).

peakBitrate

Maximum contentBitrate observed during playback.

averageBitrate

Weighted average bitrate across the session.

hadStartupFailure

true if a content error occurred before content started.

hadPlaybackFailure

true if a content error occurred during playback.

totalRebufferingTime

Total time spent rebuffering (ms).

rebufferingRatio

Rebuffering time as a percentage of total playtime.

totalPlaytime

Total content playtime (ms).

numberOfErrors

Total number of errors during the session.

Shaka Player 5.x compatibility

The tracker is now compatible with both Shaka Player 4.x and 5.x:

  • getPlayerVersion() resolves version across both major versions.
  • onError() handles both Shaka player errors (e.detail) and HTML video element errors (e.target.error).
  • Sample files updated for Shaka 5.x (removed deprecated shaka.polyfill.installAll(), updated player instantiation).

Upgrade guide

Run the following following to update:

bash
$
npm install @newrelic/video-shaka@4.0.3

To enable QoE, add qoeAggregate: true to your config options as shown above.

Dependencies

Requires @newrelic/video-core v4.1.1 or later for QoE support.

Copyright © 2026 New Relic Inc.

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.