Assets can also have several locators attached with different settings, such as a time based filter to trim the start and end off a live event to remove unwanted content. The URL does not change unless you delete the locator and create another one. This asset can now be used for on-demand playback using the same URL that you tested above in the Azure Media Player. Your live event will be archived into the Media Services asset that you created during the steps above to create the live output. Once you are done with your event, you can stop the live output, followed by the live event. Stop your stream and use other features of Media Services and Video Indexer Your live event will begin streaming in the player. With your browser, open the Azure Media Player demo page in a new tab.Copy the HLS or DASH manifest links into any player application that supports the HLS or DASH streaming formats, such as Azure Media Player, Shaka Player, HLS.js, Video.js, Dash.js, ExoPlayer or other commercial player applications.For this example, just leave all of the default settings as they are, then select Create.At this point you can choose to use a streaming policy to encrypt the asset with DRM or AES-128, as well as choose a manifest filter and expiration date for the locator. Select the Add streaming locator tab to create a new streaming locator and publish the live output with a time-shift window set to your archive length. Set the output name, archive length, asset name, and storage account location.From the live event screen, select Create output.To archive your live event to an AMS asset, create a live output on the live event page in the Azure portal. Create a live output and streaming locator You should see the Teams meeting streaming in the player. Go back to the live event page in your browser.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |