alexei.dolgolyov
f6f428515a
Remove completed/deferred items from TODO.md and add instruction to use TODO.md as the primary task tracker instead of TodoWrite. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
2.3 KiB
2.3 KiB
Pending Features & Issues
Priority: P1 quick win · P2 moderate · P3 large effort
Processing Pipeline
P3Transition effects — Crossfade, wipe, or dissolve between sources/profiles instead of instant cut- Complexity: large — requires a new transition layer concept in ProcessorManager; must blend two live streams simultaneously during switch, coordinating start/stop timing
- Impact: medium — polishes profile switching UX but ambient lighting rarely switches sources frequently
Output Targets
P2Art-Net / sACN (E1.31) — Stage/theatrical lighting protocols, DMX controllers- Complexity: medium — UDP-based protocols with well-documented specs; similar architecture to DDP client; needs DMX universe/channel mapping UI
- Impact: medium — opens stage/theatrical use case, niche but differentiating
Capture Engines
P3SCRCPY capture engine — Implement SCRCPY-based screen capture for Android devices- Complexity: large — external dependency on scrcpy binary; need to manage subprocess lifecycle, parse video stream (ffmpeg/AV pipe), handle device connect/disconnect
- Impact: medium — enables phone screen mirroring to ambient lighting; appeals to mobile gaming use case
Code Health
P1"Start All" targets button — "Stop All" exists but "Start All" is missingP2Manual backup trigger endpoint —POST /system/auto-backup/trigger(~5 lines)P2Scene snapshot should capture device brightness —software_brightnessnot saved/restoredP2Distinguish "crashed" vs "stopped" in dashboard —metrics.last_erroris already populatedP3CSS source import/export — share individual sources without full config backup
UX
P1Collapse dashboard running target stats — Show only FPS chart by default; uptime, errors, and pipeline timings in an expandable section collapsed by defaultP1Daylight brightness value source — New value source type that reports a 0–255 brightness level based on daylight cycle time (real-time or simulated), reusing the daylight LUT logicP1Tags input: move under name, remove hint/title — Move the tags chip input directly below the name field in all entity editor modals; remove the hint toggle and section title for a cleaner layout