Skip to content

Commit

Permalink
Merge pull request MicrosoftDocs#82422 from Juliako/patch-104
Browse files Browse the repository at this point in the history
Update media-services-dotnet-creating-live-encoder-enabled-channel.md
  • Loading branch information
PRMerger16 committed Jul 17, 2019
2 parents 5749f15 + 8782d91 commit 85873af
Showing 1 changed file with 2 additions and 2 deletions.
Original file line number Diff line number Diff line change
Expand Up @@ -38,7 +38,7 @@ For more conceptual information related to Channels that are enabled for live en
The following steps describe tasks involved in creating common live streaming applications.

> [!NOTE]
> Currently, the max recommended duration of a live event is 8 hours. Please contact amslived@microsoft.com if you need to run a Channel for longer periods of time.
> Currently, the max recommended duration of a live event is 8 hours. Please contact amshelp@microsoft.com if you need to run a Channel for longer periods of time.
1. Connect a video camera to a computer. Launch and configure an on-premises live encoder that can output a single bitrate stream in one of the following protocols: RTMP or Smooth Streaming. For more information, see [Azure Media Services RTMP Support and Live Encoders](https://go.microsoft.com/fwlink/?LinkId=532824).

Expand Down Expand Up @@ -93,7 +93,7 @@ The following are required to complete the tutorial.
* A webcam and an encoder that can send a single bitrate live stream.

## Considerations
* Currently, the max recommended duration of a live event is 8 hours. Please contact amslived@Microsoft.com if you need to run a Channel for longer periods of time.
* Currently, the max recommended duration of a live event is 8 hours. Please contact amshelp@microsoft.com if you need to run a Channel for longer periods of time.
* There is a limit of 1,000,000 policies for different AMS policies (for example, for Locator policy or ContentKeyAuthorizationPolicy). You should use the same policy ID if you are always using the same days / access permissions, for example, policies for locators that are intended to remain in place for a long time (non-upload policies). For more information, see [this](media-services-dotnet-manage-entities.md#limit-access-policies) article.

## Download sample
Expand Down

0 comments on commit 85873af

Please sign in to comment.