live-streaming-api | minimal API wrapper running on Azure Functions | Azure library
kandi X-RAY | live-streaming-api Summary
kandi X-RAY | live-streaming-api Summary
The Live Streaming API is a subset of a three-part application designed to control the state of one or more live events on Azure Media Services. These parts are:. In production, an event broadcaster would use the Live Streaming Controller as a front-end application to make a POST call to the /broadcaster endpoint, a DELETE call to the /broadcaster, and a GET call to the /broadcaster endpoint on the Live Streaming API to respectively start the streaming services at the beginning of an event, stop the services at the end, and read the status of these resources at any point before, during, or after. All of these calls are authenticated, since they can reveal sensitive information about the state of your resources, or result in a state change, and thus a billing change, on the broadcaster's Azure account. A viewer would then go to a website which has the Stream Switch installed to view the event. That application calls the /locators endpoint to fetch the streaming URLs from Azure to play inside of an HTML5 video player on the web. Since this endpoint intended for public consumption, it is the only endpoint in the application which is not authenticated. This portion of the application trio focuses on what is necessary to directly manipulate the state of these services on Azure. The collection you are viewing is to document all of the available calls one can make to this service, once it is deployed online. It is intended to be published on Azure Functions, although, it could be changed slightly to work on other serverless platforms, such as AWS Lambda. Please note that this application is designed to create and destroy resources on Azure in a completely self-contained manner. It does not require an administrator to change or manage these resources in any way beyond what is required for the installation. Manually changing these resources in Azure after the application is running may cause interference, resulting in an application malfunction. If you want to manually manage your own Media Services resources, it is recommended that you create a separate Media Services instance and leave the one used by this application to run on its own. The impetus of this application was to create an easy way to spin up Media Services resources on Azure before a broadcast and spin them down again after the show ends. This helps minimize unnecessary billing on our Azure account and puts the power of service management into the hands of the broadcaster. To reduce the costs associated with streaming on Azure, note that ALL resources created for a live streaming session will be DESTROYED when the application stops them. That includes the video buffer stored in the archive window. If you want to retain a copy of your live streaming session, it is recommended that the broadcaster records it locally before shutting down the stream and stopping the media resources. It is also important to note that this application does not support any kind of DRM streaming. All streams must be clear play, non-DRM protected streams. Additional CDNs and media reserved units have not been explicitly tested to work this application, but they should work properly in conjunction with this application.
Support
Quality
Security
License
Reuse
Top functions reviewed by kandi - BETA
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of live-streaming-api
live-streaming-api Key Features
live-streaming-api Examples and Code Snippets
Community Discussions
Trending Discussions on Azure
QUESTION
I am deploying an Azure Function called "Bridge" to Azure, targeting .NET 6. The project is referencing a class library called "DBLibrary" that I wrote, and that library is targeting .NET Standard 2.1. The Azure Function can be run locally on my PC without runtime errors.
When I publish the Azure Function to Azure, I see in Azure Portal a "Functions runtime error" which says:
Could not load file or assembly 'System.ComponentModel, Version=6.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'. The system cannot find the file specified.
I do not target System.ComponentModel directly, and I don't see a nuget package version 6.0.0 for "System.ComponentModel" available from any nuget feed. Why is the Azure function looking for this version 6.0.0 of System.ComponentModel? If that version does exist, why can't the Azure Function find it?
Here are the relevant parts of the csproj for the "Bridge" Azure Function:
...ANSWER
Answered 2022-Feb-25 at 10:33The .net standard you are using 2.1 but ,Microsoft.Azure.Functions.Extensions can be support upto .NET Standard 2.0
You should add the below package to your function app and deploy to Azure again.
QUESTION
I'm trying to understand how the price estimation works for Azure Data Factory from the official guide, section "Estimating Price - Use Azure Data Factory to migrate data from Amazon S3 to Azure Storage
I managed to understand everything except the 292 hours that are required to complete the migration.
Could you please explain to me how did they get that number?
...ANSWER
Answered 2022-Feb-15 at 03:46Firstly, feel free to submit a feedback here with the MS docs team to clarify with an official response on same.
Meanwhile, I see, as they mention "In total, it takes 292 hours to complete the migration" it would include listing from source, reading from source, writing to sink, other activities, other than the data movement itself.
If we consider approximately, for data volume of 2 PB and aggregate throughput of 2 GBps would give
2PB = 2,097,152 GB BINARY and Aggregate throughput = 2BGps --> 2,097,152/2 = 1,048,576 secs --> 1,048,576 secs / 3600 = 291.271 hours
Again, these are hypothetical. Further you can refer Plan to manage costs for Azure Data Factory and Understanding Data Factory pricing through examples.
QUESTION
What specific syntax or configuration changes must be made in order to resolve the error below in which terraform is failing to create an instance of azuread_application?
THE CODE:
The terraform code that is triggering the error when terraform apply is run is as follows:
ANSWER
Answered 2021-Oct-07 at 18:35This was a bug, reported as GitHub issue:
The resolution to the problem in the OP is to upgrade the version from 2.5.0 to 2.6.0 in the required_providers block from the code in the OP above as follows:
QUESTION
I want to generate User Delegation SAS Token to read the Azure BLOB I know we have to follow below step to get it.
- Get the oAuth Token from Azure Ad
- Generate user delegation key using oAuth Token
- Generate SAS Token using user delegation key
I am able to find the Rest service for step 1 & 2, I don't find any Rest service for step 3.
Is any Rest service is available to get the SAS Token using user delegation key
Thanks in Advance.
I am able to generate the delegation key and now I want to get SAS Token by using this user delegation key.
Note :- I have to use only Rest service for it
...ANSWER
Answered 2022-Mar-22 at 13:45AFAIK, there is no REST API to create a User Delegation SAS Token/URL.
Once you get the User Delegation Key which should contain the parameters needed to create User Delegation SAS, you will need to follow the instructions specified here: https://docs.microsoft.com/en-us/rest/api/storageservices/create-user-delegation-sas#construct-a-user-delegation-sas.
UPDATE:
For signing purpose, you would need to use the Value returned when you acquired the User Delegation Key.
This is what the response should be for getting the User Delegation Key:
QUESTION
I want to add to the user all possible group memberships in the Azure Active Directory, but there are so many groups so I dont want to do it manually, is there any script or button to do this quickly?
...ANSWER
Answered 2022-Mar-21 at 15:52try this in powershell install azure AD module
QUESTION
I'm new to Azure and trying to set up my nextjs client app and my ASP.NET Core backend app. Everything seems to play well now, except for file uploads. It's working on localhost, but in production the backend returns a 404 web page (attached image) before reaching the actual API endpoint. I've also successfully tested to make a multipart/form-data POST request in Postman from my computer.
The way I implemented this is that I'm proxying the upload from the browser through an api route (client's server side) to the backend. I have to go via the client server side to append a Bearer token from a httpOnly cookie.
I've enabled CORS in Startup.cs:
...ANSWER
Answered 2022-Mar-10 at 06:35Cross-Origin Resource Sharing (CORS) allows JavaScript code running in a browser on an external host to interact with your backend.
To allow all, use "*" and remove all other origins from the list.
I could only allow origins, not headers and methods?
Add the below configuration in your web.config file to allow headers and methods.
QUESTION
I want to find the index number of all items in a nested array in Cosmos DB :
Data :
...ANSWER
Answered 2022-Mar-09 at 04:25There is no built in support on Cosmos SQL API to achieve the above result. But you can implement the following suggestions
You could either write your own logic in User Defined Function or retrieve the data and format it in the way you need on the Client Side
Other way is to just include the index in the data model itself
QUESTION
Hi i am trying to get code coverage with .net5 in azure pipeline.
Run tests (not entire file)
...ANSWER
Answered 2021-Aug-25 at 08:52Please replace your PublishCodeCoverageResults with following steps:
QUESTION
I’ve the following yaml which I need to apply using the K8S go sdk (and not k8s cli) I didn’t find a way with the go sdk as it is custom resource, any idea how I can apply it via code to k8s?
This is the file
Any example will be very helpful!
...ANSWER
Answered 2022-Jan-17 at 16:00QUESTION
I updated my Asp.net core Blazor WebAssembly app to .net 6. Everything is fine, but the deploy from github actions doesn't work and throws this error:
...ANSWER
Answered 2021-Nov-15 at 05:26On Linux, it's important that any bash deployment scripts that get run have Unix line endings (LF) and not Windows line endings (CRLF).
Kuduscript will generate scripts with platform-appropriate line endings, but if those scripts are modified, or if you provide your own custom deployment scripts, it's important to make sure that your editor doesn't change the line endings.
If something seems off with your deployment script, you can always use the Kudu console to delete the contents of /home/site/deployments/tools.
This is the directory where Kudu caches kuduscript-generated deployment scripts. On the next deployment, the script will be regenerated.
The error you're currently seeing is a Kudu issue with running node/npm for deployments.
The easiest and fastest resolution for what you are currently seeing is to specify engines.node in your package.json.
Error: EISDIR: illegal operation on a directory, open '/home/site/wwwroot/wwwroot/Identity/lib/bootstrap/LICENSE'
EISDIR stands for "Error, Is Directory". This means that NPM is trying to do something to a file but it is a directory. In your case, NPM is trying to "read" a file which is a directory. Since the operation cannot be done the error is thrown.
Three things to make sure here
- Make sure the file exists. If it does not, you need to create it. (If NPM depends on any specific information in the file, you will need to have that information there).
- Make sure it is in fact a file and not a directory.
- It has the right permissions. You can change the file to have all permissions with "sudo chmod 777 FILE_NAME".
Note: You are giving Read, Write and Execute permissions to every one on that file.
Community Discussions, Code Snippets contain sources that include Stack Exchange Network
Vulnerabilities
No vulnerabilities reported
Install live-streaming-api
Setting up the Media Services resources on Azure
Creating the Azure Functions application
Setting up the environment variables
Deploying the application
Authenticating with the application
Set up the streaming software
Obviously, to use this application, you'll need an active Azure account. Please sign up for an account if you don't already have one. Once you have an account set up, sign in to the Azure Portal. First, begin by creating the Media Service resource. Now that the Media Service resource is available, create a streaming endpoint. Last, the Live Event(s) should be created.
From the search bar at the top, search for "Media Services," and then select the "Media Services" service
Click the Add button to create a new Media Service
Enter an Account Name, choose your active Subscription, and a Location
For the resource group, create a new one
Click on Storage Account > Create New
Enter a Storage Account Name, and leave all other settings as the default
Back on the Media Service creation screen, click the Create button
Click on the newly created Media Service resource
On the left panel, select Streaming Endpoints > Endpoint button to create a new Endpoint
Enter a name for the Streaming Endpoint, and configure the rest of the options on the page as desired
Click the Add Button
Inside of the Media Service resource, go to the left panel and select Live Streaming > Live Events tab > Add Live Event button
Enter a Live Event Name and configure the rest of the options as desired
Do not start the Live Event
Click the Review + Create button and confirm your entry to create the Live Event
Repeat these steps for each necessary Live Event
All of the application's configuration resides inside of the environment variables. Please refer to this table for a complete reference:. The sections below show how to obtain the necessary information to populate these environment variables for the application. Please log in to the Azure Portal to find the information shown in these steps. Some of the most important information in the above table is available from a single location in Azure. As for the rest of the properties, read on. This environment variable is set automatically by the Azure Portal when following the steps in the Setup Azure Application Insights section of this document. This value is completely up to you. Note that values less than 3 minutes are not allowed. The value can be as large as 1500 (25 hours). Webhooks can provide an excellent amount of extensibility and automation to your processes. The application will perform just fine if these variables are omitted. For more information on how the webhooks work, see the section titled Webhooks in this document. These environment variables are also optional. It is recommended to include them if you have a Sentry account and wish to monitor the health of this application. For more information on these environment variables, please see the Sentry Docs.
From the search bar at the top, search for "Media Services", and then select the "Media Services" service
In the table of available Media Services, select the service to use
In the panel on the left, select API Access
Under the Manage Your AAD App and Secret section, for the AAD App, click Create New > Enter a Name > click the Create button
Once the application is created, for the Secret, click Create New > Enter a Description and Expiration > click the Create button
Under the Connect to Media Services API section, ensure V3 is selected
Here is the mapping of environment variables to the values shown in Azure:
SENTRY_DSN: https://docs.sentry.io/error-reporting/configuration/?platform=csharp#dsn
SENTRY_ENVIRONMENT: https://docs.sentry.io/error-reporting/configuration/?platform=csharp#environment
SENTRY_RELEASE: https://docs.sentry.io/error-reporting/configuration/?platform=csharp#release
Now that all of the resources are in place on Azure, the streaming software can be configured. Common examples of streaming software include Wirecast or OBS Studio. Both pieces of software require a streaming URL to which the stream is sent.
In the Azure Portal, go to Media Services and select the appropriate resource
In the panel on the left select Live Streaming > Live Events tab
Select the appropriate Live Event from the list
Copy the Input URL from the Live Event details screen. This URL begins with rtmp:// or rtmps://. If you do not see this URL, make sure that the Essentials panel is expanded by clicking the toggle arrows near the top of the screen.
Paste the URL into your streaming software, according to the manufacture's instructions
Repeat these steps to extract the Input URL for each relevant Live Event
Support
Reuse Trending Solutions
Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items
Find more librariesStay Updated
Subscribe to our newsletter for trending solutions and developer bootcamps
Share this Page
