Mux Video's support for receiving live streams over Secure Reliable Transport (SRT) is now generally available, and recommended for production usage. Using SRT can increase the reliability of live streams being sent over imperfect networks. Streams sent to Mux over SRT can optionally be sent with the HEVC codec to reduce network bandwidth requirements.
Mux Video now supports configuring a playback restriction to filter playback requests by the User-Agent HTTP header. It is possible to filter both traffic with no user agent, as well as known high-risk user agents, as defined internally by Mux. This feature can be used alongside signed URLs and referrer restrictions, to increase the security of your video delivery.
The mp4_support
field used to create static MP4 renditions for an asset now supports 3 new options, including an option to produce an audio-only MP4. These should be used instead of the now deprecated standard
value.
capped-1080p
, which produces a single MP4 rendition up to 1080p in resolution.audio-only
, which produces a single audio-only MP4 rendition.audio-only,capped-1080p
, which produces both.The tabs in the Asset and Live Stream Details pages in the dashboard have been renamed to give a more clear indication of what information is shown in each tab.
For Assets:
Monitor -> Events, Logs, and Engagement
Build -> Playback and Thumbnails
Details -> Asset Details
For Live Streams:
Monitor -> Events, Logs, and Engagement
Build -> Playback and Thumbnails
Details -> Live Stream Details
Mux Video now supports receiving live streams over the Secure Reliable Transport (SRT) protocol, which can increase the reliability of live streams being sent over imperfect networks. Streams sent to Mux over SRT can optionally be sent with the HEVC codec to reduce network bandwidth requirements.
You can now sign up for our Starter plan, which is $10/mo for $100 of usage and includes access to all Mux products. Usage over $100 transitions to pay as you go rates. No commitment, cancel anytime. A credit card is required to activate the plan.
Mux Video's auto-generated captions for on-demand video is now in general availability. We have also added a new API to allow captions to be generated retroactively for assets created in the last 7 days.
Automatic Cold Storage is now available. Assets will automatically transition to Cold or Infrequent based on when they were last viewed, and will be less expensive to store. Assets must have MP4s disabled to qualify.
Mux Real-Time Video and Mux Studio have been shut down and are no-longer available for use. This includes the /spaces and /studios APIs, which are no-longer available. Mux's Live and On-Demand Video streaming features are unaffected.
Auto-generated captions for on-demand video now supports 21 additional languages, including Spanish, Italian, Portuguese, German, Polish, Russian, Dutch, Catalan, French, Turkish, Swedish, Ukrainian, Norwegian, Finnish, Slovak, Greek, Czech, Croatian, Danish, Romanian, and Bulgarian.
Mux Video's low-latency mode is now in general availability.
Mux Video now supports 2 new playback modifiers, min_resolution
and rendition_order
. min_resolution
allows developers to limit the renditions available by a minimum resolution, for example 720p
. rendition_order
allows developers to set the order renditions appear in the manifest.
Mux Video now supports a new type of on-demand asset with free video encoding. Baseline assets are a cost-effective option for video applications that have simpler quality needs. The standard tier of video encoding is now referred to as "smart" encoding, and offers superior visual quality and scalability for video-centric applications.
Auto-generated captions can now be enabled on Mux Video Assets through the API at asset creation time. Additionally, a plain text transcript of the video is available for assets where auto-generated captions are enabled.
Mux Video now supports ingesting, storing, and delivering videos at 4K resolutions (2160p), allowing customers to deliver higher quality video content to viewers.
Mux Video now supports adding alternate audio tracks to a video asset. This can be used to allow users to pick between different audio languages, to add director's commentary, or to increase accessibility with descriptive audio.
The max_stored_resolution
field on Assets has been deprecated, and replaced with the more accurate resolution_tier
field. The Mux Dashboard has also been updated to display this field. All previously ingested Assets have been backfilled with the new resolution_tier
field.
We now have 2 new SDKs for handling Direct Uploads from mobile applications. Mux Uploader for iOS and Android have been released in beta. Mux Uploader will handle file splitting and chunking logic to optimize upload speed and in cases of non-standard input Mux Uploader will process the video on the client in order to minimize the time it takes for the asset to be playable after upload.
See more
In order to improve security of RTMPS (RTMP over TLS) connections, we have deprecated TLS versions 1.0 and 1.1 (which are considered insecure) for our live ingest endpoints.
At this time, only TLS versions 1.2 and 1.3 are supported, however the older versions are not immediately being disabled. We strongly recommend that any clients connecting using these obsolete TLS versions be upgraded promptly. Unencrypted RTMP remains available.
Spaces has been removed from the navigation bar on the left of dashboard.mux.com for those who are not utilizing Mux Real-Time Video. Reach out to real-time-video@mux.com if you have any questions.
We’ve added more features to the Build tab for both Assets and Live Streams. You can now create thumbnails, gifs, and timeline hover previews with storyboards for Assets and Live Streams right from the Dashboard.
The Build tab for Spaces has two new sections - one for integrating, another for broadcasting - that direct users on how to best build a Real Time experience with Mux.
We’ve improved the Viewer Engagement metrics in the Monitor tab for both Assets and Live Streams by adding 7 day historical View and Overall Viewer Experience data. We removed the “unique viewers” and “updated (x)s ago” counters for clarity - current views will continue to update live. We’ve also improved the null state for clarity.
Passthrough Data is now shown in the Details tabs in Assets and Live Streams for better visibility and use.
We have updated the Details pages for Spaces to helpfully organize information into tabs. The new Monitor tab contains Recent Events and Logs, while Build has useful information about the Broadcast and integrating into your applications. We’ve also improved the user experience for Deleting a Space.
Participants in a Real-Time Video session who are not publishing a video or audio track no longer appear in broadcasts. All participants with the subscriber
role are also now hidden from broadcasts. For more information, see our Guide to using Real-Time Video Broadcasts.
iOS and Android SDKs for Mux Real-Time Video (Spaces) have been released to General Availability. This 1.0.0 release of both SDKs includes new features (Custom Events, Display Names), performance improvements, and bug fixes. Please refer to the GA blog post for more details.
Mux Real-Time Video now supports customizable participant display names. Participant display names can be set, updated, and retrieved within your own application using the web SDK, and will appear overlaid on any broadcasts of your sessions.
Version 1.2.0 of the Spaces Web SDK has been released. This version adds support for setting, updating, and retrieving participant display names.
Spaces Web SDK 1.2.0 Release Notes.
Guide to using participant display names.
We have updated the Asset and Live Stream Details pages to organize content into tabs to help find information faster. Live Stream Details has also been updated to show key information used to identify the live stream more clearly at the top of the page and be more responsive - it is now easier to see and copy critical information when on mobile devices or smaller screens.
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.
Mux currently supports videos with 8-bit color profiles. Converting video from 10-12 bit formats – such as HDR, HLG, and DolbyVision – to spec compliant 8-bit video, such as BT.709, isn’t something that we currently support. Previously all 10- and 12-bit colorspace assets would be naively transcoded to 8-bit video, but streams that originally had PQ colorspace would fail to play on some devices. In the future, we may improve our handling of these files and accept them. However, in an effort to provide more reliable functionality, we will now fail the ingest task. Please convert these files to 8-bit color, such as 4:2:0 mpeg(tv) range video BT.709, before sending them to ingest into Mux.
A new Live Stream Health Stats API is now available in Public Beta for developers to get live ingest health status. For example, you can call the API to return the live stream stats to your streamer during a live event, so that the streamer can monitor the status and take actions when issues occur.
Read this documentation for more information.
Mux Real-Time Video now supports a crop
broadcast layout, which crops the input real-time video on the fly, squeezing in the edges of a participant's video, to maximize the use of your output livestream’s resolution.
Blog post announcing crop layout.
Guide to using Real-Time Video Broadcasts.
We have updated the Asset Details page to show key information used to identify the asset more clearly at the top of the page.
We have improved the responsiveness of the Asset Details page in the Dashboard for VOD content. It is now easier to see and copy critical information when on mobile devices or smaller screens.
This update to the web SDK for Spaces includes a bugfix for when subscriber
role participants try leaving a Space, error handling when trying to publish no tracks, automatically unpublishing screen-share audio when the browser dialog is closed, and additional documentation for the helper function to create LocalTracks from a MediaStream.
This update to the web SDK for Spaces includes the ability to publish custom events in the session, a helper function to create LocalTrack
s from a MediaStream
, changing the default subscriptions from 20 to 16, and enforcement of published track limits. For more details, see the Spaces Web SDK 1.1.0 Release Notes.
You can now export your Live Stream Input Health data to your infrastructure using the Streaming Exports feature. You can send the Live Stream Input Health messages that occur every five seconds for each active Live Stream to an Amazon Kinesis or Google Pub/Sub endpoint in your cloud account. The docs provide a how-to guide for more detailed information. Please note that this feature is available to customers on a Media plan, or if it has been added as part of a Mux Video contract. You can find this feature by going to the Settings menu in your Mux Dashboard and click on the “Streaming Exports” option. If that option is not available in your Mux Dashboard, contact our sales team if you would like more information.
Mux now supports webp images for storyboards, thumbnails, and GIFs. Webp images increase website performance due to smaller image sizes compared to JPEG and PNG. Increased page speed due to more lightweight images decreases bandwidth and can positively impact site ranking in search engines.
Users can now upload files from their local machine via the Dashboard. The upload flow utilizes our Direct Uploads flow, and illustrates what APIs are used behind the scenes.
Mux Real-Time Video (Spaces) has been released to General Availability. This update includes updated SDKs for all platforms, multi-region support, user experience report collection, and additional improvements and bug fixes. Please refer to the following for more details:
Version 1.0.0 of the Spaces Web SDK has been released. This version adds user experience reporting, QoS tracking, automatic reconnect handling on poor networks, and additional improvements and bug fixes. For more information: Spaces Web SDK 1.0.0 Release Notes
Mux has released version 7.0.0 of its NodeJS SDK. This release fixes some type issues for customers using TypeScript, and adds some missing module exports. In addition, it adds support for signing JavaScript Web Tokens (JWTs) for Mux Real-Time Spaces. In order to support signing of Spaces, the JWT.sign
method has been deprecated in favor of separate JWT.signPlaybackId
and JWT.signSpaceId
methods.
A single playback restriction contains a list of domains allowed to play your videos. You may allow up to 10 unique domains or sub-domains where your videos will be embedded. We’ve raised the limit for the number of playback restrictions per environment from 5 to 100. You can read more in our Docs.
We’ve released Reconnect Window support to general availability for all modes of live streams, including reduced & low latency, in Beta. Reconnect Window is the time in seconds you want Mux to wait for the live stream to reconnect before considering it completed and generating a recorded asset. Slate image is also in general availability. Add a slate image as a video frame during live stream interruptions to let your viewers know the video isn’t over and you’re trying to reconnect. During beta, we stabilized the feature by fixing problems that were causing occasional crashes.
We’ve released Custom Domain for Mux Video to General Availability. You can stream videos or serve images from your branded domain instead of from stream.mux.com
and image.mux.com
.
We’ve increased the maximum value of the live stream’s reconnect_window
parameter from 5 minutes (300 seconds) to 30 minutes (1800 seconds). Reconnect Window is the time in seconds you want Mux to wait for the live stream to reconnect before considering it completed and generating a recorded asset. For many scenarios, Reconnect Window of 5 minutes just was not long enough, like an encoder machine reboot. You can set the reconnect_window
parameter with live stream Create API and Update API endpoints.
We’ve released Reconnect Window support for all modes of live streams, including reduced & low latency, in Beta. Reconnect Window is the time in seconds you want Mux to wait for the live stream to reconnect before considering it completed and generating a recorded asset. You can also add a slate image as a video frame during live stream interruptions to let your viewers know the video isn’t over and you’re trying to reconnect. You can read more on docs and the blog post.
We’ve released Custom Domain for Mux Video to Beta. You can stream videos or serve images from your branded domain instead of from stream.mux.com
and image.mux.com
. You can learn more about Custom Domains, reasons to use, and information on requesting access from the announcement blog.
By providing technical terms and proper names to us before a live stream, we can increase the accuracy of auto-generated live closed captions. Create a transcription library by making a POST
request to the /transcription-vocabularies
endpoint and define the input parameters.
Closed captions refer to the visual display of the audio in a program. Auto-generated live closed captions use Artificial Intelligence based speech-to-text technology to generate closed captions. You can enable live auto-generated captions by adding the generated_subtitles
array at time of stream creation or to an existing live stream.
We have deprecated the add_audio_only
query parameter on stream.mux.com. The add_audio_only
parameter added an audio-only variant to the HLS manifest. However, this audio-only variant is no longer required as Apple’s HLS authoring spec no longer mandates this. In addition, many video players across web and mobile do not support this audio-only variant. For these reasons, Mux has chosen to deprecate this feature.
We've added version 0.1.0 of our mux-java
SDK. This is the initial release of the Mux Java SDK. New SDK versions typically introduce new features, bug fixes, and updates. You can read more in the 0.1.0 Release Notes and also on the package manager Maven. This is a release that we're confident is stable and usable in production, but we would love any customer feedback! To submit feedback, please email sdks@mux.com.
We've added version 3.4.0 of our mux-php
SDK. New SDK versions typically introduce new features, bug fixes, and updates. You can read more on the 3.4.0 Release Notes.
We've added version 0.1.0 of our mux-csharp
SDK. This is the initial release of the Mux C# SDK and it reflects the current state of the Mux API. You can read more on the 0.1.0 Release Notes. You can also view the NuGet package and GitHub repository. This is a release that we're confident is stable and usable in production, but we would love any customer feedback! To submit feedback, please email sdks@mux.com.
If you are a new Mux Video user, you can enjoy an updated getting started experience. The new Assets and Live Streams pages make it easy to upload your first video, find in-context onboarding guidance and get quick links to support and documentation. Users who have already uploaded a video no longer see the Getting Started link in the navigation.
We've added version 3.4.0 of our mux-ruby
SDK. New SDK versions typically introduce new features, bug fixes, and updates. You can read more on the 3.4.0 Release Notes.
We've added version 4.1.0 of our mux-go
SDK. New SDK versions typically introduce new features, bug fixes, and updates. You can read more on the 4.1.0 Release Notes.
We've added version 3.4.0 of our mux-python
SDK. New SDK versions typically introduce new features, bug fixes, and updates. You can read more on the 3.4.0 Release Notes.
We now support 5fps to 10fps as standard input which means you do not need to wait as long for ingest. Previously, all assets with a frame rate of less than 10fps were considered non-standard inputs. See our guide about why non-standard inputs take longer to process
We’ve added the max_continuous_duration
parameter to Live Streams. You can now set the maximum duration for recording a single live stream event lower than 12 hours. Set the max_continuous_duration
parameter during Live Stream creation or update an existing live stream. On hitting the duration, the behavior is the same as signaling the live stream has finished. For more information, see the Live Stream API and the Signal a live stream has finished API.
We’ve added a new status
filter to the List Live Streams API endpoint. With this new filter, you can get a list of all live streams that have active
or idle
or disabled
status. This list is sorted by live stream’s creation time from most recent to oldest. You can learn more in the API Reference.
We've added version 4.0.0 of our mux-go
SDK. New SDK versions typically introduce new features, bug fixes, and updates. You can read more on the 4.0.0 Release Notes.
We've added version 3.3.0 of our mux-ruby
SDK. New SDK versions typically introduce new features, bug fixes, and updates. You can read more on the 3.3.0 Release Notes.
We've added version 3.3.0 of our mux-php
SDK. New SDK versions typically introduce new features, bug fixes, and updates. You can read more on the 3.3.0 Release Notes.
We've added version 3.3.0 of our mux-python
SDK. New SDK versions typically introduce new features, bug fixes, and updates. You can read more on the 3.3.0 Release Notes.
We now support non-square pixels as standard input which means you do not need to wait as long for ingestion. Previously, we supported non-square pixels as non-standard input. See our Guide to learn more about this change and why non-standard inputs take longer to process.
We've added version 3.2.0 of our mux-ruby
SDK. New SDK versions typically introduce new features, bug fixes, and updates. You can read more on the 3.2.0 Release Notes.
We've added version 3.2.0 of our mux-go
SDK. New SDK versions typically introduce new features, bug fixes, and updates. You can read more on the 3.2.0 Release Notes.
We've added version 3.2.0 of our mux-php
SDK. New SDK versions typically introduce new features, bug fixes, and updates. You can read more on the 3.2.0 Release Notes.
We've added version 3.2.0 of our mux-python
SDK. New SDK versions typically introduce new features, bug fixes, and updates. You can read more on the 3.2.0 Release Notes.
We’ve introduced Referrer Validation, a new method of Playback Restrictions to secure your videos. You can restrict your videos to play only on your approved websites with Referrer Validation. Mux validates the requesting website against your approved list by examining the HTTP Referrer header sent by the Web browser. This feature requires the use of Signed URLs. You can read more on the Blog Post, API Reference, and Guide.
We’ve added the PATCH method to several API endpoints for updating Assets & Live Streams. You can update the passthrough
parameter value of Assets & Live Streams anytime after creating them. Similarly, you can update the latency_mode
and reconnect_window
parameter values of Live Streams. For more details, see the Live Streams PATCH API or Assets PATCH API documentation.
Streamers can broadcast on the same Live Stream multiple times, each time creating a new video asset. We’ve added a new live_stream_id
filter to the Delivery Usage API. With this new filter, you can get delivered minutes usage information for all the video assets created from a single live stream. You can learn more from the API Reference.