Re: pipewire and wireplumber

[Barry]

> On 25 Mar 2022, at 18:58, R. G. Newbury  wrote:
>
> 
> > Date: Fri, 25 Mar 2022 01:02:01 -0700
>
> Samuel Sieb wrote
> > Subject: Re: pipewire and wireplumber
> > R. G. Newbury wrote:
> > > DJ Delorie  wrote
> > > > Geoffrey Leach  writes:
> > > > > Is there a 'Getting Started With pipewire' and/or wireplumber
> > > > > somewhere? Or should they 'just work' and I need to check my
> > > > > connections?
> > > >
> > > > As a non-gnome (and non-display-manager) user, I share these .xsession
> > > > snippets:
> > > >
> > > > # Required by pipewire, at least
> > > > export XDG_RUNTIME_DIR=$(mktemp -d/tmp/$(id -u)-runtime-dir.XXX)
> > > >
> > > > # Required by most things
> > > > eval `dbus-launch --sh-syntax --exit-with-session`
> > > >
> > > > pipewire &
> > > > pipewire-pulse &
> > > > (sleep 2 ; wireplumber & ) &
> > > >
> > > > There wasn't a pipewire-specific config; it uses the same ALSA backend
> > > > as pulseaudio used.
> > >
> > > If you don't mind answering, was it a Rhode Island Red cockerel or a hen
> > > which you sacrificed to learn these arcane secrets? And, full-moon at
> > > midnight, or dark of the moon? Or did this take moving up to a goat?
> > > Or are you a graduate of Hogwarts? Because I am quite sure that none of
> > > these snippets show up anywhere in the so-called documentation. Pure
> > > magic, just like any sufficiently advanced technology.
> > That's because they aren't necessary.  For any standard desktop all
> > those pieces are already setup for you.  Notice how he said
> > "non-display-manager user".  Those are only necessary if you don't have
> > a graphical login session.
>
> Non-display-manager user or not, those might be necessary even if you have a graphical login session. I installed the KDE spin of Fedora 35 on Monday. A bare metal install: I partitioned the sda drive and formatted it during the install.
> I had NO audio.

As another data point.

I just installed f35 KDE spin on a new pc and everything just worked.
I have no audio issues. I did not do any special config it just worked.

Barry
> And nothing I did allowed the system to even *find* any audio hardware. I played a fugue's worth of combinations and read everything I could find.
> Unfortunately, as noted in this thread, there is no install guide. It just works - NOT. I saw an error message about XDG_RUNTIME_DIR and spent most of an evening down that rabbit-hole, but nothing worked. Pipewire would not even find a module which its own rpm had installed. In the end, I basically inverted the lines of the install process script I was playing with, and re-installed pulseaudio.
>
> Audio works fine now. My opinion of pipewire is, that like pulseaudio and systemd were, it has been released far too early in its beta stages. It took a couple of years for each of pulseaudio and systemd to reach adequate levels of instalability and reliability. Likely the same for pipewire.
>
> Geoff
> _______________________________________________
> users mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]
> Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: https://lists.fedoraproject.org/archives/list/[e-mail]
> Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure