Bring back Discord notification sounds that PipeWire swallows
The Arch wiki PipeWire/Troubleshooting 'No notification sounds from Discord' section gives exactly this rule (application.process.binary = "Discord", pulse.min.quantum = 1024/48000) and says the cause 'might' be min.quantum too low, advising more than 700. /usr/share/pipewire/pipewire-pulse.conf (pipewire 1.6.8) confirms the default pulse.min.quantum 256/48000 and the speech-dispatcher rule. pipewire.conf(5) confirms drop-in arrays are appended. omarchy-restart-audio exists. The defect is Omarchy-specific: Omarchy 4 does not install a native Discord. /usr/share/omarchy/applications/Discord.desktop runs omarchy-launch-webapp https://discord.com/channels/@me, which launches the default Chromium-family browser with --app, so on a stock Omarchy machine the rule matches nothing and the record's web-app caveat is the main case, not a footnote. Matching the browser binary instead raises the floor for every stream from that browser, which the record does not say. Arch's discord package (1:1.0.160 in extra) now installs only /usr/bin/discord plus an updater bootstrap, so the binary name of the downloaded client was not confirmed here and must be checked. The cause asserted a mechanism (stream over before the graph settles) that the wiki does not state. Not exercised.
Symptom
Discord voice and music play normally, but message and join notification sounds are missing or cut down to a click. Other apps' short sounds are fine.
Cause
Discord's notification sounds are very short streams played through pipewire-pulse. The Arch wiki reports that they can go missing when the minimum quantum is too low, and pipewire-pulse's default pulse.min.quantum is 256/48000 (5.3 ms). Raising it for Discord's client alone gives those streams a larger buffer without changing latency for anything else. The wiki recommends more than 700 frames, and the stock /usr/share/pipewire/pipewire-pulse.conf already uses the same per-client mechanism for speech-dispatcher. The wiki entry is about the native Discord client. Omarchy 4 ships Discord as a web app in the default Chromium-family browser, and whether the web app shows the same problem is not documented.
Fix
**1. Find which binary owns the Discord stream.** Run this while a notification sound plays:
pactl list sink-inputs | grep -E 'application.(name|process.binary)'
Omarchy 4: the Discord launcher in the app menu is a web app (omarchy-launch-webapp https://discord.com/channels/@me), so the binary is your browser, for example chromium. A rule on that name raises the minimum quantum for every stream from that browser, not only Discord. If you installed the native client (discord from extra), the binary is normally Discord.
Plain Arch: the native client from the discord package, binary normally Discord. Confirm with the command above.
**2. Add a client rule in a pipewire-pulse drop-in.** Drop-in array sections such as pulse.rules are appended to the stock list rather than replacing it, so the shipped Teams, Firefox and speech-dispatcher rules stay in force:
mkdir -p ~/.config/pipewire/pipewire-pulse.conf.d
# ~/.config/pipewire/pipewire-pulse.conf.d/60-discord-min-quantum.conf
pulse.rules = [
{
matches = [ { application.process.binary = "Discord" } ]
actions = {
update-props = {
pulse.min.quantum = 1024/48000
}
}
}
]
Replace Discord with the binary name from step 1 if it differs.
**3. Restart audio, then restart Discord or the browser.**
Omarchy 4:
omarchy restart audio
Plain Arch:
systemctl --user restart pipewire.service pipewire-pulse.service wireplumber.service
Verify
While a notification plays, pactl list sink-inputs | grep -A30 'application.process.binary = "Discord"' (or your browser's binary name) shows the stream, and the notification sounds play in full.