Configuration changes can cause the event to become unstable. Changing your encoder configuration after it has started pushing has negative effects on the event.When using software-based encoders, close out any unnecessary programs.Although not mandatory, this simple rule helps to mitigate the impact of network congestion. When you're determining bandwidth requirements, double the streaming bitrates.Whenever possible, use a hardwired internet connection.Playback of the video-only stream is not supported. To play back content, both an audio and video stream must be present. Configuring on-premises live encoder settingsįor information about what settings are valid for your live event type, see Live Event types comparison. Encoders are not tested or validated by Microsoft on a continual basis and support or bugs can be introduced by the encoder vendors or open source projects that break compatibility at any time. The above list of encoders is just a recommendation list. When streaming via RTMPS, check firewall and/or proxy settings to confirm that outbound TCP ports 29 are open. When streaming via RTMP, check firewall and/or proxy settings to confirm that outbound TCP ports 19 are open. The supported URL schemes are rtmp:// or rtmps://. Media Services recommends using one of following live encoders that have RTMP as output. Encoder requirementsĮncoders must support TLS 1.2 when using HTTPS or RTMPS protocols. For instructions on how to verify your on-premises live encoder, see verify your on-premises encoderįor detailed information about live encoding with Media Services, see Live streaming with Media Services v3. Microsoft Azure Media Services does not do full or rigorous testing of each encoder, and does not continually re-verify on updates. The verification is done through vendor self-verification or customer verification. This article discusses verified on-premises live streaming encoders. The Live Event then performs live encoding of the incoming single-bitrate stream to a multi-bitrate (adaptive) video stream. The basic pass-through is the most economical, but is limited in capabilities.Īn on-premises live encoder sends a single-bitrate stream to the Live Event that is enabled to perform live encoding with Media Services in one of the following formats: RTMP or Smooth Streaming (fragmented MP4). The service supports a basic and standard pass-through mode depending on your ingest requirements. Using a pass-through method is the most economical way to do live streaming. If you are using multi-bitrates streams for the pass-through live event, the video GOP size and the video fragments on different bitrates must be synchronized to avoid unexpected behavior on the playback side. We recommend for the live encoder to send multi-bitrate streams instead of a single-bitrate stream to a pass-through live event to allow for adaptive bitrate streaming to the client. The ingested streams pass through Live Events without any further processing. The Live Event receives live input streams in one of two ways.Īn on-premises live encoder sends a multi-bitrate RTMP or Smooth Streaming (fragmented MP4) stream to the Live Event that is not enabled to perform live encoding with Media Services. In Azure Media Services, a Live Event (previously called a channel in v2) represents a pipeline for processing live-streaming content. For more information, see the AMS Retirement Guide. Azure Media Services will be retired June 30th, 2024.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |