您现在访问的是微软AZURE全球版技术文档网站,若需要访问由世纪互联运营的MICROSOFT AZURE中国区技术文档网站,请访问 https://docs.azure.cn.

Azure 媒体服务发行说明Azure Media Services release notes

这些 Azure 媒体服务发行说明汇总了与以前版本相比的变更之处和已知的问题。These release notes for Azure Media Services summarize changes from previous releases and known issues.

备注

媒体服务 v2 中未添加新功能。No new features are being added to Media Services v2.
查看最新版本的媒体服务 v3Check out the latest version, Media Services v3. 另请参阅从 v2 到 v3 的迁移指南Also, see migration guidance from v2 to v3

我们希望能够倾听客户的心声,以便努力解决对客户造成影响的问题。We want to hear from our customers so that we can focus on fixing problems that affect you. 要报告问题或提出问题,请将在 Azure 媒体服务 MSDN 论坛提交问题。To report a problem or ask questions, submit a post in the Azure Media Services MSDN Forum.

已知问题Known issues

媒体服务一般问题Media Services general issues

问题Issue 说明Description
REST API 中未提供几种常见的 HTTP 标头。Several common HTTP headers aren't provided in the REST API. 如果使用 REST API 来开发媒体服务应用程序,将发现一些常见的 HTTP 标头字段(包括 CLIENT-REQUEST-ID、REQUEST-ID 和 RETURN-CLIENT-REQUEST-ID)不受支持。If you develop Media Services applications by using the REST API, you find that some common HTTP header fields (including CLIENT-REQUEST-ID, REQUEST-ID, and RETURN-CLIENT-REQUEST-ID) aren't supported. 未来的更新将增加这些标头。The headers will be added in a future update.
不允许使用百分号编码。Percent-encoding isn't allowed. 为流内容构建 URL 时,媒体服务使用 IAssetFile.Name 属性的值(例如,http://{AMSAccount}.origin.mediaservices.windows.net/{GUID}/{IAssetFile.Name}/streamingParameters)。Media Services uses the value of the IAssetFile.Name property when building URLs for the streaming content (for example, http://{AMSAccount}.origin.mediaservices.windows.net/{GUID}/{IAssetFile.Name}/streamingParameters). 出于这个原因,不允许使用百分号编码。For this reason, percent-encoding isn't allowed. Name 属性的值不能含有任何以下百分号编码保留字符:!* '();:@&=+$,/?%#[]"。The value of the Name property can't have any of the following percent-encoding-reserved characters: !*'();:@&=+$,/?%#[]". 此外,文件扩展名中只能含有一个“.”。Also, there can be only one "." for the file name extension.
Azure 存储 SDK 版本 3.x 中的 ListBlobs 方法会失败。The ListBlobs method that is part of the Azure Storage SDK version 3.x fails. 媒体服务基于 2012-02-12 版本生成 SAS URL。Media Services generates SAS URLs based on the 2012-02-12 version. 如果希望使用存储 SDK 来列出 BLOB 容器中的 BLOB,请使用存储 SDK 版本 2.x 中的 CloudBlobContainer.ListBlobs 方法。If you want to use the Storage SDK to list blobs in a blob container, use the CloudBlobContainer.ListBlobs method that is part of the Storage SDK version 2.x.
媒体服务限制机制会限制那些发出过多服务请求的应用程序的资源使用情况。The Media Services throttling mechanism restricts the resource usage for applications that make excessive requests to the service. 该服务可能返回“服务不可用” 503 HTTP 状态代码。The service might return the "Service Unavailable" 503 HTTP status code. 有关详细信息,请参阅媒体服务错误代码中的 503 HTTP 状态代码说明。For more information, see the description of the 503 HTTP status code in Media Services error codes.
查询实体时,一次返回的实体数限制为 1,000 个,因为公共 REST 第 2 版将查询结果数限制为 1,000 个。When you query entities, a limit of 1,000 entities is returned at one time because the public REST version 2 limits query results to 1,000 results. 使用此 .NET 示例此 REST API 示例中所述的 Skip 和 Take (.NET)/ top (REST)。Use Skip and Take (.NET)/top (REST) as described in this .NET example and this REST API example.
某些客户端可能会在平滑流式处理清单中碰到重复标记问题。Some clients can come across a repeat tag issue in the Smooth Streaming manifest. 有关详细信息,请参阅此部分For more information, see this section.
媒体服务 .NET SDK 对象无法序列化,因此无法与 Azure Redis 缓存配合使用。Media Services .NET SDK objects can't be serialized and as a result don't work with Azure Cache for Redis. 如果尝试对 SDK AssetCollection 对象进行序列化以将其添加到 Azure Redis 缓存,则会引发异常。If you try to serialize the SDK AssetCollection object to add it to Azure Cache for Redis, an exception is thrown.
尝试获取资产或帐户级别筛选器时,REST API 会以一条错误消息做出响应,指出“此版本的 REST API 无法访问筛选器”。The REST API responds with an error message saying “The filter cannot be accessed by this version of REST Api” when attempting to get an Asset or Account level filter. 该筛选器是使用比尝试获取该筛选器所使用的 API 版本更高的 API 版本创建或修改的。The filter was created or modified with a newer API version than is being used to try to get the filter. 如果客户使用的代码或工具正在使用两个 API 版本,则可能会发生这种情况。This can happen if two API versions are being used by code or tools being used by the customer. 此处的最佳解决方案是升级代码或工具,以使用较新版本或两个 API 版本。The best solution here is to upgrade the code or tools to use the newer or the two API versions.

REST API 版本历史记录REST API version history

有关媒体服务 REST API 版本历史记录的信息,请参阅 [Azure 媒体服务 REST API 参考]。For information about the Media Services REST API version history, see the Azure Media Services REST API reference.

2020 年 2 月February 2020

将停用一些分析媒体处理器。Some analytics media processors will be retired. 有关停用日期,请参阅旧组件主题。For the retirement dates, see the legacy components topic.

2019 年 9 月September 2019

弃用媒体处理器Deprecation of media processors

我们将宣布弃用Azure Media IndexerAzure Media Indexer 2 预览版We are announcing deprecation of Azure Media Indexer and Azure Media Indexer 2 Preview. Azure 媒体服务视频索引器替代了这些旧媒体处理器。Azure Media Services Video Indexer replaces these legacy media processors.

有关停用日期,请参阅此旧版组件主题。For the retirement dates, see this legacy components topic.

另请参阅从 Azure Media Indexer 迁移和 Azure Media Indexer 2 迁移到 Azure 媒体服务视频索引器Also see Migrate from Azure Media Indexer and Azure Media Indexer 2 to Azure Media Services Video Indexer.

2019 年 8 月August 2019

弃用媒体处理器Deprecation of media processors

我们宣布弃用 Windows Azure 媒体编码器** (WAME) 和 Azure 媒体编码器** (AME) 媒体处理器。We are announcing deprecation of the Windows Azure Media Encoder (WAME) and Azure Media Encoder (AME) media processors. 有关停用日期,请参阅此旧版组件主题。For the retirement dates, see this legacy components topic.

有关详细信息,请参阅将 WAME 迁移到 Media Encoder Standard将 AME 迁移到 Media Encoder StandardFor details, see Migrate WAME to Media Encoder Standard and Migrate AME to Media Encoder Standard.

2019 年 3 月March 2019

Azure 媒体服务的 Media Hyperlapse 预览功能已弃用。The Media Hyperlapse Preview feature of Azure Media Services was deprecated.

2018 年 12 月December 2018

Azure 媒体服务的 Media Hyperlapse 预览功能即将停用。The Media Hyperlapse Preview feature of Azure Media Services will soon be retired. 从 2018 年 12 月 19 日起,媒体服务不再对 Media Hyperlapse 进行更改或改进。Starting December 19, 2018, Media Services will no longer make changes or improvements to Media Hyperlapse. 在 2019 年 3 月 29 日,它将停用并不再可用。On March 29, 2019, it will be retired and no longer available.

2018 年 10 月October 2018

CMAF 支持CMAF support

CMAF 和“cbcs”加密支持 Apple HLS (iOS 11+) 以及支持 CMAF 的 MPEG-DASH 播放器。CMAF and 'cbcs' encryption support for Apple HLS (iOS 11+) and MPEG-DASH players that support CMAF.

Web VTT 缩略图子画面Web VTT thumbnail sprites

可以使用媒体服务生成使用 v2 API 的 Web VTT 缩略图子画面。You can now use Media Services to generate Web VTT thumbnail sprites using our v2 APIs. 有关详细信息,请参阅生成缩略图子画面For more information, see Generate a thumbnail sprite.

2018 年 7 月July 2018

使用最新的服务版本,当作业失败时,服务返回的错误消息会有一些细微的格式更改,这些更改与如何分解为两行或更多行相关。With the latest service release, there are minor formatting changes to the error messages returned by the service when a Job fails, with respect to how it is broken up into two or more lines.

2018 年 5 月May 2018

自 2018 年 5 月 12 日起,实时频道将不再支持 RTP/MPEG-2 传输流引入协议。Starting May 12, 2018, live channels will no longer support the RTP/MPEG-2 transport stream ingest protocol. 请从 RTP/MPEG-2 迁移到 RTMP 或分段 MP4(平滑流式处理)引入协议。Please migrate from RTP/MPEG-2 to RTMP or fragmented MP4 (Smooth Streaming) ingest protocols.

2017 年 10 月版本October 2017 release

重要

媒体服务支持 Azure 访问控制服务身份验证密钥。Media Services is deprecating support for Azure Access Control Service authentication keys. 2018 年 6 月 22 日起,不再可使用访问控制服务密钥通过代码向媒体服务后端进行身份验证。On June 22, 2018, you can no longer authenticate with the Media Services back end via code by using Access Control Service keys. 必须根据基于 Azure AD 的身份验证一文中所述,将代码更新为使用 Azure Active Directory (AAD)。You must update your code to use Azure Active Directory (Azure AD) per Azure AD-based authentication. 请注意 Azure 门户中有关此更改的警告。Watch for warnings about this change in the Azure portal.

2017 年 10 月更新Updates for October 2017

SDKSDKs

  • .NET SDK 已更新为支持 Azure AD 身份验证。The .NET SDK was updated to support Azure AD authentication. 为鼓励用户尽快迁移到 Azure AD,Nuget.org 上的 .NET SDK 已不再支持访问控制服务身份验证。Support for Access Control Service authentication was removed from the latest .NET SDK on Nuget.org to encourage faster migration to Azure AD.
  • JAVA SDK 已更新为支持 Azure AD 身份验证。The JAVA SDK was updated to support Azure AD authentication. 已向 Java SDK 添加 Azure AD 身份验证支持。Support for Azure AD authentication was added to the Java SDK. 有关如何将 Java SDK 用于 Media Services 的信息,请参阅适用于 Azure 媒体服务的 Java 客户端 SDK 入门For information on how to use the Java SDK with Media Services, see Get started with the Java client SDK for Azure Media Services

基于文件的编码File-based encoding

  • 现可使用高级编码器,针对 H.265 高效率视频编码 (HEVC) 视频编解码器进行内容编码。You now can use the Premium Encoder to encode your content to the H.265 high-efficiency video coding (HEVC) video codec. 选择 H.265 而不是其他编解码器(例如 H.264)不会影响价格。There is no pricing impact if you choose H.265 over other codecs, such as H.264. 有关 HEVC 专利许可证的信息,请参阅联机服务条款For information about HEVC patent licenses, see Online Services Terms.

  • 如果源视频是使用 H.265(HEVC) 视频编解码器编码的(例如,使用 iOS11 或 GoPro Hero 6 捕获的视频),则现在可以使用高级编码器或标准编码器来编码这些视频。For source video that is encoded with the H.265 (HEVC) video codec, such as video captured by using iOS11 or GoPro Hero 6, you now can use either the Premium Encoder or the Standard Encoder to encode those videos. 有关专利许可证的信息,请参阅联机服务条款For information about patent licenses, see Online Services Terms.

  • 对于包含多语言音轨的内容,必须根据相应文件格式规范(例如 ISO MP4)正确标记语言值。For content that contains multiple language audio tracks, the language values must be correctly labeled according to the corresponding file format specification (for example, ISO MP4). 然后即可使用标准编码器编码内容以便进行流式处理。Then you can use the Standard Encoder to encode the content for streaming. 生成的流式处理定位符将列出可用的音频语言。The resultant streaming locator lists the available audio languages.

  • 标准编码器现在支持两个仅限音频的新系统预设:“AAC 音频”和“AAC 优质音频”。The Standard Encoder now supports two new audio-only system presets, "AAC Audio" and "AAC Good Quality Audio." 这两个预设分别生成 128 Kbps 和 192 Kbps 比特率的立体声高级音频编码 (AAC) 输出。Both produce stereo advanced audio coding (AAC) output, at bit rates of 128 Kbps and 192 Kbps, respectively.

  • 高级编码器现支持以 QuickTime/MOV 文件格式作为输入。The Premium Encoder now supports QuickTime/MOV file formats as input. 视频编解码器必须是这篇 GitHub 文章中列出的 Apple ProRes 类型之一。The video codec must be one of the Apple ProRes types listed in this GitHub article. 音频必须是 AAC 或脉冲编码调制 (PCM) 格式。The audio must be either AAC or pulse code modulation (PCM). 高级编码器不支持使用 QuickTime/MOV 文件中包装的 DVC/DVCPro 视频等内容作为输入。The Premium Encoder doesn't support, for example, DVC/DVCPro video wrapped in QuickTime/MOV files as input. 标准版编码器支持这些视频编解码器。The Standard Encoder does support these video codecs.

  • 编码器中进行了以下 bug 修复:The following bug fixes were made in encoders:

    • 现可使用输入资产提交作业。You can now submit jobs by using an input asset. 这些作业完成后,可修改资产(例如添加、删除或重命名资产中的文件),并提交其他作业。After these jobs finish, you can modify the asset (for example, add, delete, or rename files within the asset), and submit additional jobs.
    • 改进了标准编码器生成的 JPEG 缩略图的质量。The quality of JPEG thumbnails produced by the Standard Encoder is improved.
    • 在持续时间极短的视频中,标准编码器现可更好地处理输入元数据和缩略图生成。The Standard Encoder handles input metadata and thumbnail generation better in very short duration videos.
    • 对标准编码器中使用的 H.264 解码器做了改进,消除了某些罕见颗粒。Improvements to the H.264 decoder used in the Standard Encoder eliminate certain rare artifacts.

媒体分析Media Analytics

Azure 媒体编修器正式推出 - 此媒体处理器将会通过模糊化所选个人的脸部来执行匿名化处理,特别适用于公共安全和新闻媒体方案。General availability of the Azure Media Redactor: This media processor performs anonymization by blurring the faces of selected individuals and is ideal for use in public safety and news media scenarios.

有关此新处理器的概述,请参阅这篇博客文章For an overview on this new processor, see this blog post. 有关文档和设置的信息,请参阅使用 Azure 媒体分析来编修面部For information on documentation and settings, see Redact faces with Azure Media Analytics.

2017 年 6 月版本June 2017 release

媒体服务现在支持 基于 Azure AD 的身份验证Media Services now supports Azure AD-based authentication.

重要

目前,媒体服务支持访问控制服务身份验证模型。Currently, Media Services supports the Access Control Service authentication model. 访问控制服务授权将于 2018 年 6 月 1 日弃用。Access Control Service authorization will be deprecated on June 1, 2018. 建议尽快迁移到 Azure AD 身份验证模型。We recommend that you migrate to the Azure AD authentication model as soon as possible.

2017 年 3 月版本March 2017 release

在创建编码任务时,现在可通过指定“自适应流式处理”预设字符串使用标准编码器自动生成比特率阶梯You can now use the Standard Encoder to auto-generate a bitrate ladder by specifying the "Adaptive Streaming" preset string when you create an encoding task. 若要使用媒体服务对视频进行流式处理,请使用“自适应流式处理”预设。To encode a video for streaming with Media Services, use the "Adaptive Streaming" preset. 若要为特定方案自定义编码预设,可从这些预设开始。To customize an encoding preset for your specific scenario, you can begin with these presets.

现在可使用标准编码器或媒体编码器高级工作流来创建生成 fMP4 区块的编码任务You can now use Media Encoder Standard or Media Encoder Premium Workflow to create an encoding task that generates fMP4 chunks.

2017 年 2 月版本February 2017 release

自 2017 年 4 月 1 日起,将自动删除帐户中超过 90 天的所有作业记录及其相关任务记录。Starting April 1, 2017, any job record in your account older than 90 days is automatically deleted, along with its associated task records. 即使记录总数低于最大配额,也会进行删除。Deletion occurs even if the total number of records is below the maximum quota. 若要存档作业/任务信息,可使用使用媒体服务 .NET SDK 管理资产和相关实体中所述的代码。To archive the job/task information, you can use the code described in Manage assets and related entities with the Media Services .NET SDK.

2017 年 1 月版本January 2017 release

在媒体服务中,流式处理终结点表示一个流服务,该服务可以直接将内容传递给客户端播放器应用程序,也可以传递给内容支付网络 (CDN) 以进一步分发。In Media Services, a streaming endpoint represents a streaming service that can deliver content directly to a client player application or to a content delivery network (CDN) for further distribution. 媒体服务还提供无缝 Azure 内容分发网络集成。Media Services also provides seamless Azure Content Delivery Network integration. StreamingEndpoint 服务的出站流可以是媒体服务帐户中的实时流、点播视频或渐进式下载的资产。The outbound stream from a StreamingEndpoint service can be a live stream, a video on demand, or a progressive download of your asset in your Media Services account. 每个媒体服务帐户均包括一个默认的流式处理终结点。Each Media Services account includes a default streaming endpoint. 可以在帐户下创建其他流式处理终结点。Additional streaming endpoints can be created under the account.

有两个版本的流式处理终结点:1.0 和 2.0。There are two versions of streaming endpoints, 1.0 and 2.0. 2017 年 1 月 10 日起,任何新创建的媒体服务帐户都会包括 2.0 版默认流式处理终结点。Starting January 10, 2017, any newly created Media Services accounts include the version 2.0 default streaming endpoint. 可添加到此帐户的其他流式处理终结点也是 2.0 版。Additional streaming endpoints that you add to this account are also version 2.0. 此更改不会影响现有帐户。This change doesn't affect existing accounts. 现有流式处理终结点为 1.0,可升级到 2.0 版。Existing streaming endpoints are version 1.0 and can be upgraded to version 2.0. 此次更改带来了行为、计费和功能更改。There are behavior, billing, and feature changes with this change. 有关详细信息,请参阅流式处理终结点概述For more information, see Streaming endpoints overview.

从 2.15 版本开始,向流式处理终结点实体的以下属性添加了媒体服务:Starting with the 2.15 version, Media Services added the following properties to the streaming endpoint entity:

  • CdnProviderCdnProvider
  • CdnProfileCdnProfile
  • FreeTrialEndTimeFreeTrialEndTime
  • StreamingEndpointVersionStreamingEndpointVersion

有关这些属性的信息,请参阅 StreamingEndpointFor more information on these properties, see StreamingEndpoint.

2016 年 12 月版本December 2016 release

现可使用媒体服务访问其服务的遥测/指标数据。You now can use Media Services to access telemetry/metrics data for its services. 可使用当前版本的媒体服务收集实时通道、流式处理终结点和存档实体的遥测数据。You can use the current version of Media Services to collect telemetry data for live channel, streaming endpoint, and archive entities. 有关详细信息,请参阅媒体服务遥测For more information, see Media Services telemetry.

2016 年 7 月版本July 2016 release

编码任务所生成清单文件 (*.ISM) 的更新Updates to the manifest file (*.ISM) generated by encoding tasks

将某个编码任务提交到 Media Encoder Standard 或 Media Encoder Premium 后,该编码任务会在输出资产中生成流式处理清单文件 (*.ism)。When an encoding task is submitted to Media Encoder Standard or Media Encoder Premium, the encoding task generates a streaming manifest file (*.ism) in the output asset. 最新的服务版本已更新此流式处理清单文件的语法。With the latest service release, the syntax of this streaming manifest file was updated.

备注

流式处理清单 (.ism) 文件的语法保留供内部使用。The syntax of the streaming manifest (.ism) file is reserved for internal use. 这在将来的版本中可能会有所改变。It's subject to change in future releases. 请勿修改或操作此文件的内容。Do not modify or manipulate the contents of this file.

当某个编码任务输出一个或多个 MP4 文件时,会在输出资产中生成新的客户端清单 (*.ISMC) 文件A new client manifest (*.ISMC) file is generated in the output asset when an encoding task outputs one or more MP4 files

从最新服务版本开始,在完成编码任务以生成一个或多个 MP4 文件以后,输出资产中也会包含流式处理客户端清单 (*.ismc) 文件。Starting with the latest service release, after the completion of an encoding task that generates one or more MP4 files, the output asset also contains a streaming client manifest (*.ismc) file. 该 .ismc 文件有助于改进动态流式处理的性能。The .ismc file helps improve the performance of dynamic streaming.

备注

客户端清单 (.ismc) 文件的语法保留供内部使用。The syntax of the client manifest (.ismc) file is reserved for internal use. 这在将来的版本中可能会有所改变。It's subject to change in future releases. 请勿修改或操作此文件的内容。Do not modify or manipulate the contents of this file.

有关详细信息,请参阅此博客For more information, see this blog.

已知问题Known issues

某些客户端可能会在平滑流式处理清单中碰到重复标记问题。Some clients can come across a repeat tag issue in the Smooth Streaming manifest. 有关详细信息,请参阅此部分For more information, see this section.

2016年4月版April 2016 release

媒体分析Media Analytics

媒体服务引入了媒体分析,以实现功能强大的视频智能。Media Services introduced Media Analytics for powerful video intelligence. 有关详细信息,请参阅媒体服务分析概述For more information, see Media Services Analytics overview.

Apple FairPlay(预览版)Apple FairPlay (preview)

现可使用 Azure 媒体服务,通过 Apple FairPlay 动态加密 HTTP Live Streaming (HLS) 内容。You now can use Media Services to dynamically encrypt your HTTP Live Streaming (HLS) content with Apple FairPlay. 还可使用媒体服务许可证传送服务,将 FairPlay 许可证传送到客户端。You also can use the Media Services license delivery service to deliver FairPlay licenses to clients. 有关详细信息,请参阅“使用 Azure 媒体服务流式传输受 Apple FairPlay 保护的 HLS 内容”。For more information, see "Use Azure Media Services to stream your HLS content protected with Apple FairPlay."

2016年2月版February 2016 release

适用于 .NET 的媒体服务 SDK 最新版本 (3.5.3) 包含 Google Widevine 相关的 bug 修复程序。The latest version of the Media Services SDK for .NET (3.5.3) contains a Google Widevine-related bug fix. 之前无法对 Widevine 加密的多个资产重复使用 AssetDeliveryPolicy。It was impossible to reuse AssetDeliveryPolicy for multiple assets encrypted with Widevine. 为了修复此 bug,SDK 中添加了以下属性:WidevineBaseLicenseAcquisitionUrl。As part of this bug fix, the following property was added to the SDK: WidevineBaseLicenseAcquisitionUrl.

Dictionary<AssetDeliveryPolicyConfigurationKey, string> assetDeliveryPolicyConfiguration =
    new Dictionary<AssetDeliveryPolicyConfigurationKey, string>
{
    {AssetDeliveryPolicyConfigurationKey.WidevineBaseLicenseAcquisitionUrl,"http://testurl"},

};

2016年1月版January 2016 release

编码预留单位已重命名,以减少与编码器名称的混淆。Encoding reserved units were renamed to reduce confusion with encoder names.

基本、标准和高级编码预留单位已分别重命名为 S1、S2 和 S3 预留单位。The Basic, Standard, and Premium encoding reserved units were renamed to S1, S2, and S3 reserved units, respectively. 使用基本编码预留单位的客户现可在 Azure 门户(和帐单)中看到 S1 标签。Customers who use Basic encoding reserved units today see S1 as the label in the Azure portal (and in the bill). 使用标准和高级版的客户分别会看到 S2 和 S3 标签。Customers who use Standard and Premium see the labels S2 and S3, respectively.

2015年12月版本December 2015 release

媒体编码器弃用公告Media Encoder deprecation announcement

将在 Media Encoder Standard 发布后大约 12 个月内开始弃用媒体编码器。Media Encoder will be deprecated starting in approximately 12 months from the release of Media Encoder Standard.

内置 Web 服务器Azure SDK for PHP

Azure SDK 团队已发布新版 Azure SDK for PHP 包,其中包含媒体服务的更新与新功能。The Azure SDK team published a new release of the Azure SDK for PHP package that contains updates and new features for Media Services. 具体而言,适用于 PHP 的媒体服务 SDK 现支持最新内容保护功能。In particular, the Media Services SDK for PHP now supports the latest content protection features. 使用 AES 和 DRM(PlayReady 和 Widevine)对这些功能进行动态加密(可以使用也可不使用标记限制)。These features are dynamic encryption with AES and DRM (PlayReady and Widevine) with and without token restrictions. 它还支持缩放编码单位It also supports scaling encoding units.

有关详细信息,请参见:For more information, see:

2015 年 11 月版本November 2015 release

媒体服务现已在云中提供 Widevine 许可证传送服务。Media Services now offers the Widevine license delivery service in the cloud. 有关详细信息,请参阅此博客For more information, see this blog. 另请参阅此教程GitHub 存储库Also, see this tutorial and the GitHub repository.

媒体服务提供的 Widevine 许可证传送服务为预览版。Widevine license delivery services provided by Media Services are in preview. 有关详细信息,请参阅此博客For more information, see this blog.

2015年10月版October 2015 release

媒体服务现已在以下数据中心推出:巴西南部、印度西部、印度南部和印度中部。Media Services is now live in the following data centers: Brazil South, India West, India South, and India Central. 现在可以使用 Azure 门户创建媒体服务帐户,以及执行媒体服务文档网页中所述的各项任务。You can now use the Azure portal to create Media Service accounts and perform various tasks described in the Media Services documentation webpage. 这些数据中心未启用实时编码。Live Encoding isn't enabled in these data centers. 此外,并非所有类型的编码预留单位都可用于这些数据中心。Further, not all types of encoding reserved units are available in these data centers.

  • 巴西南部:只可以使用标准和基本编码预留单位。Brazil South: Only Standard and Basic encoding reserved units are available.
  • 印度西部、印度南部和印度中部:只可以使用基本编码预留单位India West, India South, and India Central: Only Basic encoding reserved units are available.

2015年9月发布September 2015 release

媒体服务现在提供通过 Widevine 模块化 DRM 技术保护点播视频和实时流的功能。Media Services now offers the ability to protect both video on demand and live streams with Widevine modular DRM technology. 可以通过以下交付服务合作伙伴来交付 Widevine 许可证:You can use the following delivery services partners to help you deliver Widevine licenses:

有关详细信息,请参阅此博客For more information, see this blog.

可以通过媒体服务 .NET SDK(从版本 3.5.1 开始)或 REST API 来配置 AssetDeliveryConfiguration 以使用 Widevine。You can use the Media Services .NET SDK (starting with version 3.5.1) or the REST API to configure AssetDeliveryConfiguration to use Widevine.

  • 媒体服务增加了对 Apple ProRes 视频的支持。Media Services added support for Apple ProRes videos. 你现在可以上传使用 Apple ProRes 或其他编解码器的 QuickTime 源视频文件。You can now upload your QuickTime source videos files that use Apple ProRes or other codecs. 有关详细信息,请参阅此博客For more information, see this blog.

  • 现可使用 Media Encoder Standard 来执行子剪辑和实时存档提取操作。You can now use Media Encoder Standard to do subclipping and live archive extraction. 有关详细信息,请参阅此博客For more information, see this blog.

  • 在筛选方面做了以下更新:The following filtering updates were made:

    • 现可使用通过“仅音频”筛选器使用 Apple HLS 格式。You can now use the Apple HLS format with an audio-only filter. 通过此更新,可在 URL 中指定 (audio-only=false) 来删除仅音频曲目。You can use this update to remove an audio-only track by specifying (audio-only=false) in the URL.

    • 为资产定义筛选器时,现在可以将多个(最多 3 个)筛选器组合到一个 URL 中。When you define filters for your assets, you now can combine multiple (up to three) filters in a single URL.

      有关详细信息,请参阅此博客For more information, see this blog.

  • 媒体服务现在支持 HLS 第 4 版格式的 I-frame。Media Services now supports I-frames in HLS version 4. I-frame 支持优化快进和倒带操作。I-frame support optimizes fast-forward and rewind operations. 默认情况下,所有 HLS 第 4 版输出包括 I-frame 播放列表 (EXT-X-I-FRAME-STREAM-INF)。By default, all HLS version 4 outputs include the I-frame playlist (EXT-X-I-FRAME-STREAM-INF). 有关详细信息,请参阅此博客For more information, see this blog.

2015年8月版本August 2015 release

  • 现已推出用于 Java 0.8.0 版的媒体服务 SDK 和新示例。The Media Services SDK for the Java version 0.8.0 release and new samples are now available. 有关详细信息,请参见:For more information, see:

  • 已更新 Azure Media Player,现支持多音频流。The Azure Media Player was updated with multi-audio stream support. 有关详细信息,请参阅此博客文章For more information, see this blog post.

2015 年 7 月版本July 2015 release

  • 宣布了 Media Encoder Standard 公开上市。The general availability of Media Encoder Standard was announced. 有关详细信息,请参阅此博客文章For more information, see this blog post.

    Media Encoder Standard 使用本节所述的预设值。Media Encoder Standard uses presets, as described in this section. 使用 4k 编码预设时,请获取高级预留单位类型。When you use a preset for 4K encodes, get the Premium reserved unit type. 有关详细信息,请参阅缩放编码For more information, see Scale encoding.

  • 媒体服务和 Media Player 中采用了直播实时字幕。Live real-time captions were used with Media Services and the Media Player. 有关详细信息,请参阅此博客文章For more information, see this blog post.

媒体服务 .NET SDK 更新Media Services .NET SDK updates

媒体服务 .NET SDK 当前版本为 3.4.0.0。The Media Services .NET SDK is now version 3.4.0.0. 进行了以下更新:The following updates were made:

  • 实现了对实时存档的支持。Support was implemented for live archive. 不能下载包含实时存档的资产。You can't download an asset that contains a live archive.
  • 实现了对动态筛选器的支持。Support was implemented for dynamic filters.
  • 实现了这样的功能,让用户可在删除资产时保留存储容器。Functionality was implemented so that users can keep a storage container while they delete an asset.
  • 进行了与频道中的重试策略相关的 Bug 修复。Bug fixes were made related to retry policies in channels.
  • 启用了 Media Encoder Premium Workflow。Media Encoder Premium Workflow was enabled.

2015年6月发布June 2015 release

媒体服务 .NET SDK 更新Media Services .NET SDK updates

媒体服务 .NET SDK 当前版本为 3.3.0.0。The Media Services .NET SDK is now version 3.3.0.0. 进行了以下更新:The following updates were made:

  • 添加了对 OpenId Connect 发现规范的支持。Support was added for the OpenId Connect discovery spec.
  • 添加了对标识提供者端处理密钥变换的支持。Support was added for handling keys rollover on the identity provider side.

如果使用的标识提供程序会公开 OpenID Connect 发现文档(就像 Azure AD、Google、Salesforce 那样),可指示 Azure 媒体服务获取签名密钥,以根据 OpenID Connect 发现规范验证 JSON Web 令牌 (JWT)。If you use an identity provider that exposes an OpenID Connect discovery document (as Azure AD, Google, and Salesforce do), you can instruct Media Services to obtain signing keys for validation of JSON Web Tokens (JWTs) from the OpenID Connect discovery spec.

有关详细信息,请参阅使用 OpenID Connect 发现规范中的 Json Web 密钥在媒体服务中进行 JWT 身份验证For more information, see Use JSON web keys from the OpenID Connect discovery spec to work with JWT authentication in Media Services.

5月2015版May 2015 release

宣布推出了以下新功能:The following new features were announced:

2015年4月版April 2015 release

媒体服务一般更新General Media Services updates

  • 公布了 Media PlayerMedia Player was announced.
  • 从媒体服务 REST 2.10 开始,使用主要和辅助引入 URL 创建了配置为引入实时消息传输协议 (RTMP) 协议的通道。Starting with the Media Services REST 2.10, channels that are configured to ingest a Real-Time Messaging Protocol (RTMP) are created with primary and secondary ingest URLs. 有关详细信息,请参阅频道引入配置For more information, see Channel ingest configurations.
  • 更新了 Azure Media Indexer。Azure Media Indexer was updated.
  • 添加了西班牙语支持。Support for Spanish language was added.
  • 添加了 XML 格式的新配置。A new configuration for the XML format was added.

有关详细信息,请参阅此博客For more information, see this blog.

媒体服务 .NET SDK 更新Media Services .NET SDK updates

媒体服务 .NET SDK 当前版本为 3.2.0.0。The Media Services .NET SDK is now version 3.2.0.0. 进行了以下更新:The following updates were made:

  • 重大更改:将 TokenRestrictionTemplate.Issuer 和 TokenRestrictionTemplate.Audience 改为了字符串类型。Breaking change: TokenRestrictionTemplate.Issuer and TokenRestrictionTemplate.Audience were changed to be of a string type.
  • 进行了与创建自定义重试策略相关的更新。Updates were made related to creating custom retry policies.
  • 进行了与上传和下载文件相关的 Bug 修复。Bug fixes were made related to uploading and downloading files.
  • MediaServicesCredentials 类现在接受向主要和辅助访问控制终结点进行身份验证。The MediaServicesCredentials class now accepts primary and secondary access control endpoints to authenticate against.

2015年3月发布March 2015 release

媒体服务一般更新General Media Services updates

  • 媒体服务现提供内容分发网络集成。Media Services now provides Content Delivery Network integration. 为了支持集成,将 CdnEnabled 属性添加到了 StreamingEndpoint。To support the integration, the CdnEnabled property was added to StreamingEndpoint. CdnEnabled 可用于 2.9 及以上版本的 REST API。CdnEnabled can be used with REST APIs starting with version 2.9. 有关详细信息,请参阅 StreamingEndpointFor more information, see StreamingEndpoint. CdnEnabled 可用于 3.1.0.2 及以上版本的 .NET SDK。CdnEnabled can be used with the .NET SDK starting with version 3.1.0.2. 有关详细信息,请参阅 StreamingEndpointFor more information, see StreamingEndpoint.
  • 公布了 Media Encoder Premium Workflow。The Media Encoder Premium Workflow was announced. 有关详细信息,请参阅在 Azure 媒体服务中引入高级编码For more information, see Introducing Premium encoding in Azure Media Services.

2015年2月版February 2015 release

媒体服务一般更新General Media Services updates

媒体服务 REST API 当前版本为 2.9。The Media Services REST API is now version 2.9. 自此版本起,可以通过流式处理终结点启用 Azure 内容分发网络集成。Starting with this version, you can enable the Content Delivery Network integration with streaming endpoints. 有关详细信息,请参阅 StreamingEndpointFor more information, see StreamingEndpoint.

2015年1月版January 2015 release

媒体服务一般更新General Media Services updates

公布了采用动态加密的内容保护公开上市。The general availability of content protection with dynamic encryption was announced. 有关详细信息,请参阅媒体服务采用公开上市的 DRM 技术增强流式处理的安全性For more information, see Media Services enhances streaming security with general availability of DRM technology.

媒体服务 .NET SDK 更新Media Services .NET SDK updates

媒体服务 .NET SDK 当前版本为 3.1.0.1。The Media Services .NET SDK is now version 3.1.0.1.

此版本将默认的 Microsoft.WindowsAzure.MediaServices.Client.ContentKeyAuthorization.TokenRestrictionTemplate 构造函数标记为已过时。This release marked the default Microsoft.WindowsAzure.MediaServices.Client.ContentKeyAuthorization.TokenRestrictionTemplate constructor as obsolete. 新的构造函数将 TokenType 作为参数。The new constructor takes TokenType as an argument.

TokenRestrictionTemplate template = new TokenRestrictionTemplate(TokenType.SWT);

2014年12月版本December 2014 release

媒体服务一般更新General Media Services updates

  • 向 Media Indexer 添加了一些更新和新功能。Some updates and new features were added to the Media Indexer. 有关详细信息,请参阅Azure Media Indexer 版本1.1.6.7 发行说明For more information, see Azure Media Indexer version 1.1.6.7 release notes.
  • 添加了新的 REST API,可用于更新编码预留单位。A new REST API was added that you can use to update encoding reserved units. 有关详细信息,请参阅 REST 中的 EncodingReservedUnitTypeFor more information, see EncodingReservedUnitType with REST.
  • 添加了对密钥传送服务的 CORS 支持。CORS support was added for the key delivery service.
  • 改进了查询授权策略选项的性能。Performance improvements were made to querying authorization policy options.
  • 在中国数据中心,密钥传递 URL 现在是每个客户一份(同其他数据中心一样)。In the China data center, the key delivery URL is now per customer (just like in other data centers).
  • 增加了 HLS 自动目标持续时间。HLS auto target duration was added. 当执行实时流式传输时,HLS 始终是动态打包的。When doing live streaming, HLS is always packaged dynamically. 默认情况下,媒体服务将根据从关键帧间隔 (KeyFrameInterval) 自动计算 HLS 段打包率 (FragmentsPerSegment)。By default, Media Services automatically calculates the HLS segment packaging ratio (FragmentsPerSegment) based on the keyframe interval (KeyFrameInterval). 此方法也称为从实时编码器接收的帧组 (GOP)。This method is also referred to as a group of pictures (GOP) that is received from the live encoder. 有关详细信息,请参阅使用媒体服务实时传送视频流For more information, see Work with Media Services live streaming.

媒体服务 .NET SDK 更新Media Services .NET SDK updates

媒体服务 .NET SDK 当前版本为 3.1.0.0。The Media Services .NET SDK is now version 3.1.0.0. 进行了以下更新:The following updates were made:

2014年11月发布November 2014 release

  • 现在可以使用媒体服务通过 TLS 连接引入实时平滑流式处理(fMP4)内容。You now can use Media Services to ingest live Smooth Streaming (fMP4) content over a TLS connection. 若要通过 TLS 引入,请确保将摄取 URL 更新为 HTTPS。To ingest over TLS, make sure to update the ingest URL to HTTPS. 目前,媒体服务不支持 TLS 和自定义域。Currently, Media Services doesn't support TLS with custom domains. 有关实时传送视频流的详细信息,请参阅使用 Azure 媒体服务实时传送视频流For more information about live streaming, see Work with Azure Media Services Live Streaming.
  • 目前,无法通过 TLS 连接引入 RTMP 实时流。Currently, you can't ingest an RTMP live stream over a TLS connection.
  • 只有在2014年9月10日之后创建了你从中传送内容的流式处理终结点时,才可以通过 TLS 进行流式传输。You can stream over TLS only if the streaming endpoint from which you deliver your content was created after September 10, 2014. 如果流式处理 URL 是基于 2014 年 9 月 10 日之后创建的流式处理终结点,则 URL 会包含“streaming.mediaservices.windows.net”(新格式)。If your streaming URLs are based on the streaming endpoints created after September 10, 2014, the URL contains "streaming.mediaservices.windows.net" (the new format). 包含 "origin.mediaservices.windows.net" (旧格式)的流式处理 Url 不支持 TLS。Streaming URLs that contain "origin.mediaservices.windows.net" (the old format) don't support TLS. 如果你的 URL 采用旧格式,并且你想要流式传输 TLS,请创建新的流式处理终结点If your URL is in the old format and you want to stream over TLS, create a new streaming endpoint. 若要通过 TLS 流式传输内容,请使用基于新流式处理终结点的 Url。To stream your content over TLS, use URLs based on the new streaming endpoint.

媒体服务 .NET SDKMedia Services .NET SDK

适用于 .NET 的媒体服务 SDK 扩展当前版本为 2.0.0.3。The Media Services SDK for .NET extensions is now version 2.0.0.3.

适用于 .NET 的媒体服务 SDK 当前版本为 3.0.0.8。The Media Services SDK for .NET is now version 3.0.0.8. 进行了以下更新:The following updates were made:

  • 在重试策略类中实现了重构。Refactoring was implemented in retry policy classes.
  • 向 HTTP 请求标头添加了用户代理字符串。A user agent string was added to HTTP request headers.
  • 添加了 NuGet 还原生成步骤。A NuGet restore build step was added.
  • 修复了方案测试以使用存储库中的 x509 证书。Scenario tests were fixed to use x509 cert from repository.
  • 通道和流式处理结束更新时,添加了验证设置。Validation settings were added for when the channel and streaming end update.

新增了承载媒体服务示例的 GitHub 存储库New GitHub repository to host Media Services samples

Azure 媒体服务示例 GitHub 存储库中提供了示例。Samples are in the Media Services samples GitHub repository.

2014年9月发布September 2014 release

媒体服务 REST 元数据当前版本为 2.7。The Media Services REST metadata is now version 2.7. 有关最新 REST 更新的详细信息,请参阅媒体服务 REST API 参考For more information about the latest REST updates, see the Media Services REST API reference.

适用于 .NET 的媒体服务 SDK 当前版本为 3.0.0.7。The Media Services SDK for .NET is now version 3.0.0.7

中断性变更Breaking changes

  • 原点重命名为了 StreamingEndpointOrigin was renamed to StreamingEndpoint.
  • 更改了使用 Azure 门户编码和发布 MP4 文件时的默认行为。A change was made in the default behavior when you use the Azure portal to encode and then publish MP4 files.

公开上市版中的新增功能/方案New features/scenarios that are part of the general availability release

  • 引入了 Media Indexer 媒体处理器。The Media Indexer media processor was introduced. 有关详细信息,请参阅使用 Media Indexer 索引媒体文件For more information, see Index media files with the Media Indexer.

  • 可使用 StreamingEndpoint 实体添加自定义域(主机)名。You can use the StreamingEndpoint entity to add custom domain (host) names.

    若要使用自定义域名作为媒体服务流式处理终结点名称,请向流式处理终结点添加自定义主机名。To use a custom domain name as the Media Services streaming endpoint name, add custom host names to your streaming endpoint. 使用媒体服务 REST API 或 .NET SDK 添加自定义主机名。Use the Media Services REST APIs or the .NET SDK to add custom host names.

    请注意以下事项:The following considerations apply:

    • 必须具有该自定义域名的所有权。You must have the ownership of the custom domain name.

    • 域名的所有权必须通过媒体服务验证。The ownership of the domain name must be validated by Media Services. 若要验证域,请创建映射 MediaServicesAccountId 父域的 CName 来验证 DNS mediaservices-dns-zone。To validate the domain, create a CName that maps the MediaServicesAccountId parent domain to verify DNS mediaservices-dns-zone.

    • 必须创建另一个 CName,以将自定义主机名(例如 sports.contoso.com)映射到媒体服务 StreamingEndpont 的主机名(例如 amstest.streaming.mediaservices.windows.net)。You must create another CName that maps the custom host name (for example, sports.contoso.com) to your Media Services StreamingEndpoint host name (for example, amstest.streaming.mediaservices.windows.net).

      有关详细信息,请参阅 StreamingEndpoint 一文中的 CustomHostNames 属性。For more information, see the CustomHostNames property in the StreamingEndpoint article.

公共预览版的新增功能/方案New features/scenarios that are part of the public preview release

2014年8月版本August 2014 release

对资产进行编码时,完成编码作业后会生成输出资产。When you encode an asset, an output asset is produced when the encoding job is finished. 在此版本之前,媒体服务编码器会生成有关输出资产的元数据。Until this release, the Media Services Encoder produced metadata about output assets. 自此版本起,编码器还将生成有关输入资产的元数据。Starting with this release, the encoder also produces metadata about input assets. 有关详细信息,请参阅输入元数据输出元数据For more information, see Input metadata and Output metadata.

2014 年 7 月版本July 2014 release

修复了 Azure 媒体服务包装程序和加密程序中的以下 Bug:The following bug fixes were made for the Azure Media Services Packager and Encryptor:

  • 将实时存档资产传输到 HLS 时,只播放音频:此问题已修复,现可同时播放音频和视频。When a live archive asset is transmitted to HLS, only audio plays back: This issue was fixed, and now both audio and video can play.
  • 打包资产以进行 HLS 和 AES 128 位信封加密时,Android 设备上不播放已打包的流:此 Bug 已修复,支持 HLS 的 Android 设备现将播放已打包的流。When an asset is packaged to HLS and AES 128-bit envelope encryption, the packaged streams don't play back on Android devices: This bug was fixed, and the packaged stream plays back on Android devices that support HLS.

2014 年 5 月版本May 2014 release

媒体服务一般更新General Media Services updates

现可使用动态打包对 HLS 第 3 版文件进行流式处理。You can now use dynamic packaging to stream HLS version 3. 要对 HLS 第 3 版文件进行流式处理,请将以下格式添加到原点定位符路径:*.ism/manifest(format=m3u8-aapl-v3)。To stream HLS version 3, add the following format to the origin locator path: * .ism/manifest(format=m3u8-aapl-v3). 有关详细信息,请访问此论坛For more information, see this forum.

动态打包现在还支持基于使用 PlayReady 静态加密的平滑流式处理内容传递使用 PlayReady 加密的 HLS(第 3 版和第 4 版)。Dynamic packaging now also supports delivering HLS (version 3 and version 4) encrypted with PlayReady based on Smooth Streaming statically encrypted with PlayReady. 有关如何使用 PlayReady 加密平滑流式处理内容的信息,请参阅使用 PlayReady 保护平滑流For information on how to encrypt Smooth Streaming with PlayReady, see Protect Smooth Streaming with PlayReady.

媒体服务 .NET SDK 更新Media Services .NET SDK updates

媒体服务 .NET SDK 当前版本为 3.1.0.5。The Media Services .NET SDK is now version 3.0.0.5. 进行了以下更新:The following updates were made:

  • 上传和下载媒体资产时,速度和复原能力得到提升。Speed and resilience are better when you upload and download media assets.

  • 进行了重试逻辑和暂时性异常处理方面的改进:Improvements were made in retry logic and transient exception handling:

    • 改进了暂时性错误检测和重试逻辑,以处理由查询、保存更改、上传或下载文件引起的异常。Transient error detection and retry logic were improved for exceptions that are caused when you query, save changes, and upload or download files.
    • 收到 Web 异常时(例如在访问控制服务令牌请求过程中),灾难性错误现将更快失败。When you get web exceptions (for example, during an Access Control Service token request), fatal errors fail faster now.

有关详细信息,请参阅适用于[.net 的媒体服务 SDK 中的重试逻辑]。For more information, see Retry logic in the Media Services SDK for .NET.

2014 年 1/2 月版本January/February 2014 releases

媒体服务 .NET SDK 3.0.0.1、3.0.0.2 和 3.0.0.3Media Services .NET SDK 3.0.0.1, 3.0.0.2 and 3.0.0.3

3.0.0.1 和 3.0.0.2 中的更改包括:The changes in 3.0.0.1 and 3.0.0.2 include:

  • 修复了与具有 OrderBy 语句的 LINQ 查询的使用相关的问题。Issues related to the usage of LINQ queries with OrderBy statements were fixed.
  • GitHub 中的测试解决方案拆分为了基于单位的测试和基于方案的测试。Test solutions in GitHub were split into unit-based tests and scenario-based tests.

有关这些更改的详细信息,请参阅媒体服务 .NET SDK 3.0.0.1 和 3.0.0.2 版本For more information about the changes, see the Media Services .NET SDK 3.0.0.1 and 3.0.0.2 releases.

版本 3.0.0.3 中进行了以下更改:The following changes were made in version 3.0.0.3:

  • Azure 存储依赖项已升级为使用版本 3.0.3.0。Azure storage dependencies were upgraded to use version 3.0.3.0.
  • 修复了 3.0.. 的后向兼容性问题A backward-compatibility issue was fixed for 3.0.. 版本的向后兼容性问题。releases.

2013 年 12 月版本December 2013 release

媒体服务 .NET SDK 3.0.0.0Media Services .NET SDK 3.0.0.0

备注

3.0.x.x 版本不后向兼容 2.4.x.x 版本。The 3.0.x.x releases are not backward compatible with 2.4.x.x releases.

媒体服务 SDK 当前的最新版本为 3.0.0.0。The latest version of the Media Services SDK is now 3.0.0.0. 你可以从 NuGet 下载最新程序包或从GitHub获取该版本。You can download the latest package from NuGet or get the bits from GitHub.

自媒体服务 SDK 3.0.0.0 版本起,可以重复使用 Azure AD 访问控制服务令牌。Starting with the Media Services SDK version 3.0.0.0, you can reuse the Azure AD Access Control Service tokens. 有关详细信息,请参阅使用适用于 .NET 的媒体服务 SDK 连接到媒体服务中的“重复使用访问控制服务令牌”一节。For more information, see the section "Reuse Access Control Service tokens" in Connect to Media Services with the Media Services SDK for .NET.

媒体服务 .NET SDK 扩展 2.0.0.0Media Services .NET SDK extensions 2.0.0.0

媒体服务.NET SDK 扩展是一组扩展方法和帮助器函数,可简化代码,并令使用媒体服务进行开发变得更加容易。The Media Services .NET SDK extensions are a set of extension methods and helper functions that simplify your code and make it easier to develop with Media Services. 媒体服务 .NET SDK 扩展中提供了最新信息。You can get the latest bits from Media Services .NET SDK extensions.

2013年11月发布November 2013 release

媒体服务 .NET SDK 更改Media Services .NET SDK changes

自此版本起,适用于 .NET 的媒体服务 SDK 将处理在调用媒体服务 REST API 层时可能发生的暂时性故障错误。Starting with this version, the Media Services SDK for .NET handles transient fault errors that might occur when calls are made to the Media Services REST API layer.

2013年8月版本August 2013 release

Azure SDK 工具中包含的媒体服务 PowerShell cmdletMedia Services PowerShell cmdlets included in Azure SDK tools

Azure SDK 工具中现在包含以下媒体服务 PowerShell cmdlet。The following Media Services PowerShell cmdlets are now included in Azure SDK tools:

  • Get-AzureMediaServicesGet-AzureMediaServices

    例如:Get-AzureMediaServicesAccountFor example: Get-AzureMediaServicesAccount

  • New-AzureMediaServicesAccountNew-AzureMediaServicesAccount

    例如:New-AzureMediaServicesAccount -Name "MediaAccountName" -Location "Region" -StorageAccountName "StorageAccountName"For example: New-AzureMediaServicesAccount -Name "MediaAccountName" -Location "Region" -StorageAccountName "StorageAccountName"

  • New-AzureMediaServicesKeyNew-AzureMediaServicesKey

    例如:New-AzureMediaServicesKey -Name "MediaAccountName" -KeyType Secondary -ForceFor example: New-AzureMediaServicesKey -Name "MediaAccountName" -KeyType Secondary -Force

  • Remove-AzureMediaServicesAccountRemove-AzureMediaServicesAccount

    例如:Remove-AzureMediaServicesAccount -Name "MediaAccountName" -ForceFor example: Remove-AzureMediaServicesAccount -Name "MediaAccountName" -Force

2013年6月发布June 2013 release

媒体服务更改Media Services changes

本节所述的以下变化是 2013 年 6 月媒体服务版本中包含的更新。The following changes mentioned in this section are updates included in the June 2013 Media Services releases:

  • 将多个存储帐户链接到一个媒体服务帐户的功能。Ability to link multiple storage accounts to a Media Service account.
    • StorageAccountStorageAccount
    • Asset.StorageAccountName 和 Asset.StorageAccountAsset.StorageAccountName and Asset.StorageAccount
  • 更新 Job.Priority 的功能。Ability to update Job.Priority.
  • 与通知相关的实体和属性:Notification-related entities and properties:
    • JobNotificationSubscriptionJobNotificationSubscription
    • NotificationEndPointNotificationEndPoint
    • 作业Job
  • Asset.UriAsset.Uri
  • Locator.NameLocator.Name

媒体服务 .NET SDK 更改Media Services .NET SDK changes

2013 年 6 月媒体服务 SDK 版本中包含以下更改。The following changes are included in the June 2013 Media Services SDK releases. GitHub 上提供有最新的媒体服务 SDK。The latest Media Services SDK is available on GitHub.

  • 自 2.3.0.0 版起,媒体服务 SDK 支持将多个存储帐户链接到一个媒体服务帐户。Starting with version 2.3.0.0, the Media Services SDK supports linking multiple storage accounts to a Media Services account. 以下 API 支持此功能:The following APIs support this feature:

  • 与通知相关的 API。Notification-related APIs. 自 2.2.0.0 版起,可侦听 Azure 队列存储通知。Starting with version 2.2.0.0, you can listen to Azure Queue storage notifications. 有关详细信息,请参阅处理媒体服务作业通知For more information, see Handle Media Services job notifications.

    • Microsoft.WindowsAzure.MediaServices.Client.IJob.JobNotificationSubscriptions 属性Microsoft.WindowsAzure.MediaServices.Client.IJob.JobNotificationSubscriptions property
    • Microsoft.WindowsAzure.MediaServices.Client.INotificationEndPoint 类型Microsoft.WindowsAzure.MediaServices.Client.INotificationEndPoint type
    • Microsoft.WindowsAzure.MediaServices.Client.IJobNotificationSubscription 类型Microsoft.WindowsAzure.MediaServices.Client.IJobNotificationSubscription type
    • Microsoft.WindowsAzure.MediaServices.Client.NotificationEndPointCollection 类型Microsoft.WindowsAzure.MediaServices.Client.NotificationEndPointCollection type
    • Microsoft.WindowsAzure.MediaServices.Client.IJobNotificationSubscription 类型Microsoft.WindowsAzure.MediaServices.Client.NotificationEndPointType type
  • 存储客户端 SDK 2.0 中的依赖项 (Microsoft.WindowsAzure.StorageClient.dll)Dependency on the Storage client SDK 2.0 (Microsoft.WindowsAzure.StorageClient.dll)

  • OData 5.5 中的依赖项 (Microsoft.Data.OData.dll)Dependency on OData 5.5 (Microsoft.Data.OData.dll)

2012年12月版本December 2012 release

媒体服务 .NET SDK 更改Media Services .NET SDK changes

  • IntelliSense:为许多类型添加了缺少的 IntelliSense 文档。IntelliSense: Missing IntelliSense documentation was added for many types.
  • Microsoft.Practices.TransientFaultHandling.Core:修复了 SDK 仍依赖于此程序集的旧版本的问题。Microsoft.Practices.TransientFaultHandling.Core: An issue was fixed where the SDK still had a dependency to an old version of this assembly. SDK 现在引用此程序集的 5.1.1209.1 版本。The SDK now references version 5.1.1209.1 of this assembly.

修复了 2012 年 11 月版 SDK 中发现的问题:Fixes for issues found in the November 2012 SDK:

  • IAsset.Locators.Count:现在会在删除所有定位符后在新的 IAsset 接口上正确报告此计数。IAsset.Locators.Count: This count is now correctly reported on new IAsset interfaces after all locators are deleted.
  • IAssetFile.ContentFileSize:现在会在通过 IAssetFile.Upload(filepath) 上传后正确设置此值。IAssetFile.ContentFileSize: This value is now properly set after an upload by IAssetFile.Upload(filepath).
  • IAssetFile.ContentFileSize:现可在创建资产文件时设置此属性。IAssetFile.ContentFileSize: This property can now be set when you create an asset file. 此属性以前是只读的。It was previously read only.
  • IAssetFile.Upload(filepath):修复了将多个文件上传到资产时,此同步上传方法引发以下错误的问题。IAssetFile.Upload(filepath): An issue was fixed where this synchronous upload method was throwing the following error when multiple files were uploaded to the asset. 错误为“服务器未能对请求进行身份验证。The error was "Server failed to authenticate the request. 请确保授权标头的值构成正确,且包括签名。”Make sure the value of Authorization header is formed correctly including the signature."
  • IAssetFile.UploadAsync:修复了同时上传文件限于五个的问题。IAssetFile.UploadAsync: An issue was fixed that limited the simultaneous upload of files to five files.
  • IAssetFile.UploadProgressChanged:现在由 SDK 提供此事件。IAssetFile.UploadProgressChanged: This event is now provided by the SDK.
  • IAssetFile.DownloadAsync(string, BlobTransferClient, ILocator, CancellationToken):现在提供了此方法重载。IAssetFile.DownloadAsync(string, BlobTransferClient, ILocator, CancellationToken): This method overload is now provided.
  • IAssetFile.DownloadAsync:修复了同时下载文件限于五个的问题。IAssetFile.DownloadAsync: An issue was fixed that limited the simultaneous download of files to five files.
  • IAssetFile.Delete():修复了如果没有为 IAssetFile 上传文件,调用 delete 时可能会引发异常的问题。IAssetFile.Delete(): An issue was fixed where calling delete might throw an exception if no file was uploaded for the IAssetFile.
  • Jobs:修复了使用作业模板将“MP4 平滑流任务”与“PlayReady 保护任务”链接在一起时未创建任何任务的问题。Jobs: An issue was fixed where chaining an "MP4 to Smooth Streams task" with a "PlayReady Protection Task" by using a job template didn't create any tasks at all.
  • EncryptionUtils.GetCertificateFromStore():由于未找到基于证书配置问题的证书,此方法不再引发 null 异常。EncryptionUtils.GetCertificateFromStore(): This method no longer throws a null reference exception due to a failure in finding the certificate based on certificate configuration issues.

2012年11月发布November 2012 release

本部分所述的变化是 2012 年 11 月(2.0.0.0 版)SDK 中包含的更新。The changes mentioned in this section were updates included in the November 2012 (version 2.0.0.0) SDK. 这些更改可能要求对 2012 年 6 月预览版 SDK 的代码进行修改或重写。These changes might require any code written for the June 2012 preview SDK release to be modified or rewritten.

  • 资产Assets

    • IAsset (assetName)是唯一的资产创建函数。IAsset.Create(assetName) is the only asset creation function. IAsset.Create 不再在方法调用中上传文件。IAsset.Create no longer uploads files as part of the method call. 使用 IAssetFile 进行上传。Use IAssetFile for uploading.
    • IAsset.Publish 方法和 AssetState.Publish 枚举值已从媒体服务 SDK 中删除。The IAsset.Publish method and the AssetState.Publish enumeration value were removed from the Services SDK. 必须重写依赖于此值的任何代码。Any code that relies on this value must be rewritten.
  • FileInfoFileInfo

    • 此类已由 IAssetFile 删除并取代。This class was removed and replaced by IAssetFile.
  • IAssetFileIAssetFiles

    • IAssetFile 取代了 FileInfo 并具有不同的行为。IAssetFile replaces FileInfo and has a different behavior. 若要使用它,请先实例化 IAssetFile 对象,然后使用媒体服务 SDK 或存储 SDK 上传文件。To use it, instantiate the IAssetFiles object, followed by a file upload either by using the Media Services SDK or the Storage SDK. 可以使用以下 IAssetFile.Upload 重载:The following IAssetFile.Upload overloads can be used:

      • IAssetFile.Upload(filePath):此同步方法将阻止线程,建议仅在上传单个文件时使用。IAssetFile.Upload(filePath): This synchronous method blocks the thread, and we recommend it only when you upload a single file.

      • IAssetFile.UploadAsync(filePath, blobTransferClient, locator, cancellationToken):此异步方法是优选上传机制。IAssetFile.UploadAsync(filePath, blobTransferClient, locator, cancellationToken): This asynchronous method is the preferred upload mechanism.

        已知 bug:如果使用取消令牌,将取消上传。Known bug: If you use the cancellation token, the upload is canceled. 任务可以有多个取消状态。The tasks can have many cancellation states. 必须正确捕获并处理异常。You must properly catch and handle exceptions.

  • 定位符Locators

    • 删除了原点特定的版本。The origin-specific versions were removed. SAS 特定的 context.Locators.CreateSasLocator(asset, accessPolicy) 将标记为已弃用或在公开上市时删除。The SAS-specific context.Locators.CreateSasLocator (asset, accessPolicy) will be marked deprecated or removed by general availability. 请参阅“新增功能”下的“定位符”部分以了解更新行为。See the "Locators" section under "New functionality" for updated behavior.

2012 年 6 月预览版June 2012 preview release

以下是 11 月版 SDK 中的新增功能:The following functionality was new in the November release of the SDK:

  • 删除实体Deleting entities

    • IAsset、IAssetFile、ILocator、IAccessPolicy、IContentKey 对象现在已从对象级别(即 IObject.Delete())删除,而不要求在集合(即 cloudMediaContext.ObjCollection.Delete(objInstance))中删除。IAsset, IAssetFile, ILocator, IAccessPolicy, and IContentKey objects are now deleted at the object level, that is, IObject.Delete(), instead of requiring a delete in the Collection, that is, cloudMediaContext.ObjCollection.Delete(objInstance).
  • 定位符Locators

    • 现在只能使用 CreateLocator 方法创建定位符。Locators now must be created by using the CreateLocator method. 它们只能使用 LocatorType.SAS 或 LocatorType.OnDemandOrigin 枚举值作为希望创建的特定类型定位符的参数。They must use the LocatorType.SAS or LocatorType.OnDemandOrigin enum values as an argument for the specific type of locator you want to create.
    • 定位符增加了新的属性,以便更轻松地为内容获取可用的 URL。New properties were added to locators to make it easier to obtain usable URIs for your content. 这种重新设计的定位符旨在为将来的第三方扩展提供更大的灵活性,并提高媒体客户端应用程序的易用性。This redesign of locators provides more flexibility for future third-party extensibility and increases the ease of use for media client applications.
  • 异步方法支持Asynchronous method support

    • 对所有方法增加了异步支持。Asynchronous support was added to all methods.

附加说明Additional notes

  • Widevine 是 Google Inc. 提供的一项服务,并受 Google Inc. 服务条款和隐私策略的约束。Widevine is a service provided by Google Inc. and subject to the terms of service and Privacy Policy of Google, Inc.

提供反馈Provide feedback

使用 用户之声 论坛提供反馈意见,并提出有关如何改进 Azure 媒体服务的建议。Use the User Voice forum to provide feedback and make suggestions on how to improve Azure Media Services. 还可以直接转到以下类别之一:You also can go directly to one of the following categories: