System guide
Understand device responsibilities, transports, emergency behaviour and current scope before troubleshooting.
Open System GuideSupport for the
current system.
Find help for Showduino Studio, HauntSync and the Director → Communications Controller → P4 Show Engine → specialist-node architecture.
Studio help
Project saving, imports, exports, timelines, routing and creator-mode operation.
Open StudioHauntSync help
Projects, registered hardware roles, local storage and account-ready project management.
Open HauntSyncHow the current system behaves
Does a live show need the browser?
No. Studio is the authoring environment. The P4 Show Engine is intended to own the live runtime after a production has been loaded.
Does losing the Director stop the show?
It should not. The Director is an operator interface, not the runtime authority.
What does the Communications Controller decide?
Nothing about the show. It bridges ESP-NOW traffic to the P4 over UART and provides communications diagnostics.
What happens in an emergency?
Emergency state interrupts normal playback, latches, overrides pixel outputs to bright white and does not automatically resume the show when the initiating condition clears.
Is DMX part of the current build?
No. DMX is intentionally outside the current development scope while the core relay, MOSFET, pixel, audio and runtime path is completed.
Found a reproducible software bug?
GitHub issues are the best place to keep technical problems, logs and fixes attached to the codebase.