Skip to content

Add media server 3.5.0 release notes - #797

Open
bcostdolby wants to merge 1 commit into
mainfrom
devin/1785982800-media-server-3-5-0-release-notes
Open

Add media server 3.5.0 release notes#797
bcostdolby wants to merge 1 commit into
mainfrom
devin/1785982800-media-server-3-5-0-release-notes

Conversation

@bcostdolby

@bcostdolby bcostdolby commented Aug 6, 2026

Copy link
Copy Markdown
Collaborator

Summary

Adds the Media Server 3.5.0 entry to millicast/changelog/changelog-dolbyio-platform-media-server.md, same shape as the 3.4.3 entry (#741).

Only customer-visible changes from v3.4.3...v3.5.0 are included:

  • Feature — UTC timestamp insertion. The server can stamp each H.264 frame with its UTC receive time as frame metadata (unregistered SEI, epoch ms) for RTMP/RTMPS/SRT contribution, passthrough and transcoded layers, without re-encoding. Enabled per publish token or per broadcast via enableUTCInsertion. Frames that already carry an onFi/AMF sender time are not overwritten — the note says so explicitly, because enabling it on a source that emits onFi on only some frames produces timestamps that alternate between the encoder clock and the server clock.
  • Fix — a broadcast that stopped immediately after starting could stay reported as active (stream looked like it was still publishing after it ended).
  • Fix — OS/dependency security updates in the media server images, plus general stability.

The rest of the release (per-subsystem EventLoop metrics + Grafana dashboard, a Redis key-growth fix, packer/CI and base-image work, internal tooling) has no customer-visible surface and is deliberately excluded.

Two things for the reviewer:

  • The date heading is 2026-08-06, a placeholder — 3.5.0 has not shipped to production yet. It needs to be set to the actual release date before this merges.
  • enableUTCInsertion is not yet documented in the Publishing Parameters table, so the release note describes the parameter without linking to it. Adding that row (plus a short "reading the timestamp in the player" section) is left as a separate change so it can be reviewed on its own.

prettier --check passes on the modified file.

Link to Devin session: https://dolby.devinenterprise.com/sessions/129703589f184ee59a13ec158d646653
Requested by: @bcostdolby


Open in Devin Review

@bcostdolby
bcostdolby requested a review from a team as a code owner August 6, 2026 02:20
@bcostdolby bcostdolby self-assigned this Aug 6, 2026
@devin-ai-integration

Copy link
Copy Markdown
Contributor

🤖 Devin AI Engineer

I'll be helping with this pull request! Here's what you should know:

✅ I will automatically:

  • Address comments on this PR. Add '(aside)' to your comment to have me ignore it.
  • Look at CI failures and help fix them

Note: I can only respond to comments from users who have write access to this repository.

⚙️ Control Options:

  • Disable automatic comment, CI, and merge conflict monitoring

@devin-ai-integration devin-ai-integration Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Devin Review found 2 potential issues.

Open in Devin Review


#### Features

- Added UTC timestamp insertion for H.264 broadcasts. When enabled, the platform stamps each video frame with the server's UTC receive time as frame metadata (an unregistered SEI message, in Unix-epoch milliseconds), so players and downstream tools can measure end-to-end latency, align multiple feeds, or correlate media with external events. It is available for RTMP, RTMPS, and SRT contribution, applies to both passthrough and transcoded layers, and does not re-encode passthrough video. Enable it on a publish token, or for an individual broadcast with the `enableUTCInsertion` publishing parameter. Frames that already carry an `onFi`/AMF sender timestamp are never overwritten, so this is intended for sources that do not already send timecodes.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🔍 Undocumented publishing parameter referenced without a link

The new entry references the enableUTCInsertion publishing parameter, but that parameter is not present in the Publishing Parameters documentation (unlike other changelog entries which link to related docs such as /millicast/distribution/re-streaming). Readers who follow the changelog will have no place to look up valid values or how to read the SEI timestamp. Worth confirming the follow-up docs change lands close to this release.

Open in Devin Review

Was this helpful? React with 👍 or 👎 to provide feedback.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Known and called out in the PR description: enableUTCInsertion is not yet in the Publishing Parameters table, which is why the note describes the parameter instead of linking to it. The follow-up docs change (parameter row + how to read the SEI timestamp in the player, cross-linked from the frame-metadata guide) is deliberately kept separate for review; flagged to the release owner to land it alongside this.


Updates to Dolby OptiView's Real-time Streaming Platform and Media Server.

## 2026-08-06

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🔍 Release date heading is a placeholder

The date heading 2026-08-06 matches the PR authoring date rather than an actual release date, and the description states 3.5.0 has not yet shipped. Since entries are ordered newest-first by this heading, merging before the real ship date would publish an inaccurate release date to customers.

Open in Devin Review

Was this helpful? React with 👍 or 👎 to provide feedback.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Correct, and intentional — the PR description states this heading is a placeholder that must be set to the actual 3.5.0 production release date before merge. Not changing it here since the ship date isn't fixed yet.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant