# Destinations

BridgeWIZ supports the following types of destinations:

* SDI output
* NDI output
* Network Streaming
* Local Files

Each of the types supports its own features.

Once configured, you can see the destination in the “*Destinations*” list with the “*Bridge to …*” name that shows you a type and main information about the type. For example, a name of an NDI stream, or a streaming protocol.

![](https://3554148854-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwE5Dw5CXP63kQw6XW1le%2Fuploads%2Ff7sjRmKhj1mkAgoM6Qc8%2F10.png?alt=media) ![](https://3554148854-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwE5Dw5CXP63kQw6XW1le%2Fuploads%2FGaAN5PWyF2v6ZeLzjGfL%2F11.png?alt=media)

## SDI outputs

For output SDI devices, BridgeWIZ supports only Blackmagic Design devices (Decklink and Intensity families). For this destination, you should select a device and set the output line. Usually, SDI and HDMI are running at the same time, and you choose a mode for Composite or Component outputs if you work with SD resolutions.

![](https://3554148854-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwE5Dw5CXP63kQw6XW1le%2Fuploads%2FZCvrTXfGVyIG5Ou9BcRR%2F12.png?alt=media)

## NDI outputs

For NDI signals, you should set the output stream name (by default, BridgeWIZ uses “BridgeWIZ NDI” as a stream name). Optionally, you can set up an NDI group to protect a stream.

![](https://3554148854-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwE5Dw5CXP63kQw6XW1le%2Fuploads%2FPW4iK1n9wMpPJKR5ZdmZ%2F13.png?alt=media)

## Network streaming

Network streaming supports the following protocols:

* RTMP - suitable for YouTube, Twitch, and other media platforms as well as entry points of CDNs (Akamai, for example).
* UDP - transport stream to hardware devices
* SRT - a modern protocol to stream to studios and devices

For each protocol, you should set a target URL and a bitrate. The bitrate can be adjusted based on the input content – for this, you can keep using the “Auto”. The video encoder is configured automatically based on your system hardware. BridgeWIZ supports GPU-powered encoders from NVIDIA, AMD, and Intel. If nothing is available, it uses a software-based encoding.

For RTMP and UDP, you should set the streaming parameters like a stream key. Also, if it is required, you can set a username and a password. For this type, you can have more than just RTMP streaming – you can have a backup URL specified to have more than just a single stream running at once. This mode could help you save some resources by streaming to RTMP and UDP at the same time, for example.

<figure><img src="https://3554148854-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwE5Dw5CXP63kQw6XW1le%2Fuploads%2Fmsk2aQj4YGcaK4LBUisx%2F14.png?alt=media" alt=""><figcaption></figcaption></figure>

In addition to the above, for SRT streams you can set a stream type (caller, listener, or rendezvous).

## Local files

With BridgeWIZ, you can record the input video into local files. You should set a target folder to keep the recorded files and set a naming prefix for the files. Local dates and times will be used as a template for the resulting file names. If you set the “Split Every” option, your recordings will be cut into chunks of equal duration.

<figure><img src="https://3554148854-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwE5Dw5CXP63kQw6XW1le%2Fuploads%2FiJZUbrtguvTnzE4gVrd4%2Fimage.png?alt=media&#x26;token=1fd48be9-405f-4874-bf25-e9148c504b0f" alt=""><figcaption></figcaption></figure>
