Networking & Streaming
PTZOptics Cameras connect to your network over a single Ethernet cable, giving you access to the web interface, video streaming, and remote control. This page covers the most common networking and streaming tasks, followed by protocol decision guidance and reference tables.
If you connected the camera to your network via Ethernet and powered it on, the camera will automatically request an IP address from your network's DHCP server. This process typically takes 10–30 seconds.
Find Your Camera on the Network
Before you can configure streaming or control the camera remotely, you need to find it on your network. Choose the method that works best for your situation.
Method 1: Use the Camera's Hostname (Easiest)
PTZOptics Cameras support mDNS (multicast DNS), so you can reach them by hostname without knowing the IP address.
- Open a web browser on any device connected to the same network.
- Type the following address and press Enter:
http://ptzoptics.local/
- You will be prompted to set up a username and password on first login. The default username is admin.
If you have multiple cameras on the same network, give each camera a unique Device ID from the web interface's Device Info tab. Then reach each camera by its ID: http://camera-one.local, http://camera-two.local, etc.
Method 2: Display the IP on Your Video Output
If the hostname method doesn't work, use the IR remote to display the camera's IP address directly on the connected display.
- Make sure the camera is connected to a display via HDMI, SDI, or USB.
- Press the following buttons on the IR remote in order:
[*] → [#] → [4]
- The camera's IP address will appear as an overlay on the video feed.
Method 3: Find Your Network Range Manually
If you need to scan for the camera's IP, first determine your computer's local network range.
Windows:
- Open the Start menu, type CMD, and open the Command Prompt.
- Type
ipconfigand press Enter. - Locate the IPv4 Address under your active network adapter (e.g.,
192.168.15.117). - Your network range is
192.168.15.xxx. The camera will have a similar address in that range.
Mac:
- Open Terminal (Applications → Utilities → Terminal).
- Type
ipconfig getifaddr en0and press Enter. - The result is your computer's local IP address. The camera will have a similar address in the same range.
Access the Web Interface
Once you have the camera's IP address:
- Open a web browser and enter:
http://<camera-ip-address> - Log in with username admin and set a strong password on first login.
Set a strong password to secure your camera, especially if it's accessible on a shared network.
How to set a Static IP Address
Certain setups, such as permanent installations, require setting a static IP so the camera is always reachable at the same address.
- Log into the camera's web interface.
- Navigate to Network Settings (or Device Settings > Network in Horizon).
- Change the IP Configuration Type from DHCP to Static.
- Enter the following:
- IP Address: The static IP you want to assign (e.g.,
192.168.1.100) - Subnet Mask: Typically
255.255.255.0 - Gateway: Your router's IP address (e.g.,
192.168.1.1) - DNS Server: Your network's DNS server (often the same as the gateway)
- IP Address: The static IP you want to assign (e.g.,
- Click Apply to save.
Make sure the static IP you choose is outside your DHCP server's address pool to avoid IP conflicts. Check your router's DHCP settings to see which addresses are being handed out automatically. If you need further assistance, contact your network administrator.
Which Streaming Protocol Should I Use?
The Move 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.
-
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
- Download and install NDI Tools on the computer that will receive the stream. NDI Tools is available for free from ndi.video/tools.
- 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.
- Select the camera within your NDI-compatible software. The camera should appear as an available NDI source automatically.
NDI|HX is optimized for low-latency production use. The actual resolution and quality depend on your network bandwidth and NDI encoding settings.
The Move 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 RTMP(S) Streaming
PTZOptics cameras support 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
- Log in to the camera's web interface.
- Navigate to Audio & Video or Streaming settings.
- Select RTMP (or RTMPS for encrypted streaming).
- Enter the destination URL provided by your streaming platform (e.g.,
rtmp://a.rtmp.youtube.com/live2/). - Enter your stream key from the platform's dashboard.
- Click Apply to start streaming.
Use RTMPS instead of RTMP whenever your streaming platform supports it. RTMPS encrypts the stream in transit, protecting it from interception on untrusted networks.
The Move 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 cameras support 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
- Log in to the camera's web interface and verify that RTSP is enabled in the Streaming settings.
- 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
- The software will connect to the camera and begin receiving the video stream.
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):
- Ensure ONVIF is enabled in the camera's network settings.
- In your ONVIF client, add the camera using its IP address, port 80, and admin credentials.
- The camera will appear as an ONVIF-compliant 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, NDI workflows | Very low | No (local network) |
| 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.3at) required |
| IP Configuration | DHCP (default) or Static |
| mDNS | Supported (hostname: ptzoptics.local) |
| Streaming Protocols | RTSP, RTMP/RTMPS, NDI|HX |
| Control Protocols | VISCA over IP, ONVIF, HTTP, WebSockets, Sony VISCA |
| Max Streaming Resolution | 4K (3840 x 2160) depends on network bandwidth |
| Multi-Destination | Yes, stream to multiple protocols simultaneously |