why won't pipewire detect any devices while alsa works fine?

apparently I didn’t have eudev, setup-devd udev fixed it but for some reason sound quality using pipewire is horrible (while alsa is fine)

@noisytoot horrible in what way? choppy? low sample rate? buzzing?

@noisytoot (ive experienced all of these with pipewire at least once)

@kemona_halftau low sample rate I think, but I'm not sure it's actually a pipewire issue or more a "I had to unplug and replug my headphones to get pipewire to detect them and didn't plug them in properly" issue because it also occurs with alsa after this and after unplugging and replugging them a few more times it doesn't consistently happen

@noisytoot i had a laptop on-board sound card which defaulted its sample rate to 4khz for some reason, and its resampler added high-frequency artifacts to the audio signal (like a chiptune bitcrush effect almost, like the sound is coming from a shrill cheap toy speaker, specifically a wii remote speaker)
pulseaudio handled it fine (using 48khz for playback and recording) but pipewire would alternate between 4khz and 44.1khz depending on if the microphone or line-in was last used and seemingly at random if neither was used

@noisytoot i also remember my startup sound being played through aplay (which should use alsa directly, since pipewire/pulseaudio wouldnt have started yet) and it would always consistently use 4khz with no way of setting the sample rate to any other setting without muting all sound until pipewire started

@kemona_halftau the only issue I have had with pipewire previously is that headphone jack detection was broken in the coreboot ports for various skylake/kabylake thinkpads (in my case T480s, but they were all affected, they're very similar) and pulseaudio would still allow manually switching to it while pipewire wouldn't (that bug is now fixed in coreboot so I switched to pipewire on that laptop, but on my main laptop I still use pulseaudio)