Can BlueIris load a video stream using a ffmpeg.sdp file?

[D0T-C0M]

My bambu P2S 3d printer puts out a video stream and provides a ffmpeg.sdp file that I've been using VLC player to load it to see the stream. Can BlueIris load this stream using this file?

Below is the contents of the ffmeg.sdp file

v=0
o=- 0 0 IN IP4 127.0.0.1
s=No Name
c=IN IP4 127.0.0.1
t=0 0
a=tool:libavformat LIBAVFORMAT_VERSION
m=video 1234 RTP/AVP 96
a=rtpmap:96 H264/90000
a=fmtp:96 packetization-mode=1; sprop-parameter-sets=XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX=; profile-level-id=XXXXXXX

ps I blanked out the sensitive info with X's

 

[TheWaterbug]

I don't know about ffmpeg/sdp, but Claude and I were able to get the feed from my Bambu H2C into Blue Iris using a go2rtc relay server. Here's the dump from Claude:

Bambu Lab Printer → Blue Iris via go2rtc (RTSP relay)​

Problem: Bambu Lab printers (with Live Video set to "LAN Only") stream video over RTSPS — RTSP wrapped in TLS, but with a nonstandard/self-signed handshake that most NVR software (including Blue Iris) can't consume directly.

Solution: Run go2rtc as a lightweight relay on the same machine as Blue Iris. It pulls the printer's odd RTSPS stream and re-serves it as plain RTSP that Blue Iris can add like any normal camera.

Steps​

1. Get the printer's connection details(from its touchscreen/network settings):
   • IP address
   • Access code (shown under LAN-only video settings)
   • Username is always bblp
2. Confirm reachability — printer listens on TCP port 322 for RTSPS (not the usual 554).
3. Install go2rtcon the Blue Iris box:
   • Download the Windows build from the go2rtc releases page (go2rtc_win64.zip)
   • Extract to e.g. C:\go2rtc\go2rtc.exe
4. Write C:\go2rtc\go2rtc.yaml:
   
   streams:<br> bambu_h2c: rtspx:/bblp:&lt;ACCESS_CODE&gt;@&lt;PRINTER_IP&gt;:322/streaming/live/1<br><br>rtsp:<br> listen: ":8554"<br><br>api:<br> listen: ":1984"<br>
   Key detail: use go2rtc's special rtspx:/ scheme (not rtsps:/) — it's go2rtc's purpose-built handler for Bambu's nonstandard TLS-RTSP handshake.
5. Make it persistent. Don't just run it from an SSH/RDP session — a process launched that way dies when the session closes (Windows job-object behavior). Instead create a Scheduled Task:
   
   schtasks /Create /TN "go2rtc" /TR "\"C:\go2rtc\go2rtc.exe\" -config \"C:\go2rtc\go2rtc.yaml\"" /SC ONSTART /RU SYSTEM /RL HIGHEST /F<br>schtasks /Run /TN "go2rtc"<br>
   Trigger = At Startup, runs as SYSTEM — survives reboots and doesn't need anyone logged in.
6. Open the firewall(inbound, scoped to go2rtc.exe) for whichever ports matter to you:
   • 8554 TCP — RTSP relay (Blue Iris needs this)
   • 1984 TCP — go2rtc web UI/API (optional, handy for debugging)
   • 8555 TCP — WebRTC (optional, only if you want browser-based low-latency viewing)
   • If Blue Iris and go2rtc are on the same box, only localhost access is required and you may not need to open anything beyond what's needed for your own debugging.
7. Verify before trusting it:
   • http://&lt;host&gt;:1984/api/streams should show the stream with a connected producer
   • http://&lt;host&gt;:1984/api/stream.mp4?src=bambu_h2c&amp;duration=2 should return real MP4 bytes (tens/hundreds of KB, not an error page) — proof video is actually flowing end-to-end
8. Add the camera in Blue Iris using:
   
   rtsp:/127.0.0.1:8554/bambu_h2c<br>
   No credentials needed on this URL — go2rtc already holds them internally.

Gotchas worth flagging to others​

• rtsps:/ vs rtspx:/ — ffmpeg wants rtsps:/ + -tls_verify 0; go2rtc wants rtspx:/. Mixing them up gives confusing TLS errors.
• Port is 322, not 554.
• A relay process started interactively over SSH/RDP looks alive but silently dies on logout — always wire it into Task Scheduler (or a proper service) before calling it done.
• If your camera software and the printer are on different subnets/VLANs, remember the relay only needs to reach the printer — but your test client pulling from the relay needs its own firewall path, which can trip people up if they test from a laptop across VLANs instead of from the NVR box itself.

Here's the camera setup in BI:



and here it is in ui3: