On 1/9/25 11:07 AM, dep via tde-users wrote:
Trying various settings in pavucontrol I found a place where it was seemingly forcing HDMI. I disabled that, apparently, because instantly I had sound. Oh, and nuked pipewire and all its near relatives and close friends.
Just a slight aside. While I very much embrace your 25 year model and bleeding edge, I have had a very different experience with pipewire. Arch moved to pipewire several years ago, and I was skeptical of the new sound approach. However, my experience with it since on Arch and openSUSE (Tumbleweed) and PiOS has been painless and quite pleasant. Whether it is normal sound, or streaming audio with mplayer from the command-line over a remote connected machine to speakers -- it has simply worked.
The unpleasant part (and this is true for pulseaudio, generally), the sound setup is enabled as a user-service (at least by systemd). This means that the sound system isn't enable completely at boot, but relies on user-login and systemd magic to make all the source/sink connections. While I can appreciate the design from a multi-user standpoint, it is a PITA if you just want to use a box as a sound server without a user having to login.
So "don't throw the baby out with the bathwater." There may be OS difficulties in arriving at that "perfect user-service systemd setup voodoo", but when it works, it works quite well.
Glad you got your sound working, and pulseaudio alone will work quite well too. However, with a slight view of what the future holds, it may be worth making friends with pipewire too :)
-- David C. Rankin, J.D.,P.E.
Attachment:
OpenPGP_signature.asc
Description: OpenPGP digital signature
____________________________________________________ tde-users mailing list -- users@xxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxx Web mail archive available at https://mail.trinitydesktop.org/mailman3/hyperkitty/list/users@xxxxxxxxxxxxxxxxxx
