v1.8.8 — Fix Bambu RTSP camera: drop -tls_verify (unsupported by bundled ffmpeg)

Author: BenGlut

CHANGELOG.md

@@ -5,6 +5,14 @@ Versions follow [Semantic Versioning](https://semver.org/).
 
 ---
 
+## v1.8.8 — 2026-05-29
+
+### Fixed
+
+- **Bambu RTSP cameras (X1C / X1E / P2S / H2x) now actually stream** — the camera launched ffmpeg with `-tls_verify 0`, an option the bundled ffmpeg doesn't recognise, so it errored out and showed nothing as soon as it reached a reachable printer. Removed the flag — TLS verification is off by default, so the printer's self-signed certificate is still accepted. This completes the cross-platform camera fix (Windows + macOS), verified live against a P2S.
+
+---
+
 ## v1.8.7 — 2026-05-29
 
 ### Fixed

WORKLOG.md

@@ -1,14 +1,13 @@
-# Worklog — v1.8.7 (in progress)
+# Worklog — v1.8.8 (in progress)
 
 ## Added
 
 ## Changed
 
 ## Fixed
 
-- **Bundled ffmpeg not found at runtime on packaged Windows (RTSP camera dead despite v1.8.6)** — `main.js`
-  - `_detectFfmpeg` used `require('ffmpeg-static').replace('app.asar', 'app.asar.unpacked')`, which points inside `app.asar` — a path the OS cannot spawn (and `fs.accessSync` can even false-positive on it via the asar shim, so a bogus binary path gets selected). Now keyed on `app.isPackaged`: in a packaged app the binary path is built straight from `process.resourcesPath` (`…/resources/app.asar.unpacked/node_modules/ffmpeg-static/ffmpeg.exe`, the real on-disk, spawn-safe location); in dev it uses `require('ffmpeg-static')`. Windows manual-install fallbacks kept.
-  - Added diagnostics: `[ffmpeg] using <path>` / `[ffmpeg] NOT FOUND — checked: …` and `[bambu-rtsp:<key>] launching ffmpeg → rtsps://bblp:***@<ip>:322 (bin: …)`, landing in `electron-log` (`%APPDATA%\Tiger Studio Manager\logs\main.log`).
+- **Bambu RTSP camera failed with "Option tls_verify not found" (no stream on bundled ffmpeg)** — `main.js`
+  - The RTSP launch passed `-tls_verify 0` before `-i`, applied to the rtsp demuxer. Older ffmpeg (the bundled ffmpeg-static 6.0) has no `tls_verify` on the rtsp demuxer → ffmpeg exits code 1 when it reaches the TLS stage of a reachable printer. Homebrew ffmpeg 8.x has it, which masked the bug in dev before ffmpeg-static was bundled. Removed the flag — the tls protocol defaults to `verify=0`, so the printer's self-signed cert is still accepted (works on ffmpeg 6.0 and 8.x). This was the real reason the P2S camera showed no stream on Windows (and on macOS once it switched to the bundled binary).
 
 ## Removed
 

main.js

@@ -1853,7 +1853,10 @@ ipcMain.handle('timelapse:download', async (_evt, videoUrl, suggestedFilename) =
       const proc = spawn(_ffmpegBin, [
         '-loglevel', 'error',          // show errors in main-process console
         '-rtsp_transport', 'tcp',
-        '-tls_verify',    '0',         // ignore self-signed printer cert
+        // No -tls_verify: the rtsp demuxer in older ffmpeg (e.g. the bundled
+        // ffmpeg-static 6.0) doesn't expose it → "Option tls_verify not found".
+        // The tls protocol defaults to verify=0 anyway, so the printer's
+        // self-signed cert is accepted without it (works on ffmpeg 6.0 and 8.x).
         '-i', rtspUrl,
         '-vf', 'fps=5',                // ~5 fps is plenty for a status cam
         '-f', 'image2pipe',

package.json

@@ -1,6 +1,6 @@
 {
   "name": "tigertag-inventory",
-  "version": "1.8.7",
+  "version": "1.8.8",
   "description": "Tiger Studio Manager — desktop app",
   "main": "main.js",
   "engines": {