Proof Portal

Project overview

Omarchy

ProbeLabs65 findings · 95 requirements

A 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.

Inbox
ReportR-1430GitHub issuePublicDecided· Out of scope

ASUS ROG blanket software-mixer fix degrades audio quality on smart-amp laptops (e.g. G733ZW) — muddy sound out of the box

Reported by Orneyfish · filed Aug 26, 2026 · open at source

Decided: Out of scope — decided by agents · verified 4 days ago.

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?
AreaOutside the audited area· Decided by agents · verified
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?
Decided by agents and verified by a second, independent agent — see the decision.

Original report

ASUS ROG blanket software-mixer fix degrades audio quality on smart-amp laptops (e.g. G733ZW) — muddy sound out of the boxrevision 1 · captured 2026-09-28 21:24 UTC via poll

System details

ASUS ROG Strix G733ZW, Omarchy base install (audio hardware fixup handled by install/user/hardware/asus/fix-audio-mixer.sh).

What's wrong

Out of the box, audio on this machine was completely muddy — enough that I ended up having to build a manual PipeWire + EasyEffects setup (custom EQ, compressor, etc.) just to get it to a usable baseline, and even after all that manual tuning it's still not on par with a stock Windows install on the same hardware. This is a rough first-audio-experience for a "quick install and go" desktop.

Looking at the install script that runs for any ASUS ROG machine:

# install/user/hardware/asus/fix-audio-mixer.sh
if omarchy-hw-asus-rog; then
  mkdir -p ~/.config/wireplumber/wireplumber.conf.d/
  cp "$OMARCHY_PATH/default/wireplumber/wireplumber.conf.d/alsa-soft-mixer.conf" ~/.config/wireplumber/wireplumber.conf.d/
  rm -rf ~/.local/state/wireplumber/default-routes

  card=$(aplay -l 2>/dev/null | grep -i "ALC285" | head -1 | sed 's/card \([0-9]*\).*/\1/')
  if [[ -n $card ]]; then
    amixer -c "$card" set Master 80% unmute 2>/dev/null
  fi
fi

and the config it installs:

# default/wireplumber/wireplumber.conf.d/alsa-soft-mixer.conf
monitor.alsa.rules = [
  {
    matches = [ { device.name = "~alsa_card.*" } ]
    actions = { update-props = { api.alsa.soft-mixer = true } }
  }
]

This applies api.alsa.soft-mixer = true to every ALSA card on any machine that matches omarchy-hw-asus-rog, unconditionally — it disables the hardware mixer path entirely in favor of a software volume control, on the theory that it works around Realtek hardware-mixer quirks (per the comment, and per #7458 which covers the ALC285-only unmute logic being too narrow).

The G733ZW isn't a plain Realtek-codec laptop — it has dedicated smart-amp speaker hardware that normally relies on the hardware/firmware audio path for amp protection and frequency shaping. Forcing every card on every ROG model onto a blanket software mixer, with no per-model or per-amp distinction, plausibly explains why the out-of-box sound here was muddy: the fix designed to work around a Realtek quirk on some models is applied indiscriminately and may be actively working against the audio hardware on models with their own smart amp.

Suggested enhancement

  • Scope fix-audio-mixer.sh / alsa-soft-mixer.conf to the specific codecs/models it's actually meant to fix, rather than every omarchy-hw-asus-rog match (same gap #7458 flags for the unmute logic, but it affects the mixer-mode config too).
  • For models with dedicated smart-amp speaker hardware (G733ZW and similar), consider not applying the soft-mixer override at all, or shipping a tuned default profile/EQ instead of leaving users to reconstruct one from scratch via PipeWire + EasyEffects to reach basic listenable quality.
View raw text
### System details

ASUS ROG Strix G733ZW, Omarchy base install (audio hardware fixup handled by `install/user/hardware/asus/fix-audio-mixer.sh`).

### What's wrong

Out of the box, audio on this machine was completely muddy — enough that I ended up having to build a manual PipeWire + EasyEffects setup (custom EQ, compressor, etc.) just to get it to a usable baseline, and even after all that manual tuning it's still not on par with a stock Windows install on the same hardware. This is a rough first-audio-experience for a "quick install and go" desktop.

Looking at the install script that runs for any ASUS ROG machine:

```sh
# install/user/hardware/asus/fix-audio-mixer.sh
if omarchy-hw-asus-rog; then
  mkdir -p ~/.config/wireplumber/wireplumber.conf.d/
  cp "$OMARCHY_PATH/default/wireplumber/wireplumber.conf.d/alsa-soft-mixer.conf" ~/.config/wireplumber/wireplumber.conf.d/
  rm -rf ~/.local/state/wireplumber/default-routes

  card=$(aplay -l 2>/dev/null | grep -i "ALC285" | head -1 | sed 's/card \([0-9]*\).*/\1/')
  if [[ -n $card ]]; then
    amixer -c "$card" set Master 80% unmute 2>/dev/null
  fi
fi
```

and the config it installs:

```
# default/wireplumber/wireplumber.conf.d/alsa-soft-mixer.conf
monitor.alsa.rules = [
  {
    matches = [ { device.name = "~alsa_card.*" } ]
    actions = { update-props = { api.alsa.soft-mixer = true } }
  }
]
```

This applies `api.alsa.soft-mixer = true` to **every** ALSA card on **any** machine that matches `omarchy-hw-asus-rog`, unconditionally — it disables the hardware mixer path entirely in favor of a software volume control, on the theory that it works around Realtek hardware-mixer quirks (per the comment, and per #7458 which covers the ALC285-only unmute logic being too narrow).

The G733ZW isn't a plain Realtek-codec laptop — it has dedicated smart-amp speaker hardware that normally relies on the hardware/firmware audio path for amp protection and frequency shaping. Forcing every card on every ROG model onto a blanket software mixer, with no per-model or per-amp distinction, plausibly explains why the out-of-box sound here was muddy: the fix designed to work around a Realtek quirk on some models is applied indiscriminately and may be actively working against the audio hardware on models with their own smart amp.

### Suggested enhancement

- Scope `fix-audio-mixer.sh` / `alsa-soft-mixer.conf` to the specific codecs/models it's actually meant to fix, rather than every `omarchy-hw-asus-rog` match (same gap #7458 flags for the unmute logic, but it affects the mixer-mode config too).
- For models with dedicated smart-amp speaker hardware (G733ZW and similar), consider not applying the soft-mixer override at all, or shipping a tuned default profile/EQ instead of leaving users to reconstruct one from scratch via PipeWire + EasyEffects to reach basic listenable quality.

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.

  • Out of scopeDecided by agents · verified · 2026-10-09 09:18 UTC