FIR DSP 408: own memory layout and FIR tab (filters, coefficient files, tap budget)

Layout and commands derived from the behaviour of its control software, tested
against the simulator only. No GEQ on this model; dynamic EQs are left untouched.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
GivouandClaude Opus 5.5 committed 2026-11-02 17:11:46 +01:00
1 parent f7d5e22bb0
commit 5597fae3f3
13 files changed
+622 -35

No files matched your search

+9 -4
View File
@@ -47,6 +47,9 @@ pi_writer.py → pi_image.py (cloud-init SD card, installs server.py as a system
until it is below the limit again. The client mirrors this in `gainCap` (faders, sliders, `setParam`).
* **Link group names** – `Device.linknames` (app-side, like the colours), keyed by kind and members (`"out:0,1"`), so a
changed group starts without a name. The mixer draws them as brackets in row 1 of the `.strips` grid (`linkBands`).
* **FIR tab** (`viewFir`, only `d.fir`) – outputs: `0x4B` type/window/cut-offs/taps index, the DSP calculates the filter;
the curve is the app's own windowed sinc. Files: `Device.upload_fir` (`0x5B` name, `0x4E` packets of 12 floats). The DSP
can't send coefficients back, so the curve of a file only exists in the session (`S.firCoef`).
* **Network search** – `App.scan_network` probes the local /24 networks on TCP 9761 (handshake + device info),
skipping DSPs this app is connected to.
* **Copy settings / mute all** – `App.copy_settings` (`POST /api/copy`, groups level/filters/eq/dynamics/routing) and
@@ -109,10 +112,12 @@ and the DSP's own mirroring inside groups, limiter-active bit mask, preset impor
Not verified yet – ask for a log (`python server.py -v`) from real hardware before changing protocol code here:
* **Beta models** `206` and `408fir` – never seen on real hardware, same protocol and memory layout are only assumed
(also the USB ID). Never auto-detected (`detect_model`, a FIR device must not pass as a 408); the only hint is the
note in the add-device form, afterwards they work like the others. The FIR filters are deliberately not implemented;
ask testers for a preset export (it holds the raw image) and a log first.
* **Beta models** `206` and `408fir` – never seen on real hardware. Never auto-detected (`detect_model`, a FIR device
must not pass as a 408); the only hint is the note in the add-device form, afterwards they work like the others.
`206`: same protocol and layout as the 204/408 are only assumed (no control software looked at), also the USB ID.
`408fir`: own layout and commands derived from its control software (`Model.fir`, `_parse_fir`, `_fir_command`), simulator
only. Not done: dynamic EQs (kept untouched), saving coefficients into a preset slot of the DSP (`0x5A`, format
not worked out), where it keeps the test signal (the app remembers it). Ask testers for a preset export and a log.
* **DSP 408 on real hardware** (layout and frames match published captures, limiter bits for Out 5–8 assumed)
* USB on Windows and Linux against a real DSP (only tested against a fake HID device)
* Where the PEQ bypass flag lives in the memory image; format of the set-command acknowledgement; where the number