Streaming

NDIRTMPRTSPSRT

Which Streaming Protocol Should I Use?

The Rise 4K supports three streaming protocols, each designed for a different workflow. The right choice depends on where the video is going and what you're doing with it.

• NDI HX is the right choice if you're working in a live production environment with NDI-compatible software such as vMix, OBS (with the NDI plugin), or a NewTek TriCaster. NDI sources are automatically discoverable on the network, making cameras easy to add to your production. NDI HX delivers low-latency, high-quality video that's ideal for live switching and monitoring. The trade-off is that it requires NDI-compatible software on the receiving end and is best suited for a reliable local network.

• SRT is an excellent choice when streaming over the public internet because it automatically recovers from packet loss and network fluctuations while maintaining low latency. For many remote production workflows, it provides a more reliable connection than traditional RTMP.

• RTMP (and RTMPS) is the right choice if you're streaming directly to an online platform such as YouTube, Twitch, or Facebook Live. The camera handles the video encoding and transmission; you simply enter the platform's server URL and stream key. RTMPS adds encryption for secure delivery. Because RTMP is a push protocol, the camera initiates the connection to the streaming service, making it ideal for direct platform streaming but less suited for local production workflows.

• RTSP is the right choice if you're bringing a camera feed into local software such as OBS, vMix, VLC, or a recording server. RTSP is a pull protocol, meaning your software connects to the camera and requests the stream. It provides efficient, low-latency video for monitoring and recording and is widely supported by professional video software. RTSP is primarily designed for local network use and typically requires additional infrastructure or conversion before being streamed over the public internet.

In many professional workflows, cameras use multiple streaming protocols simultaneously. For example, you might use NDI HX for live production switching, RTSP for local recording or monitoring, and RTMP to stream directly to YouTube, all from the same camera at the same time, provided the camera supports simultaneous streaming.

Set Up NDI HX Streaming

NDI HX is designed for live production workflows where you need low-latency, high-quality video that's automatically discoverable by NDI-compatible software (vMix, OBS with NDI plugin, NewTek TriCaster, etc.).

What You Need

• NDI Tools or NDI-compatible software installed on the receiving device(s)
• Camera and receiving device on the same network

Steps

1. Download and install NDI Tools on the computer that will receive the stream. NDI Tools is available for free from ndi.video/tools.
2. Configure NDI settings on the camera:
   • Log in to the camera's web interface.
   • Navigate to the NDI settings tab.
   • Set the NDI name (this is how the camera will appear in NDI software).
   • Optionally set an NDI group for organizing multiple sources.
   • Configure encoding settings as needed.
   • Click Apply.
3. Select the camera within your NDI-compatible software. The camera should appear as an available NDI source automatically.

note

NDI HX is optimized for low-latency production use. The actual resolution and quality depend on your network bandwidth and NDI encoding settings.

tip

The Rise 4K can stream to multiple destinations simultaneously. You can use NDI for live production while also pushing an RTMP stream to a streaming platform.

Set Up SRT Streaming

SRT (Secure Reliable Transport) is designed to deliver high-quality, low-latency video over unpredictable networks such as the public internet. Unlike RTMP, SRT automatically compensates for packet loss and network jitter while encrypting the video stream with AES encryption.

SRT is commonly used to send video between remote production sites, studios, cloud production platforms, and broadcast facilities.

📋What you need

• A receiving device or software that supports SRT (OBS Studio, vMix, Haivision, FFmpeg, cloud production platforms, etc.)
• The IP address or hostname of the receiving device
• The receiving port number
• (Optional) An SRT passphrase if encryption is enabled

Steps

1. Configure your receiving software or server to accept an incoming SRT stream.
2. Log in to the camera's web interface.
3. Navigate to the Streaming settings.
4. Select SRT as the streaming protocol.
5. Enter the destination IP address or hostname.
6. Enter the destination port number.
7. If required, enable encryption and enter the shared passphrase.
8. Click Apply to begin streaming.

SRT is not automatically discoverable

Unlike NDI|HX, SRT requires you to manually specify the destination address and port. Before starting the stream, ensure the receiving device is reachable over the network and is configured to accept incoming SRT connections.

Set Up RTMP(S) Streaming

PTZOptics Rise 4K supports Push-Based RTMP (Real-Time Messaging Protocol), where the camera sends its video stream directly to a destination like YouTube, Twitch, Facebook Live, or a custom RTMP server. RTMPS adds TLS encryption for secure delivery.

What You Need

• A streaming platform account (YouTube, Twitch, etc.) or custom RTMP server
• The platform's stream URL and stream key

Steps

1. Log in to the camera's web interface.
2. Navigate to Audio & Video or Streaming settings.
3. Select RTMP (or RTMPS for encrypted streaming).
4. Enter the destination URL provided by your streaming platform (e.g., rtmp://a.rtmp.youtube.com/live2/).
5. Enter your stream key from the platform's dashboard.
6. Click Apply to start streaming.

tip

Use RTMPS instead of RTMP whenever your streaming platform supports it. RTMPS encrypts the stream in transit, protecting it from interception on untrusted networks.

note

Rise 4K can push to multiple RTMP destinations simultaneously, or combine RTMP with other protocols like RTSP or NDI.

Set Up RTSP Viewing

What You Need

PTZOptics Rise 4K supports pull-based RTSP (Real-Time Streaming Protocol). Your software (OBS, vMix, VLC, a recording server, etc.) requests the stream from the camera. It's ideal for local recording, monitoring, and pulling video into production software.

Steps

1. Log in to the camera's web interface and verify that RTSP is enabled in the Streaming settings.
2. In your receiving software, add a new media source using the camera's RTSP URL:

rtsp://<camera-ip>/stream1

For example, if your camera's IP is 192.168.1.100:

rtsp://192.168.1.100/stream1

3. The software will connect to the camera and begin receiving the video stream.

tip

RTSP offers low latency and works well for local recording. If you need to stream over the internet or to a platform like YouTube, use RTMP instead.

Using ONVIF for VMS Integration

If you're integrating with a security system or Video Management System (VMS):

1. Ensure ONVIF is enabled in the camera's network settings.
2. In your ONVIF client, add the camera using its IP address, port 80, and admin credentials.
3. The camera will appear as an ONVIF PTZ device.

Reference

Control Port Numbers

Protocol	Port	Transport	Use Case
VISCA over IP (TCP)	5678	TCP	PTZ joysticks, control systems
VISCA over IP (UDP)	1259	UDP	Low-latency PTZ control
Sony VISCA over IP	52381	TCP/UDP	Sony-compatible control systems
ONVIF	80	TCP	Security systems, VMS platforms
HTTP	80	TCP	Web interface, custom scripts
WebSockets	80/443	TCP	Real-time web applications

Streaming Protocol Comparison

Protocol	Direction	Best For	Latency	Encryption
NDI HX	Bidirectional (discoverable)	Live production on local networks	Very Low	No (local network)
SRT	Push (camera → receiver)	Reliable internet streaming and remote production	Low	Yes (AES)
RTMP	Push (camera → platform)	Direct-to-platform streaming (YouTube, Twitch)	Medium	No
RTMPS	Push (camera → platform)	Secure direct-to-platform streaming	Medium	Yes (TLS)
RTSP	Pull (software ← camera)	Local recording, monitoring, OBS/vMix input	Low	No

Network Specifications

Feature	Specification
Ethernet	10/100/1000 Mbps (Gigabit)
Max Cable Length	Up to 328 ft (100 m) with Cat5e/Cat6
PoE	PoE++ (802.3bt) required (or 802.3at if that's what this specific camera requires)
IP Configuration	DHCP (default) or Static
mDNS	Supported (Default local device address: ptzoptics.local)
Streaming Protocols	SRT, RTSP, RTMP/RTMPS, NDI|HX
Control Protocols	VISCA over IP, ONVIF, HTTP, WebSockets, Sony VISCA
Max Streaming Resolution	Up to 4K (3840 × 2160), depending on network bandwidth
Multi-Destination Streaming	Yes, stream to multiple protocols simultaneously