Hacker News Reader

Man, how much are distros + bad user config hurting user "Linux" reports.

Thank god for NixOS where (1) we do a decent job of base config and (2) user config errors are basically trivially identifiable.

1. Open `pulsemixer` to monitor pulse clients

2. `ssh localhost "pacat < /dev/urandom"`

Observe that pacat is showing as a pulse client. This stuff is really easy and should absolutely just work.

View on HN

I'm running nixos (22.05), and I can't run alsa clients to the pipewire alsa device on the remote machine over ssh without setting the "correct" environment variables (I have yet to identify them, so I use what I posted to clone the environment of an X program).

Did you reply to the wrong comment? This doesn't seem relevant to remote audio

Um, it's just an example? Does this somehow help?

1. (term1) `ssh remote pulsemixer`

2. (term2) `ssh remote "pacat </dev/urandom"`

Observe that (1) you can see a new client appear on the remote, and (2) audio will play from the default playback device on the remote (and you can trivially change that device with `pulsemixer`)

EDIT: for your speakers/ears-sake, I recommend turning down the default playback device before doing this.

Reply on news.ycombinator.com