Skip to content

Commit b0dbc0b

Browse files
authored
Merge pull request #178306 from mayankchief/patch-5
Update get-started-livepipelines-portal.md
2 parents 58d3099 + 51e883c commit b0dbc0b

File tree

1 file changed

+11
-11
lines changed

1 file changed

+11
-11
lines changed

articles/azure-video-analyzer/video-analyzer-docs/cloud/get-started-livepipelines-portal.md

Lines changed: 11 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -45,28 +45,28 @@ This section shows you how to deploy an RTSP camera simulator on Azure Linux VM,
4545
> Please note that this RTSP camera simulator endpoint is exposed over the internet and hence will be accessible to anyone who knows the RTSP URL.
4646
4747
**Deployment steps:**
48-
1. Deploy a standard_D2s_v3 series Azure Linux VM running 'Ubuntu Server 18.04' operating system, [see here](../../../virtual-machines/linux/quick-create-portal.md) for VM creation steps, don't have to install web server in linked article. Also allow SSH port in deployment wizard so that you could connect to VM using SSH connection.
48+
1. Deploy a standard_D2s_v3 series Azure Linux VM running 'Ubuntu Server 18.04' operating system, [see here](../../../virtual-machines/linux/quick-create-portal.md) for VM creation steps, don't have to install web server mentioned in the linked article. Also allow SSH port in deployment wizard so that you could connect to VM using SSH connection.
4949
1. Enable inbound connections for RTSP protocol. In the Azure portal, open the management pane for the Linux VM you created above.
5050

5151
1. Click on Networking - you will see the blade open to the inbound port rules for the network security group (NSG) that was created for you to support inbound SSH connections.
5252
1. Click on Add inbound port rule to add a new one
5353
1. In the pane that opens up, change Destination port ranges to 554. Choose a Name for the rule, such as "RTSP". Keep all other values as default. See [here](../../../virtual-machines/windows/nsg-quickstart-portal.md) for more details.
54-
1. Install docker on the VM using instructions [here](https://docs.docker.com/engine/install/ubuntu/), only follow the steps till verifying the Docker installation by running the ‘hello-world’ image.
54+
1. Install Docker on the VM using instructions [here](https://docs.docker.com/engine/install/ubuntu/), only follow the steps till verifying the Docker installation by running the ‘hello-world’ image.
5555
1. Connect to your VM, for example using SSH. From the terminal window, create a local folder such as 'localmedia' to host media files, this VM local folder will be used to map to RTSP mediaserver container.
5656
1. Copy an MKV file used to simulate the camera feed as follows:
5757

5858
```
5959
cd localmedia
6060
wget https://lvamedia.blob.core.windows.net/public/camera-1800s.mkv
6161
```
62-
1. From the root directory, start the RTSP server on the VM using the pre-built container image as follow
62+
1. Start the RTSP server on the VM using the pre-built container image as follow
6363
6464
```
65-
sudo docker run -d -p 554:554 -v ${PWD}/localmedia:/live/mediaServer/media mcr.microsoft.com/ava-utilities/rtspsim-live555:1.2
65+
sudo docker run -d -p 554:554 -v ${PWD}:/live/mediaServer/media mcr.microsoft.com/ava-utilities/rtspsim-live555:1.2
6666
```
6767
1. Once the RTSP server is running, clients can now connect to it via an RTSP URL:
6868
69-
- Go the 'Overview' page of your VM in Azure portal and note down the value of 'Public IP address'
69+
- Go to 'Overview' page of your VM in Azure portal and note down the value of 'Public IP address'
7070
7171
- The RTSP URL is rtsp://{Public IP address}:554/media/camera-1800s.mkv, can be tested with a player from desktop e.g. VLC
7272
@@ -98,13 +98,13 @@ Once the Video Analyzer account is created, you can go ahead with next steps t
9898
9999
- **Create a pipeline topology** wizard will appear on the portal
100100
- Select **Try sample topologies**-> select **Live capture, record, and stream from RTSP camera** topology-> Select 'Proceed' on **Load sample topology** dialog box.
101-
- The wizard to edit the 'RTSP source to Video sink' live pipeline topology will be displayed.
101+
- The wizard to create the live pipeline topology will be displayed, showing RTSP source node connected to a Video sink node.
102102
- Enter the required fields to create topology:
103103
104104
- **Topology name** – Enter the name for the topology
105105
- **Description** (optional) – Brief description about the topology
106106
- **Kind** (prepopulated ‘Live’)
107-
- For **Rtsp source** node: Set **Transport** property value as TCP
107+
- Select the **RTSP source** node, then set **Transport** property value as TCP
108108
- Select **Save** with default configuration for rest of the properties
109109
1. Next step is to create a live pipeline using the topology created in previous step.
110110
@@ -118,17 +118,17 @@ Once the Video Analyzer account is created, you can go ahead with next steps t
118118
- **videoNameParameter** - Unique name for the target video resource to be recorded. Note: use a unique video resource for each camera (or MKV file)
119119
- Select **Create** and you will see a pipeline is created in the pipeline grid on the portal.
120120
- Select the live pipeline created in the grid, select **Activate** option available towards the right of the pane to activate the live pipeline. This will start your live pipeline and start recording the video
121-
1. Now you would be able to see the video resource under Video Analyzer account-> **Videos** pane in the portal. Its status will indicate **Is in use** as pipeline is active and recording.
121+
1. Now you would be able to see the video resource under Video Analyzer account-> **Videos** pane in the portal. Its status will indicate **Recording** as pipeline is active and recording the live video stream.
122122
1. After a few seconds, select the video and you will be able to see the [low latency stream](../playback-recordings-how-to.md).
123123
124124
> [!div class="mx-imgBorder"]
125125
> :::image type="content" source="./media/camera-1800s-mkv.png" alt-text="Diagram of the recorded video captured by live pipeline on the cloud.":::
126126
127127
> [!NOTE]
128128
> If you are using an RTSP camera simulator, it’s not possible to accurately determine end-to-end latency. Further, after the RTSP camera simulator reaches the end of the MKV file, it will stop. The live pipeline will attempt to reconnect and after a while, the simulator will restart the stream from the beginning of the file. If you let this live pipeline run for many hours, you will see gaps in the video recording whenever the simulator stops and restarts.
129-
* If necessary, refer Activity log to quickly verify your deployment operations. Refer [here](./monitor-log-cloud.md) for monitoring and event logs.
130-
* To deactivate the pipeline recording go to your Video Analyzer account, on the left panel select **Live**-> **Pipelines**-> select the pipeline to be deactivated then select **Deactivate** in pipeline grid, it will stop the recording.
131-
* You can also continue to delete the pipeline & topology if they are not needed.
129+
1. If necessary, refer Activity log to quickly verify your deployment operations. Refer [here](./monitor-log-cloud.md) for monitoring and event logs.
130+
1. To deactivate the pipeline recording go to your Video Analyzer account, on the left panel select **Live**-> **Pipelines**-> select the pipeline to be deactivated then select **Deactivate** in pipeline grid, it will stop the recording.
131+
1. You can also continue to delete the pipeline & topology if they are not needed.
132132
133133
## Clean up resources
134134

0 commit comments

Comments
 (0)