RE: news-2023-05-20-kde-pipewire-wayland

hunky · l33t Joined: 19 Nov 2003 Posts: 891 Location: Alaska

Perhaps this should be in multimedia.. but here we go.

I'm using a profile of desktop/plasma and straight alsa and X. I'm not opposed to change.. the latest news suggests (if I interpret correctly) that the new Gentoo standard is going to be Wayland and pipewire for rather than X and other sound systems.

In my make.conf USE I have -wayland and -pulseaudio. I assume I need to remove those USE flags to do an update ala emerge -1avUD @world. Then start logging into Wayland sessions rather than what I use now. As for the sound system, I will look thru the wiki. In the news referenced in the subject, it gives a link #2 which I get a 404 on (even when removing the period at the end of the link). I have yet to look thru the pipewire wiki.. but will do that when I axe my desktop sound system as it exists now.

So I guess the question is if all I need to do is remove those USE entries in my make.conf, and then update.. and then configure pipewire ala the wiki. Simple as that?

[edit]: oh, and I suppose remove the USE flag alsa in make.conf?

thanks, JD

thumper · Guru Joined: 06 Dec 2002 Posts: 544 Location: Venice FL

It seems fine to keep using X if you want to, periodically I log in to Wayland from SDDM to see how it's progressing, but last I checked it still had issues for me, so I'm still on X and working fine with the settings requested in the News item.

Now my question is the same as yours, is ALSA no longer needed?
And safe to remove?

Thanks,

George

hunky · l33t Joined: 19 Nov 2003 Posts: 891 Location: Alaska

asturm · Posted: Tue May 23, 2023 9:31 am Post subject:

Both PulseAudio and PipeWire sit on top of ALSA so no, you are not supposed to remove it. USE=alsa remains default enabled in desktop profile and plasma/gnome profiles inherit that.
_________________
backend.cpp:92:2: warning: #warning TODO - this error message is about as useful as a cooling unit in the arctic

hunky · l33t Joined: 19 Nov 2003 Posts: 891 Location: Alaska

Well I made the jump. Basically all I've done is the emerge update after removing the -wayland and -pulseaudio from my make.conf and adding sound-server to pipewire in package.use. I added a couple other USE flags as well.

I'm not using systemd.

Rebooted after a --depclean which just removed a couple python things and a zope-interface ??.. Music files played right off. But browser noises (youtube for example) did not work. Exploring on the sound icon in system tray.. there was applications listed and I just had to check the proper sound device.. choice between HDMI (wrong), focusrite interface (wrong), and analog (right). So without much more exploring it seems to work. (Still logged into X).

I haven't yet tried Ardour and what I used to use: jack. Haven't been needing it lately, but will have to make sure I get that working. I see there's some jack replacements.

Anyway.. so far, so good. /jd

dmpogo · Advocate Joined: 02 Sep 2004 Posts: 3198 Location: Canada

so what is the relation betwieen pipewire and pulseaudio ?

Anon-E-moose · Posted: Wed May 24, 2023 8:43 pm Post subject:

Pipewire is the new McP. :lol:

Pipewire will (in time) completely replace pulseaudio and jack, the server parts, it uses the libs underneath.

I wasn't using pulseaudio before I switched to pipewire, so I opted for wireplumber so I could still use alsa direct.
I haven't set either the pulseaudio flag or jack at least for now.
_________________
PRIME x570-pro, 3700x, 5.17 zen kernel
gcc 11.2.0/12.2.0, profile 17.1 amd64-no-multilib, openrc, wayland
copy of my local repo

dmpogo · Advocate Joined: 02 Sep 2004 Posts: 3198 Location: Canada

poe_1957 · Posted: Tue May 30, 2023 11:54 am Post subject: pipewire - Wayland -systemd

Is there any possibility to defer the change and have a full working system with an upgraded KDE but without Wayland and pipewire until pipewire can completely replace pulseaudio and Wayland can completly replace X ?
Secondly can Wayland retain the possibilities of X ? For example going from graphical desktop to a command prompt in several terminals ? I mean without closing Wayland and the possibility to have several terminals all open at once like X could do ?

For me if Wayland wants to replace X, it need to be stabile and run every application that X did.
Now when I upgrade packets I need to do it manually because it always want to install pipewire and Wayland. And I do not want to end up with an unusable system. And I do not like hybrid systems, they are too complicated.
The way we moved from RC to systemd was already a pain in the ass and took a long time. I do not want to be again in that street again.
_________________
Linuxpioneer
ALUG

asturm · Posted: Tue May 30, 2023 12:09 pm Post subject:

You did not read the news item?
_________________
backend.cpp:92:2: warning: #warning TODO - this error message is about as useful as a cooling unit in the arctic

stefan11111 · Guru Joined: 29 Jan 2023 Posts: 430 Location: Romania