docs: describe the v2 controller's API, UI and tests
API.md now documents what the firmware serves: groups, combined brightness, beat-driven sequences, import/export, /api/audio, patterns over ESP-NOW, outputs, /ws, driver OTA, and how API calls become driver messages and group commands. The user guide follows the current UI; the in-app audio help describes the microphone instead of input devices. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
1 parent
bfeeb958df
commit
b2cd242390
5 files changed
+335
-429
No files matched your search
@@ -1057,9 +1057,9 @@
|
||||
</div>
|
||||
</div>
|
||||
<ul>
|
||||
<li><strong>Audio</strong>: beat detection from a chosen input device (monitor sources follow playback).</li>
|
||||
<li><strong>Audio</strong>: beat detection from the controller's microphone. While it is running, its beats time sequences and go to the drivers; while it is stopped, a clock at the simulated BPM does.</li>
|
||||
<li>BPM and beat indicators appear in the header and Audio modal while detection is running.</li>
|
||||
<li>Adjust <strong>Volume</strong> (gain before detection); the level meter shows live input.</li>
|
||||
<li>The level meter shows the microphone's live input. <a href="/audio">/audio</a> has a full readout, a tap for beat 1 and a live listen.</li>
|
||||
<li><strong>Start</strong> / <strong>Stop</strong> detection; <strong>Reset detector</strong> clears stuck BPM tracking.</li>
|
||||
<li>Sync sequences to music with <kbd>S</kbd> on a downbeat while a sequence plays.</li>
|
||||
</ul>
|
||||
|
||||
Reference in new issue
Block a user