Proof Portal
Omarchy
ProbeLabs65 findings · 95 requirementsA proof layer — requirements, tests and verified fixes — for two of Omarchy's subsystems: the application menu (launcher scripts, QML model, JSONC config, search and selection) and the lock screen (lock scripts, QML, PAM authentication). Scope is deliberately limited to those components of omacom/omarchy; the rest of the distribution is not covered.
[Quattro/Apple Silicon] Audio tuning command misreports active Asahi J316 DSP as unsupported
Reported by SurreptitiousFabric · filed Aug 23, 2026Closed upstream on 2026-10-08 by the bot omarchybot, as not planned.
At a glance
- 1 · What is claimed?
- Only the report text below — no validator has restated it as checkable claims yet.
- 2 · What does it affect?
- Not yet mapped to any requirement or component.
- 3 · Is it reproducible?
- No validation has been run yet.
- 4 · What remains unclear?
- Not validated yet: no claims, no reproducer.
- 5 · What happens next?
- Our staff decide whether the report is valid. Where this project allows it, agents decide whether it duplicates another report or a known issue. No decision has been recorded yet.
Original report
System details
- Hardware: Apple MacBook Pro (16-inch, M1 Max, 2021)
- Device tree compatible:
apple,j316c,apple,t6001 - Omarchy:
4.0.0.r6589.gdec29fa-1(4.0.0-mac.11commit) - Kernel:
7.1.6-1-1-ARCH(Asahi) asahi-audio:3.4-1alsa-ucm-conf-asahi:8-1
What happens
The Omarchy speaker-tuning status reports that no supported tuning ships for this laptop:
$ omarchy audio tuning status
Installed: no
Host service: inactive (disabled)
Tuning sink: absent
Default sink: audio_effect.j316-convolver
Matches: nothing ships for this laptopThat message is misleading on Asahi systems. The correct model-specific Asahi J316 DSP is already installed and active. The live PipeWire graph contains:
audio_effect.j316-convolver
effect_output.j316-convolverThe profile and model-specific impulse responses are present under:
/usr/share/asahi-audio/j316/graph.json
/usr/share/asahi-audio/j316/tweeters-*.wav
/usr/share/asahi-audio/j316/woofers-*.wavThe default sink is correctly set to audio_effect.j316-convolver.
Cause
omarchy-audio-tuning searches only $OMARCHY_PATH/default/audio/tunings, which currently contains Omarchy supplemental profiles such as the Dell XPS tuning. It does not distinguish “no Omarchy supplemental tuning” from “this laptop has no supported tuning,” nor detect the existing Asahi DSP path.
This is especially confusing during first run because install/user/first-run/audio-tuning.sh invokes omarchy-audio-tuning on. It can imply that Apple speakers lack a supported profile even though Asahi has already loaded the correct one.
Expected behavior
On Apple Silicon/Asahi systems with an active audio_effect.*-convolver profile, Omarchy should either:
- report that speaker tuning is managed by Asahi, or
- silently skip the supplemental Omarchy tuning flow.
It should not encourage adding or forcing another filter on top of Asahi audio, since the Asahi DSP path is model-specific and participates in safe speaker operation.
Reproduction
- Install the Quattro Apple Silicon build on a supported MacBook.
- Confirm
pactl get-default-sinkreturnsaudio_effect.j316-convolver. - Run
omarchy audio tuning status. - Observe
Matches: nothing ships for this laptop.
View raw text
## System details - Hardware: Apple MacBook Pro (16-inch, M1 Max, 2021) - Device tree compatible: `apple,j316c`, `apple,t6001` - Omarchy: `4.0.0.r6589.gdec29fa-1` (`4.0.0-mac.11` commit) - Kernel: `7.1.6-1-1-ARCH` (Asahi) - `asahi-audio`: `3.4-1` - `alsa-ucm-conf-asahi`: `8-1` ## What happens The Omarchy speaker-tuning status reports that no supported tuning ships for this laptop: ```text $ omarchy audio tuning status Installed: no Host service: inactive (disabled) Tuning sink: absent Default sink: audio_effect.j316-convolver Matches: nothing ships for this laptop ``` That message is misleading on Asahi systems. The correct model-specific Asahi J316 DSP is already installed and active. The live PipeWire graph contains: ```text audio_effect.j316-convolver effect_output.j316-convolver ``` The profile and model-specific impulse responses are present under: ```text /usr/share/asahi-audio/j316/graph.json /usr/share/asahi-audio/j316/tweeters-*.wav /usr/share/asahi-audio/j316/woofers-*.wav ``` The default sink is correctly set to `audio_effect.j316-convolver`. ## Cause `omarchy-audio-tuning` searches only `$OMARCHY_PATH/default/audio/tunings`, which currently contains Omarchy supplemental profiles such as the Dell XPS tuning. It does not distinguish “no Omarchy supplemental tuning” from “this laptop has no supported tuning,” nor detect the existing Asahi DSP path. This is especially confusing during first run because `install/user/first-run/audio-tuning.sh` invokes `omarchy-audio-tuning on`. It can imply that Apple speakers lack a supported profile even though Asahi has already loaded the correct one. ## Expected behavior On Apple Silicon/Asahi systems with an active `audio_effect.*-convolver` profile, Omarchy should either: 1. report that speaker tuning is managed by Asahi, or 2. silently skip the supplemental Omarchy tuning flow. It should not encourage adding or forcing another filter on top of Asahi audio, since the Asahi DSP path is model-specific and participates in safe speaker operation. ## Reproduction 1. Install the Quattro Apple Silicon build on a supported MacBook. 2. Confirm `pactl get-default-sink` returns `audio_effect.j316-convolver`. 3. Run `omarchy audio tuning status`. 4. Observe `Matches: nothing ships for this laptop`.
Validation
Not checked yet. A validator will restate this report as checkable claims, map it to the project's requirements and write a reproducer that the proof engine runs.
Linked
Not linked to any known issue, other report or change yet.
Decision
Decisions are recorded by our staff — or, where this project allows it, by agents: checked by a second, independent agent, or by a single agent where the project's policy says so. Any decision reached so far is shown below.
No decision has been recorded yet.