Streaming immersive 6K video reliably requires more than selecting a resolution and pressing the live button. The camera encoder, SRT transport settings, Wi-Fi conditions, and the decoder in OBS Studio all need to work together.
This guide provides a field-tested configuration for streaming 6000 × 3000 video at 30 FPS from SLAM XCAM to OBS Studio using SRT and H.265/HEVC. The recommended profile maintained a stable connection without sustained congestion, mosaic artifacts, or black-screen events during final validation. A brief isolated stutter may still occur if camera processing load, temperature, Wi-Fi jitter, or receiver decoding load rises temporarily.
Recommended 6K30 profile
6000 × 3000 · 30 FPS · H.265/HEVC · 24 Mbps · SRT latency 800 ms · OBS hardware decoding enabled
What you need
- A SLAM XCAM running the current application version with 24, 30, and 36 Mbps options for 6K30 live streaming.
- A computer running OBS Studio with HEVC decoding support.
- The camera and OBS computer connected to the same 5 GHz Wi-Fi network or wired LAN.
- Inbound UDP port 9000 allowed by the computer firewall.
- The IPv4 address of the OBS computer. The example in this article uses
192.168.2.121.
Step 1: Configure SLAM XCAM
Open the live-stream settings in the SLAM XCAM application and use the following values.
| Setting | Value |
|---|---|
| Protocol | SRT |
| Resolution | 6K (actual encoded output: 6000 × 3000) |
| Frame rate | 30 FPS |
| Codec | H.265 / HEVC |
| Bitrate | 24 Mbps recommended |
| SRT role | Caller |
Enter the following address in the camera application:
srt://192.168.2.121:9000/mode=callerImportant: the current camera application expects /mode=caller after the port. Do not enter the standard ?mode=caller query syntax on the camera side.
Step 2: Choose the 6K30 bitrate
| Bitrate | Recommended use | Notes |
|---|---|---|
| 24 Mbps | Stable baseline | Lowest network and decoder load. Start here. |
| 30 Mbps | Higher image quality | Use after 24 Mbps remains stable for at least 10 minutes. |
| 36 Mbps | Maximum available quality | Requires stronger Wi-Fi and reliable 6K HEVC decoding. |
Step 3: Configure OBS Studio
- Open OBS Studio and add a Media Source to the target scene.
- Disable Local File.
- In the Input field, enter the SRT listener address shown below.
- Enter
mpegtsin Input Format. - Enable Use hardware decoding when available.
- Confirm the settings and keep the Media Source active before starting the stream on the camera.
srt://192.168.2.121:9000?mode=listener&latency=800000Replace 192.168.2.121 with the actual IPv4 address of the OBS computer. The latency value is measured in microseconds, so 800000 equals 800 ms.
If the receiving GPU cannot decode 6000-pixel-wide HEVC reliably, disable hardware decoding and test software decoding. Software decoding may require a high-performance CPU.
Step 4: Start the stream in the correct order
- Start OBS first and activate the SRT Media Source in listener mode.
- On SLAM XCAM, confirm 6K, 30 FPS, H.265, and 24 Mbps.
- Start live streaming on the camera.
- Wait several seconds for the first HEVC keyframe, then confirm video and audio in OBS.
- When finished, stop streaming on SLAM XCAM first, then deactivate the OBS Media Source.
How to check that the stream is stable
- OBS displays a continuous 2:1 VR frame at 6000 × 3000.
- The picture remains fluid for at least 10 minutes.
- No sustained mosaic artifacts, black frames, or repeated reconnections occur.
- Audio remains present and synchronized.
- The camera reports approximately 24 Mbps during normal scenes.
Troubleshooting
| Symptom | Likely cause | Corrective action |
|---|---|---|
| Connection error | Listener inactive, wrong IP/port, or UDP 9000 blocked. | Start OBS first and verify the IPv4 address and firewall. |
| Stutter or mosaic | Latency too low, Wi-Fi jitter, or decoder overload. | Use 800 ms latency and 24 Mbps; check OBS GPU/CPU load. |
| Black screen | Receiver cannot sustain 6000 × 3000 HEVC decoding. | Toggle hardware decoding, update GPU drivers, and restart the Media Source. |
| Stream disconnects | Receiver closes the SRT session after congestion or decoder failure. | Keep 24 Mbps and restart the OBS listener before the camera. |
| Video does not recover | Listener is no longer accepting a caller. | Deactivate and reactivate the Media Source, then restart camera streaming. |
Frequently asked questions
Why is 24 Mbps recommended for 6K30?
It provides the best validated balance between image quality, network load, and receiver decoding stability. Higher settings are available, but they should be tested on the actual production network and OBS computer.
Why does 6K30 use 800 ms SRT latency?
6K HEVC frames, especially keyframes, are significantly larger than 4K frames. The larger receive window gives SRT more time to recover delayed packets before they become unusable.
Can the latency be reduced?
Yes, but only after the 800 ms profile remains stable for an extended test. Reducing latency lowers end-to-end delay while also reducing tolerance for Wi-Fi jitter.
Why can a brief stutter occur even when the SRT cache is empty?
A short stutter can also come from temporary camera processing load, thermal throttling, or receiver decoding load. Monitor both the camera temperature and the GPU/CPU utilization on the OBS computer.
Recommended pre-event test
Before a production stream, run a minimum 15-minute test using the same camera position, router, OBS computer, bitrate, and decoder setting planned for the event. Keep 24 Mbps as the baseline and increase the bitrate only after the complete setup passes.