# RTMP | RTMPS

**Real-Time Messaging Protocol (RTMP)** has been well supported by popular hardware and software applications for many years. In addition to WebRTC, OptiView Real-time Streaming allows you to broadcast and distribute content from an RTMP or secure RTMPS source.

OptiView Real-time Streaming also supports the ability to live stream multiple bitrates from professional RTMP encoders and deliver WebRTC Simulcast. For more information, see [Simulcast](https://docs-preview.optiview.dolby.com/pr-861/millicast/distribution/using-webrtc-simulcast.md#how-to-enable-simulcast-from-an-encoder).

This document will outline how to set up and broadcast low-latency RTMP streams via the OptiView Real-time CDN.

## RTMP publishing

> **Getting Started**
>
> If you haven't already, begin by following the [Getting Started](https://docs-preview.optiview.dolby.com/pr-861/millicast.md) tutorial to create an OptiView Real-time application and start your first broadcast. You will need to create a publish token to generate the necessary RTMP details.

Select the publish token that you want to use for your RTMP streaming application.

![](/pr-861/assets/images/rtmp_publish_token-b3e67407dcdc7d95978d7c5c3a52fe57.png)

### How to find your RTMP publish URL

Click on the *Publishing* tab of the token screen where you will find details for the various protocols such as [WHIP](https://docs-preview.optiview.dolby.com/pr-861/millicast/broadcast/webrtc-and-whip.md), [SRT](https://docs-preview.optiview.dolby.com/pr-861/millicast/broadcast/srt.md), and RTMP.

![](/pr-861/assets/images/rtmp_publish_url-5dada699b0bb4783d1c5622d2557f1a2.png)

In order for you to publish with RTMP, you will need two items from this interface, the **RTMP publish path** and **RTMP publish stream name**. Note that the *RTMP publish stream name* value from the dashboard is a concatenation of the *stream name* and the *publishing token* as a query string parameter.

Depending on the particular RTMP integration you may need to specify these details separately or as a full URL endpoint:

> **RTMP Publish URL** = **RTMP publish path** + `/` + **RTMP publish stream name**

This information will authenticate you as a publisher on OptiView Real-time Streaming and allow you to successfully broadcast a live feed using your account. Typically the URL will look something similar to:

```text
rtmp://rtmp-auto.millicast.com:1935/v2/pub/myStreamName?token=5c7a1529...bdc8&priority=1&sourceId=YourId
```

For a secure RTMPS endpoint, you would substitute the **RTMPS publish path**, which uses a different protocol and port.

**Note:** The the `priority` and `sourceId` are optional parameters that allow you to specify the priority and a unique ID for the published stream.

### Suggested RTMP Encoder Settings

Each setup can be slightly different, so adjust the below settings to find what fits best for you.

#### OBS with RTMP

See the [OBS Integration Guide](https://docs-preview.optiview.dolby.com/pr-861/millicast/software-encoders/obs.md) for more details.

| Name              | Value           |
| ----------------- | --------------- |
| Encoder           | **nvenc**       |
| Rate Control      | **CBR**         |
| Keyframe Interval | **2 (seconds)** |
| Preset            | **Max Quality** |
| Profile           | **high**        |
| x264 options      | **bframes=0**   |

**Note:** These are the recommended settings for the NVIDIA NVENC H.264 encoder. If you do not have the NVIDIA NVENC H.264 encoder available, we recommend setting the Rate Control to `CBR` and the profile to `baseline`.

Setting **x264 options** to *bframes=0* or **profile** to *baseline* is required to avoid video artifacts on the viewer and recording side.

#### vMIX with RTMP

See the [vMix Integration Guide](https://docs-preview.optiview.dolby.com/pr-861/millicast/software-encoders/vmix.md) for more details.

|                   |                 |
| ----------------- | --------------- |
| Application       | **FFMPEG**      |
| Profile           | **baseline**    |
| Level             | **3.1**         |
| Preset            | **ultrafast**   |
| Keyframe Interval | **2 seconds**   |
| Threads           | **4**           |
| Net Buffer        | **5 (seconds)** |

#### Basic RTMP Settings

The following are basic recommended settings for any encoder:

|                   |                          |
| ----------------- | ------------------------ |
| Codec             | **H.264**                |
| bframes           | **disabled**             |
| Profile           | **baseline, main, high** |
| Keyframe Interval | **2 seconds**            |

**Note:** If you cannot disable bframes, we recommend setting the Profile to `baseline`.

If you have any questions or suggestions, feel free to [contact us](https://support.dolby.io/?_gl=1*1bfsqox*_ga*MTExNDIzMDc0OC4xNjgzNTY3ODk2*_ga_CTSBFC56JT*MTY4OTAwNDAwMS4yOS4xLjE2ODkwMTEwMjYuMC4wLjA.).

## Learn more

Find additional integration guides such as [Haivision](https://docs-preview.optiview.dolby.com/pr-861/millicast/hardware-encoders/haivision.md), [Zoom](https://docs-preview.optiview.dolby.com/pr-861/millicast/software-encoders/zoom.md), [Teradek](https://docs-preview.optiview.dolby.com/pr-861/millicast/hardware-encoders/teradek.md), [Videon](https://docs-preview.optiview.dolby.com/pr-861/millicast/videon.md), and more. To find examples for how to use this explore RTMP related articles from the [developer blog](https://optiview.dolby.com/resources/blog/tag/rtmp/).