docs: canonical Caspar LED vs PGM output topology - #30
Conversation
Add OUTPUT_TOPOLOGY.md as the single map of which RE/Sofie sources land on Caspar ch1 (LED allow-list) vs ch2 (PGM). Point AGENTS and integration docs at it; fix inverted CH1/CH2 catalogue notes and the handoff that put l3d-mod on LED. Co-authored-by: Jakub Doboš <[email protected]>
|
Warning Review limit reached
Next review available in: 115 minutes You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (6)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
2 participants
Why
LED vs PGM routing was scattered and contradictory (e.g. catalogue “CH1 PGM” / “CH2 LED”, intro handoff putting Presenter MOD on LED). Operators can’t see L3Ds on the LED wall by design — need one committed map.
What
docs/integration/OUTPUT_TOPOLOGY.md: allow-list, layer tables, RE piece cheat sheet, “why L3D missing” checklist, taxonomy disentangle.AGENTS.md, SPRAVY, DOUBLEBOX, and blueprints handoffs at it; fix inverted channel notes.Note on L3D visibility
gfx/l3d-*→ Caspar ch2 layer 121 only. Watching both consumers and still blank usually means templates/deploy or pending blueprints GFX-output fix (#61 companion), not LED routing. This PR is docs-only.