- Learn >
- Release notes >
- Media delivery >
- Media Services Live
Browse By Category
-
Web Performance
-
Media Delivery
-
Cloud Security
-
Enterprise Security
-
Core Features
- Akamai Test Center
- Alerts
- Billing Center
- Certificate Provisioning System
- Client Access Control
- Content Preparation
- Control Center Authentication
- Diagnostic Tools
- Edge Hostname
- Event Center
- Firewall Rules Notification
- Identity Management
- Log Delivery Service
- Onboard & Configuration Assistant
- Property Manager
- Purge
- Reporting
- SAML Single Sign-On
- Support
-
Network Operator
- Show All
2018-08-13
The following are the Akamai portal mega menu changes in this release:
Product or application name: MSL
Products at Monitor > Media Services Live are completely ported to new applications.
- Link Monitor > Media Services Live is removed.
- The Stream Packaging product is available at Monitor > Media Services Live > Stream Packaging.
- The HLS/HDS/DASH product is available at Monitor > Media Services Live 4.
Renamed the existing mega menu item for MSL provisioning to be consistent with Reporting navigation:
- Old name: Configure > Media Services Live Ingest
- New name: Configure > Media Services Live 4
Product or application name: MSOD
Renamed the existing mega menu item:
- Old name: Configure > Media Services On Demand > Smooth Streaming Enablement
- New name: Configure > Media Services On Demand > Smooth Streaming
2017-12-01
Media Services Live 4.2 introduces key new features.
New features include:
CMAF pass-through support: You can now ingest a Common Media Application Format (CMAF) stream using MSL 4.2. CMAF is a new media streaming format supported by both DASH and HLS. The Content Ingestion page of the Add New Stream wizard has a new radio button to select CMAF.
Multi-Account Origin Access (Beta): Multi-Account Origin Access enables you to allow Media Services Live streams defined in one account to be delivered by delivery configurations in another account(s). This is achieved by using manual access keys. The stream’s publisher creates a set of keys that they share with those who receive the stream. The publisher uses this key and matches it with the hostname to authenticate and authorize the user and share information.