node-agent BMD_COUNT override hardcodes /dev/blackmagic/dv${i} but real devices are /dev/blackmagic/io${i} #109
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Fixed.
detectHardware()inservices/node-agent/index.jsnow prefers filesystem detection — reads actual/dev/blackmagic/*entries and reports their real names (soio0,io1show as/dev/blackmagic/io0).If
/dev/blackmagicisn't mounted into the container and the operator usesBMD_COUNTto force-report a count, the newBMD_DEVICE_PREFIXenv var (defaultdv, setiofor DeckLink IO/Quad) controls the synthesized device names.docker-compose.worker.ymldocuments the new option.zgaetano referenced this issue2026-05-26 18:22:49 -04:00
Fix Plan — #109 BMD_COUNT override hardcodes wrong device paths
Root cause:
node-agent/index.js:288-298— zampp2 hasBMD_COUNT=4, override path stores fake paths/dev/blackmagic/dv0..dv3. Real devices are/dev/blackmagic/io0..io3.Fix: Prefer real device list from filesystem, fall back to override only when unreadable:
Files:
services/node-agent/index.js:288-298Effort: ~30min
**Priority: P2 — cosmetic but wrong data in DB