mollusk/peerspeak
Public Access
1
0
Fork 0
Code Issues Pull Requests 3 Actions 1 Packages Projects Releases 10 Wiki Activity

notify: correct a measured claim about the aplay fallback

Browse Source 
The comment said aplay ignores PULSE_PROP/PIPEWIRE_PROPS. Measured:
it reaches the graph through PipeWire's ALSA plugin and carries both
carriers exactly like pw-play and paplay. Comment only.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
mollusk
2026-07-25 20:07:08 -04:00
co-authored by Claude Opus 5
parent bcf1343a55
commit d40385f85c
1 changed files with 3 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
src/notify.rs
+3 -1
View File
@@ -275,7 +275,9 @@ fn spawn_player(path: &Path) {
// Ownership tag (plan §5.1). A chime is short, but it is still our // Ownership tag (plan §5.1). A chime is short, but it is still our
// audio on the default sink, and an untagged one is an unowned root // audio on the default sink, and an untagged one is an unowned root
// the exclusion engine would have to reason about from scratch. // the exclusion engine would have to reason about from scratch.
// `aplay` talks to ALSA and ignores both variables; harmless. // Measured on this host: all three fallbacks tag correctly, `aplay`
// included — it reaches the graph through PipeWire's ALSA plugin,
// which honours `PIPEWIRE_PROPS` like any other client.
ownership::tag_child(&mut command, ownership::NOTIFICATION_ROLE); ownership::tag_child(&mut command, ownership::NOTIFICATION_ROLE);
let started = command.status(); let started = command.status();
// `status()` errors only if the player binary isn't present; on a real // `status()` errors only if the player binary isn't present; on a real