Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

4
  • FYR wiki.archlinux.org/title/…. Most likely you are using wireplumber. I have no idea about the relationship between audio.rate in a session manager update-props rule and default.clock.rate / default.clock.allowed-rates in the pipewire context.properties though. Commented Sep 7 at 17:54
  • (I don't think they would be like two layers of "resampling (target)", but somehow you claimed that The DAC is displaying a sample rate of 48 kHz even when pw-top reports S16LE 2 192000 alsa_output.usb-Generic_USB_Audio-00.HiFi__SPDIF__sink. See if this helps getting you some hints or answers.) Commented Sep 7 at 17:57
  • Tom, thanks for the url. Gives me something to read. BTW: the bit rate is not resampled. Somehow the output format seems to changed from S24_32 to S16LE. Commented Sep 8 at 12:20
  • What I meant is, unless it is a hardware (or driver compatibility) problem, 192000 ... alsa_output.usb-Generic_USB_Audio-00.HiFi__SPDIF__sink shown in pw-top should be reporting what your USB sound card receive / was open at, but I don't how exactly pipewire works (with this "session manager" thing), I don't know what those two sample rate configurations mean / would do respectively. As for the sample format, it is not surprised that the samples got truncated to 16bit because it is quite expected it would be the default in configuration. Commented Sep 8 at 14:06