|
|
43 minūtes atpakaļ | |
|---|---|---|
| config | 43 minūtes atpakaļ | |
| scripts | 1 stundu atpakaļ | |
| tests | 43 minūtes atpakaļ | |
| .gitignore | 43 minūtes atpakaļ | |
| README.md | 43 minūtes atpakaļ |
Rigforge is a standalone Raspberry Pi audio pedalboard. The desired routing is described in config/desired-state.yaml. Hardware-specific ports and operational settings remain provisional until tested on the target.
The current target reports Debian GNU/Linux 13.7, AArch64, and a Behringer UMC404HD 192k. ALSA advertises four capture and four playback channels. PipeWire 1.4.2 and WirePlumber are active in the logged-in jojo user session, with Linger=no.
PipeWire exposed four capture channels named capture_AUX0 through capture_AUX3 and four playback channels named playback_AUX0 through playback_AUX3. A four-channel 48 kHz recording was completed, with the guitar on physical input 1 appearing on capture_AUX0 and the microphone on physical input 3 appearing on capture_AUX2; the other channels were at noise floor during that test. A temporary PipeWire link from capture_AUX0 to playback_AUX0 produced audible guitar. The target owner reports that playback_AUX0 feeds output 1L and that Main Out L receives 1L with MIX set to PB and MONITOR set to A. The owner then added capture_AUX2 and confirmed hearing both guitar and microphone with a 128-frame quantum at 48 kHz; this is an initial successful low-latency listening test, not yet a sustained dropout or headroom measurement. Monitoring duplication, clipping headroom under summed sources and loop returns, and MIDI/OSC behavior have not yet been tested.
The target has aconnect, amidi, and oscsend; ALSA lists the UMC404HD MIDI port. This does not yet verify FCB1010 messages or SooperLooper OSC availability. amixer -D hw:2 scontents showed capture and playback controls at 0 dB; no mixer settings have been changed.
Before collecting the target observations, the following commands were run on the current Raspberry Pi OS Lite installation:
sudo apt update
sudo apt upgrade
sudo apt install --no-install-recommends \\
rtkit pipewire pipewire-jack wireplumber \\
libspa-0.2-modules liblo-tools git
This records the preparation already performed on rigforge and is a starting point for documenting a second Pi. It is not yet a verified, version-pinned rebuild procedure: package versions, additional runtime dependencies, audio configuration, and service setup still need to be confirmed before reusing it as a complete deployment recipe.
config/desired-state.yaml: versioned desired audio topology and provisional target mapping.config/pipewire/filter-chain.conf.d/rigforge-direct-mix.conf: candidate four-channel input to mono direct mixer; not yet installed or run on the target.config/sooperlooper/fcb1010.slb: supplied FCB1010 binding file, pending on-target verification.build/sooperlooper/: reserved for the later ARM64 Docker build definition.scripts/validate_desired_state.py: validates topology and routing invariants without changing the target.scripts/observe_pipewire.py: read-only comparison for explicitly declared UMC AUX ports and links.tests/: unit tests for desired-state validation and the PipeWire observer.artifacts/sooperlooper/arm64/: reserved for an artifact and its provenance, subject to repository hosting limits and redistribution terms.The YAML describes desired state; a control surface is not a second source of truth. The initial audio profile declares 48 kHz and a quantum of 128 frames, which was reported to sound good during a temporary target test. At 48 kHz, 128 frames is about 2.7 ms per period, not the end-to-end latency. This runtime value has not yet been made persistent or measured under sustained load; apply it temporarily on the target with pw-metadata -n settings 0 clock.force-quantum 128 and return to automatic selection with pw-metadata -n settings 0 clock.force-quantum 0. Concrete PipeWire ports, buffer settings, package names, services, and artifact installation path will only be recorded as verified after target tests.
Validate the desired-state file on the development PC with:
python3 scripts/validate_desired_state.py
python3 -m unittest discover -s tests -v
The validator checks that there are four distinct physical inputs, one four-channel looper with each source assigned once, a declared mix output, and no active or planned route from looper returns back to looper inputs. It is read-only and does not connect audio ports or modify the target.
For an initial read-only graph observation on a system with pw-link, run:
python3 scripts/observe_pipewire.py
The observer reads pw-link -l and compares only connections whose endpoints are explicitly listed under routing.managed_ports; expected edges go in routing.managed_links. Both lists are empty at this stage, so it intentionally reports no project mismatches. The existing WirePlumber links between UMC AUX ports and their split monitor ports are not classified as project-managed. Only concrete UMC ALSA AUX port names are accepted; logical nodes such as direct_mix are rejected until an actual PipeWire node/port exists. The observer only prints missing or unexpected link proposals; it never creates or deletes links. No polling or automatic repair is enabled in this increment.
config/pipewire/filter-chain.conf.d/rigforge-direct-mix.conf defines a PipeWire builtin mixer with four mono inputs, a single mono output, and a conservative initial gain of 0.2 per input. It is a candidate config for a two-input listening test using capture_AUX0 and capture_AUX2; it is not installed, loaded, or claimed to be syntactically validated by PipeWire yet. Inputs 2 and 4 are provisioned for later checks, not confirmed by instrument tests.
The installed PipeWire example explicitly documents loading fragments from ~/.config/pipewire/filter-chain.conf.d/ with pipewire -c filter-chain.conf, which is the command used by the current user service. After this candidate is available in the target checkout, it can be tested as a reversible user-level fragment, without editing /etc or the packaged config:
target="$HOME/.config/pipewire/filter-chain.conf.d/rigforge-direct-mix.conf"
backup="$target.before-rigforge-test"
mkdir -p "$(dirname "$target")"
if test -e "$target"; then
cp -a "$target" "$backup"
fi
install -m 0644 config/pipewire/filter-chain.conf.d/rigforge-direct-mix.conf "$target"
systemctl --user restart filter-chain.service
Then confirm filter-chain.service is active, inspect pw-cli ls Node, pw-link -o, and pw-link -i, and stop if the two project nodes do not appear or the service reports an error. Do not infer the new port names: use the exact names printed by PipeWire. At low monitor volume, connect only the physical capture ports for inputs 1 and 3 to the matching mixer inputs, and the mixer output to playback_AUX0; listen for guitar and microphone, then remove these test links with pw-link -d using the exact observed endpoint names. Existing WirePlumber hardware links must be left alone.
Rollback the fragment and reload the filter service after the test:
if test -e "$backup"; then
mv "$backup" "$target"
else
rm -f "$target"
fi
systemctl --user restart filter-chain.service
This restarts only filter-chain.service, not the main PipeWire daemon; it has not yet been exercised with this project fragment. If activation or sound behaves unexpectedly, first remove the test links, perform the rollback, verify the filter service is active, and do not repeatedly restart it. The repository tests check channel/gain declarations, not PipeWire's native config parser or target runtime behavior.
The development host is Ubuntu AMD64 with Docker. The SooperLooper source under evaluation is https://github.com/abarker/sooperlooper-mods. The Docker build procedure is intentionally not yet provided: first select a tag and inspect that tag's build instructions and licensing. The eventual build command must take an explicit tag, resolve and record its exact commit, build for ARM64, and record artifact architecture, runtime dependencies, provenance, and checksum. The container is for building only; SooperLooper will run natively on the Raspberry Pi.
No SooperLooper artifact or Dockerfile is included at this stage.
rigforge targetNo packages, artifacts, services, or permanent audio configuration have been installed or changed by this initial increment. A temporary direct PipeWire test linked capture_AUX0 and capture_AUX2 to playback_AUX0; guitar and microphone were heard together at 48 kHz / 128 frames. pw-top showed the active capture driver at 128 frames with ERR = 0 during the reported test. The temporary links have since been removed. This is an initial listening check, not a sustained load, dropout, or headroom test.
The next target checks are:
ERR = 0 observation was brief.Linger=no currently means the running audio session is associated with the active login; unattended startup is not established.discrete_prefader 0 separately.Do not treat planned packages, commands, ports, or service settings as target-validated until these checks have been performed.
Deployment is manual: inspect and test a change, then use git pull on rigforge only when the change is ready. No CI/CD or auto-pull is configured. Service installation, activation, logs, diagnostics, and rollback commands will be documented after their units and target paths have been tested. Keep the last known working revision available; do not apply unverified audio or service changes during live use.