v5.0.0

⚠️ Heads up, this is a large regeneration that brings this SDK up to date with the API. This changelog may be incomplete, and there may be some (minor) breaking changes.

Specifically, the type of the data field of the ListRealTimeMetricsResponse has changed from ListRealTimeDimensionsResponseData to ListMonitoringDimensionsResponseData.

General:

• Assorted documentation improvements
• Brings SDK up to date with the API, there's lots of changes here and a risk that the changelog may be incomplete.

Mux Video:

• Added Multi-track Audio
• Added 4K & max_resolution_tier
• Added Encoding tiers
• Added Generated captions (beta)
• Deprecated max_stored_resolution, replaced with resolution_tier
• Add new generic signing keys API
• Add transcription vocabularies API
• Fix signing keys tests
• Add new non standard input reasons
• Improve recording times API
• Add reconnect slates
• Support delivery reports by resolution
• Add Live generated subtitles

Mux Data:

• Added Video startup failure
• Added Monitoring breakdown timeseries
• Added Monitoring API
• Support filtering realtime by timestamp
• Support custom dimensions in video view
• Assorted bugfixes and API improvements

v4.2.3

• Fixed API URLs for Spaces calls. You may now Space at your leisure.

v4.2.2

Changed Operations

• get-realtime-breakdown: fixed timestamp definition to correctly reflect that it's an integral timestamp (bug in our backing specification). This is a breaking change, but we have elected to release it as a patch because it's a breaking change to something that never worked correctly and should have extremely minimal disruption to existing operations.

v4.2.1: Mux Real-Time Video

• Mux Real-Time Video is live! As discussed at TMI, we're so happy to announce Mux's solution to real-time video. Learn more about Mux Spaces here and check out our documentation right over here.

v4.1.0

Changed Operations

• create-live-stream: added max_continuous_duration
• update-live-stream: added max_continuous_duration

Miscellaneous

• began the process of exhaustively documenting Mux Data for property nullability
• big documentation updates: text track statuses, playback IDs, better examples, property deduplication, and more!

For more information, consult the API reference at https://docs.mux.com/api-reference/video .

Thanks for using Mux!

v4.0.2

Build configurations release. See v4.0.0 for actual changes.

v4.0.0 (breaking change!)

Breaking Changes (SDK Behavior)

• LiveStreamStatus, used in the LiveStream model (./model_live_stream.go) and in ListLiveStreamsParams (./api_live_streams.go), has changed from a string to type LiveStreamStatus string, to encapsulate its enum values. You may need to add explicit casts to your code where you are using this value, but the allowed values have not changed.
  • This is an unfortunate side effect of our OpenAPI generator for mux-go; now that two different parts of the codebase are using live stream status, validation logic as extracted and refactored. Thanks for your forebearance. We try not to rev this unnecessarily, but we didn't want you getting caught out by duplicate logic in your own code too. 🙏

Bugs Fixed

• PlaybackRestrictionResponse and ListPlaybackRestrictionResponse models are now correct.

Changed Operations

• added live_stream_status query to list-live-streams

New Operations

No new operations.

For more information, consult the API reference at https://docs.mux.com/api-reference/video .

Thanks for using Mux!

v3.2.0

Changed Operations

• added embedded_subtitles to LiveStreamResponse
• added live_stream_id to list-delivery-usage

New Operations

• update-live-stream
• update-asset
• create-playback-restriction
• list-playback-restrictions
• delete-playback-restriction
• get-playback-restriction
• update-referrer-domain-restriction

For more information, consult the API reference at https://docs.mux.com/api-reference/video .

Thanks for using Mux!

v3.1.0

• Added group_by to get_metric_timeseries_data.
• Some minor bug fixes.

v3.0.0

• breaking change: the max_channel_layout field of Track was an enum and is now an open string, as our internal implementation couldn't realistically and exhaustively enumerate all possible options. This should be a very small change that applies only to projects ingesting media with multi-channel, non-stereo audio (5.1, 7.1, etc.). for mux-go specifically, this breaking change is logical rather than in code, as our current OpenAPI templates do not validate enums; doing so is on the roadmap. We wanted to still go with a breaking change to signal to our users that the contract for their application has changed.
• no, you're not missing a 2.x release - we've bumped this to 3.x to synchronize version numbering across our SDKs.