Arch Linux

withgoody7

Member

Registered: 2018-10-31

Posts: 17

[SOLVED] How we know pipewire is running or not

Just in recent I started pipewire and I installed all packages related pipewire running.  I just wanted to know how we know the system is running under
pipewire or not. 

[root@kagechio yt2]#  ps -e | grep pipewire
    554 ?        00:00:19 pipewire
    556 ?        00:00:02 pipewire-pulse
[root@kagechio yt2]#

alternative choice, i can find how the system is  working by installing patchege ?

pipewire system uses resolving latency by playback function, is it wrong for understanding the nature of pipewire system?

Thanks for giving me the tech info. 

I appreciate.

Last edited by withgoody7 (2022-05-14 17:55:52)

Lone_Wolf

Administrator

From: Netherlands, Europe

Registered: 2005-10-04

Posts: 13,281

Re: [SOLVED] How we know pipewire is running or not

Pipewire uses systemd/User for management of the server and automatic socket activation.

automatic socket activation means systemd will start pipewire whenever an apllication requires it.
Check https://wiki.archlinux.org/title/Systemd/User for more info.

---

Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.

clean chroot building not flexible enough ?
Try clean chroot manager by graysky

withgoody9

Member

Registered: 2022-01-30

Posts: 1

Re: [SOLVED] How we know pipewire is running or not

Thanks for your replying

withgoody7

Member

Registered: 2018-10-31

Posts: 17

Re: [SOLVED] How we know pipewire is running or not

further my analysis, there are two ways to go through the data as 'pipe wire',  1) pipe wire plugin installed packages, gui settings, such as vlc,  audacious, smplayer, audacity  vmpk  2) alsa-pipe wire packages only....parole... mpv  firefox, chromium... , over all, latency to be resolved by 'play back'..

withgoody7

Member

Registered: 2018-10-31

Posts: 17

Re: [SOLVED] How we know pipewire is running or not

except debian. debian works with pipewire-pulse, I added and it's really Solved... thanks.

Last edited by withgoody7 (2022-03-27 10:24:48)

V1del

Forum Moderator

Registered: 2012-10-16

Posts: 23,940

Re: [SOLVED] How we know pipewire is running or not

This has nothing to do with debian but depends on the applications you are running. If an application only/primarily has a pulse backend then you need pipewire-pulse to provide the pulseaudio API.

kokoko3k

Member

Registered: 2008-11-14

Posts: 2,426

Re: [SOLVED] How we know pipewire is running or not

Just try pw-top

---

Help me to improve ssh-rdp !
Retroarch User? Try my koko-aio shader !

withgoody7

Member

Registered: 2018-10-31

Posts: 17

Re: [SOLVED] How we know pipewire is running or not

there is a useful command I found. 

$ pactl    info

in my case,
[yt2@kagechio ~]$ pactl info
Server String: /run/user/1000/pulse/native
Library Protocol Version: 35
Server Protocol Version: 35
Is Local: yes
Client Index: 282
Tile Size: 65472
User Name: yt2
Host Name: kagechio
Server Name: PulseAudio (on PipeWire 0.3.50)
Server Version: 15.0.0
Default Sample Specification: float32le 2ch 48000Hz
Default Channel Map: front-left,front-right
Default Sink: alsa_output.pci-0000_00_1b.0.analog-stereo
Default Source: alsa_output.pci-0000_00_1b.0.analog-stereo.monitor
Cookie: 6d4e:b8a6

Last edited by withgoody7 (2022-04-27 03:51:32)

withgoody7

Member

Registered: 2018-10-31

Posts: 17

Re: [SOLVED] How we know pipewire is running or not

it's very difficult process for me to understand. I am now using pipewire: ALSA-pipewire instead of Jack control kit for all applications. I can see the latency  resolving via playback...:)

Last edited by withgoody7 (2022-05-14 17:56:19)

withgoody7

Member

Registered: 2018-10-31

Posts: 17

Re: [SOLVED] How we know pipewire is running or not

$ pactl list sinks
$ pw-cli list-objects Device