Puppy Linux Discussion Forum

@rockedge you can probably just look at this post...

Not to overwhelm, but I thought "What would run as pulseaudio native? So I fired up pavucontrol: It's running on pipewre-pulse also. If this output is to be trusted. I think it is. Or are you guys playing tricks on pipewire and exporting pipewire-pulse to pipewire native?

So to sum up: all pulse apps are showing pipewire-pulse api, even appimages and run-as-spot apps, and pw-jack apps are showing "Jack" api. All are fully functional and showing up in Carla. Notice how Carla lumps all the pavucontrol ins/outs in one box, a lot easier to move than in qpwgraph and helvum (but the names don't show in Carla, so that sucks). Only thing missing here is midi-ports on hardware. Software midi-ports show up.

root# pw-cli ls Node
	id 30, type PipeWire:Interface:Node/3
 		object.serial = "30"
 		factory.id = "10"
 		priority.driver = "20000"
 		node.name = "Dummy-Driver"
	id 31, type PipeWire:Interface:Node/3
 		object.serial = "31"
 		factory.id = "10"
 		priority.driver = "19000"
 		node.name = "Freewheel-Driver"
	id 34, type PipeWire:Interface:Node/3
 		object.serial = "49"
 		object.path = "alsa:pcm:1:front:1:playback"
 		factory.id = "18"
 		client.id = "36"
 		device.id = "42"
 		priority.session = "1009"
 		priority.driver = "1009"
 		node.description = "Studio 24c Analog Stereo"
 		node.name = "alsa_output.usb-PreSonus_Studio_24c_SC1M20010587-00.analog-stereo"
 		node.nick = "Studio 24c"
 		media.class = "Audio/Sink"
	id 46, type PipeWire:Interface:Node/3
 		object.serial = "50"
 		object.path = "alsa:pcm:1:front:1:capture"
 		factory.id = "18"
 		client.id = "36"
 		device.id = "42"
 		priority.session = "2009"
 		priority.driver = "2009"
 		node.description = "Studio 24c Analog Stereo"
 		node.name = "alsa_input.usb-PreSonus_Studio_24c_SC1M20010587-00.analog-stereo"
 		node.nick = "Studio 24c"
 		media.class = "Audio/Source"
	id 47, type PipeWire:Interface:Node/3
 		object.serial = "47"
 		object.path = "alsa:pcm:2:front:2:playback"
 		factory.id = "18"
 		client.id = "36"
 		device.id = "41"
 		priority.session = "1009"
 		priority.driver = "1009"
 		node.description = "Built-in Audio Analog Stereo"
 		node.name = "alsa_output.pci-0000_00_1b.0.analog-stereo"
 		node.nick = "92HD90BXX Analog"
 		media.class = "Audio/Sink"
	id 48, type PipeWire:Interface:Node/3
 		object.serial = "48"
 		object.path = "alsa:pcm:2:front:2:capture"
 		factory.id = "18"
 		client.id = "36"
 		device.id = "41"
 		priority.session = "2009"
 		priority.driver = "2009"
 		node.description = "Built-in Audio Analog Stereo"
 		node.name = "alsa_input.pci-0000_00_1b.0.analog-stereo"
 		node.nick = "92HD90BXX Analog"
 		media.class = "Audio/Source"
	id 60, type PipeWire:Interface:Node/3
 		object.serial = "66"
 		client.id = "59"
 		client.api = "jack"
 		node.description = "Carla"
 		node.name = "Carla"
 		media.type = "Audio"
 		media.category = "Duplex"
 		media.role = "DSP"
	id 62, type PipeWire:Interface:Node/3
 		object.serial = "79"
 		factory.id = "6"
 		client.id = "61"
 		client.api = "pipewire-pulse"
 		application.name = "LibreWolf"
 		node.name = "LibreWolf"
 		media.class = "Stream/Output/Audio"
	id 63, type PipeWire:Interface:Node/3
 		object.serial = "128"
 		factory.id = "6"
 		client.id = "68"
 		client.api = "pipewire-pulse"
 		application.name = "PulseAudio Volume Control"
 		node.name = "PulseAudio Volume Control"
 		media.class = "Stream/Input/Audio"
	id 64, type PipeWire:Interface:Node/3
 		object.serial = "129"
 		factory.id = "6"
 		client.id = "68"
 		client.api = "pipewire-pulse"
 		application.name = "PulseAudio Volume Control"
 		node.name = "PulseAudio Volume Control"
 		media.class = "Stream/Input/Audio"
	id 69, type PipeWire:Interface:Node/3
 		object.serial = "127"
 		factory.id = "6"
 		client.id = "68"
 		client.api = "pipewire-pulse"
 		application.name = "PulseAudio Volume Control"
 		node.name = "PulseAudio Volume Control"
 		media.class = "Stream/Input/Audio"
	id 71, type PipeWire:Interface:Node/3
 		object.serial = "130"
 		factory.id = "6"
 		client.id = "68"
 		client.api = "pipewire-pulse"
 		application.name = "PulseAudio Volume Control"
 		node.name = "PulseAudio Volume Control"
 		media.class = "Stream/Input/Audio"
	id 75, type PipeWire:Interface:Node/3
 		object.serial = "121"
 		factory.id = "6"
 		client.id = "74"
 		client.api = "pipewire-pulse"
 		application.name = "ALSA plug-in [mscore4portable]"
 		node.name = "ALSA plug-in [mscore4portable]"
 		media.class = "Stream/Output/Audio"
	id 95, type PipeWire:Interface:Node/3
 		object.serial = "147"
 		factory.id = "6"
 		client.id = "68"
 		client.api = "pipewire-pulse"
 		application.name = "PulseAudio Volume Control"
 		node.name = "PulseAudio Volume Control"
 		media.class = "Stream/Input/Audio"
	id 96, type PipeWire:Interface:Node/3
 		object.serial = "148"
 		factory.id = "6"
 		client.id = "68"
 		client.api = "pipewire-pulse"
 		application.name = "PulseAudio Volume Control"
 		node.name = "PulseAudio Volume Control"
 		media.class = "Stream/Input/Audio"
	id 118, type PipeWire:Interface:Node/3
 		object.serial = "171"
 		factory.id = "6"
 		client.id = "117"
 		client.api = "pipewire-pulse"
 		application.name = "Chromium"
 		node.name = "Chromium"
 		media.class = "Stream/Output/Audio"
	id 123, type PipeWire:Interface:Node/3
 		object.serial = "176"
 		factory.id = "6"
 		client.id = "68"
 		client.api = "pipewire-pulse"
 		application.name = "PulseAudio Volume Control"
 		node.name = "PulseAudio Volume Control"
 		media.class = "Stream/Input/Audio"
root# 

root# wpctl status
PipeWire 'pipewire-0' [1.0.1, spot@void-live, cookie:517297354]
 └─ Clients:
        33. pipewire                            [1.0.1, spot@void-live, pid:20600]
        35. WirePlumber                         [1.0.1, spot@void-live, pid:20599]
        36. WirePlumber [export]                [1.0.1, spot@void-live, pid:20599]
        58. xfce4-pulseaudio-plugin             [1.0.1, root@void-live, pid:20764]
        59. python3.12                          [1.0.1, root@void-live, pid:21732]
        61. LibreWolf                           [1.0.1, root@void-live, pid:21222]
        67. Chromium input                      [1.0.1, spot@void-live, pid:23097]
        68. PulseAudio Volume Control           [1.0.1, root@void-live, pid:23926]
        74. ALSA plug-in [mscore4portable]      [1.0.1, root@void-live, pid:23784]
       117. Chromium                            [1.0.1, spot@void-live, pid:23097]
       130. wpctl                               [1.0.1, root@void-live, pid:24665]

Audio
 ├─ Devices:
 │      40. GF106 High Definition Audio Controller [alsa]
 │      41. Built-in Audio                      [alsa]
 │      42. Studio 24c                          [alsa]
 │  

 ├─ Sinks:
 │      34. Studio 24c Analog Stereo            [vol: 0.40]
 │  *   47. Built-in Audio Analog Stereo        [vol: 0.50]
 │  

 ├─ Sink endpoints:
 │  

 ├─ Sources:
 │      46. Studio 24c Analog Stereo            [vol: 1.00]
 │  *   48. Built-in Audio Analog Stereo        [vol: 1.00]
 │  

 ├─ Source endpoints:
 │  

 └─ Streams:
        62. LibreWolf                                                   

             65. output_FR       > 92HD90BXX Analog:playback_FR	[init]
             66. output_FL       > 92HD90BXX Analog:playback_FL	[init]
        63. PulseAudio Volume Control                                   

             83. input_FL        < 92HD90BXX Analog:capture_FL	[active]
             84. monitor_FL     

             85. input_FR        < 92HD90BXX Analog:capture_FR	[active]
             86. monitor_FR     

        64. PulseAudio Volume Control                                   

             87. input_FL        < Studio 24c:monitor_FL	[active]
             88. monitor_FL     

             89. input_FR        < Studio 24c:monitor_FR	[active]
             90. monitor_FR     

        69. PulseAudio Volume Control                                   

             70. input_FL        < 92HD90BXX Analog:monitor_FL	[active]
             80. monitor_FL     

             81. input_FR        < 92HD90BXX Analog:monitor_FR	[active]
             82. monitor_FR     

        71. PulseAudio Volume Control                                   

             91. input_FL        < Studio 24c:capture_FL	[active]
             92. monitor_FL     

             93. input_FR        < Studio 24c:capture_FR	[active]
             94. monitor_FR     

        75. ALSA plug-in [mscore4portable]                              

             78. output_FR       > 92HD90BXX Analog:playback_FR	[active]
             79. output_FL       > 92HD90BXX Analog:playback_FL	[active]
        95. PulseAudio Volume Control                                   

            105. input_FL        < LibreWolf:output_FL	[init]
            106. monitor_FL     

            107. input_FR        < LibreWolf:output_FR	[init]
            108. monitor_FR     

        96. PulseAudio Volume Control                                   

            109. input_FL        < ALSA plug-in [mscore4portable]:output_FL	[active]
            110. monitor_FL     

            111. input_FR        < ALSA plug-in [mscore4portable]:output_FR	[active]
            112. monitor_FR     

       118. Chromium                                                    

            119. output_FL       > 92HD90BXX Analog:playback_FL	[active]
            120. output_FR       > 92HD90BXX Analog:playback_FR	[active]
       123. PulseAudio Volume Control                                   

            124. input_FL        < Chromium:output_FL	[active]
            125. monitor_FL     

            126. input_FR        < Chromium:output_FR	[active]
            127. monitor_FR     

Video
 ├─ Devices:
 │  

 ├─ Sinks:
 │  

 ├─ Sink endpoints:
 │  

 ├─ Sources:
 │  

 ├─ Source endpoints:
 │  

 └─ Streams:

Settings
 └─ Default Configured Node Names:
root# 

I shut off pavucontrol to clean up the helvum graph and inserted a plugin into carla to show that midi inputs on software do show up:

@rockedge @geo_c
Don't know it's part of the problems with audio, but I noticed that in KLV-Airedale sr8 (latest I think) that /home/spot is owned by weedog.
Anyway for me e.g. run-as-spot <some-browser> doesn't work (error).
Fixed by doing chown -R spot:spot /home/spot (and run-as-spot works OK again)

Notice that it is using depreciated pipewire-media-session

It's deprecated, yes, but wireplumber is installed, so not using it.

The pipewire-user.sh script is meant for including in e.g. /home/spot/.xinitrc , it starts pipewire etc.. as currently logged in user.
If you change in /root/.xinitrc to . /usr/local/bin/pipewire-user.sh , pipewire will run as root when logged in as root (works well from what I just tested).
Perhaps worth trying that (instead of pipewire running as spot) to see if solves anything, @geo_c (you're doing a great job, btw, by testing all this audio stuff , too advanced for me )

fredx181 wrote: ↑Fri Jan 19, 2024 5:44 pm

@rockedge @geo_c

Notice that it is using depreciated pipewire-media-session

It's deprecated, yes, but wireplumber is installed, so not using it.

That's good to know.

The more I test my KLV-airedale-RT15-JackPipe the more solid it seems to be working! I have native jack installed and can run it fully funcitoning as expected OR I can run jack applications using pw-jack, and when I do the latter I get all audio devices and pulse-application in and outs present and usuable by the jack apps. INCREDIBLE!

Literally the only thing not functioning at this point is hardware midi ins and outs.

@rockedge
My JackPipe system is squashed as an 08layer above 07-airedale-RT15_rootsfs, so if you want I could upload it and give you a screenshot of my system directory showing 6.1.38 kernel, firmware and modules so you can duplicate it and play with.

geo_c wrote:

Fred see my post above. Browsers work for me,

Does ls -l /home/ say for you that the spot dir is owned by spot ? (as I said, for me on sr8 it's not)

fredx181 wrote: ↑Fri Jan 19, 2024 5:54 pm

geo_c wrote:

Fred see my post above. Browsers work for me,

Does ls -l /home/ say for you that the spot dir is owned by spot ? (as I said, for me on sr8 it's not)

Whatever this says:

root# ls -l /home/
total 8
drwxrwx--- 1 weedog weedog 4096 Nov 12 16:06 spot
drwxr-xr-x 2 root   root      3 Dec 18  2021 void
drwx------ 5 weedog weedog  163 Nov 12 16:06 weedog
root# 

geo_c wrote: ↑Fri Jan 19, 2024 6:01 pm

fredx181 wrote: ↑Fri Jan 19, 2024 5:54 pm

geo_c wrote:

Fred see my post above. Browsers work for me,

Does ls -l /home/ say for you that the spot dir is owned by spot ? (as I said, for me on sr8 it's not)

Whatever this says:

Code: Select all

root# ls -l /home/
total 8
drwxrwx--- 1 weedog weedog 4096 Nov 12 16:06 spot
drwxr-xr-x 2 root   root      3 Dec 18  2021 void
drwx------ 5 weedog weedog  163 Nov 12 16:06 weedog
root# 

It's owned by weedog (user and group), fix:
chown -R spot:spot /home/spot

fredx181 wrote: ↑Fri Jan 19, 2024 6:05 pm

It's owned by weedog (user and group), fix:
chown -R spot:spot /home/spot

But....as far as I can tell, it's not broken!

Isn't there a rule about that somewhere?

I mean I guess it's supposed to run as spot, but it works running as weedog.

geo_c wrote: ↑Fri Jan 19, 2024 6:11 pm

fredx181 wrote: ↑Fri Jan 19, 2024 6:05 pm

It's owned by weedog (user and group), fix:
chown -R spot:spot /home/spot

But....as far as I can tell, it's not broken!

Isn't there a rule about that somewhere?

I mean I guess it's supposed to run as spot, but it works running as weedog.

For me it's broken, as run-as-spot doesn't work properly (and logging in as spot too) if /home/spot is owned by weedog (reason for the most is that the spot user doesn't have write permissions to /home/spot/)
Really, it's wrong!, /home/spot should be owned by spot (otherwise trouble), just like /home/weedog should be owned by weedog .

fredx181 wrote: ↑Fri Jan 19, 2024 6:29 pm

For me it's broken, as run-as-spot doesn't work properly (and logging in as spot too) if /home/spot is owned by weedog (reason for the most is that the spot user doesn't have write permissions to /home/spot/)
Really, it's wrong!, /home/spot should be owned by spot (otherwise trouble), just like /home/weedog should be owned by weedog .

I don't really do anything with spot. For me it's just there for making stuff work that needs it, which is not determined by me!

But if you don't mind taking the time, what sort of trouble are you referring to?

@fredx181 I just fixed it in 07KLV-airedale_rootfs.sfs and will repackage the ISO and upload it.

geo_c wrote:

But if you don't mind taking the time, what sort of trouble are you referring to?

Everything that runs as spot can give problem, e.g. for me run-as-spot firefox doesn't work, and same for when trying to login in as spot.
edit: and don't forget: pipewire etc.. runs as spot by default on KLV-Airedale, seems to work OK, but perhaps not full (because of permission problem), don't know.

@geo_c It suddenly dawned on me as I read the 10th thousandth article on pipewire and MIDI......it was beyond simple and if this is the fix........it will be quite humbling.
try in a terminal:

modeprobe snd-seq

Suddenly all the MIDI devices showed up in qpwgraph!! the MIDI bridges are RED

rockedge wrote: ↑Fri Jan 19, 2024 10:47 pm

@geo_c It suddenly dawned on me as I read the 10th thousandth article on pipewire and MIDI......it was beyond simple and if this is the fix........it will be quite humbling.
try in a terminal:

Code: Select all

modeprobe snd-seq

Suddenly all the MIDI devices showed up in qpwgraph!! the MIDI bridges are RED
Screenshot_2024-01-19_17-49-30.png

Awesome I'll try it!

And I finally got smart and bookmarked /usr/share/doc/pipewire in my browser and started reading. It's got all the terminal commands like playing audio files and midi files in the terminal, and I was just playing audio files with pw-cat -p and then tried to play a midi file with pw-midiplay and it came back with the message that it couldn't find the node, and I just thought, "It's simply not creating the node." (I was really just going to play the midi file knowing after reading the docs that it wouldn't output sound without a renderer like timidity, but I wanted to see if the midi output stream showed up in the graph. But it thew up an error that there was no node.

Okay, let me try it......

YEP!! There they are. I can go to bed early tonight. But probably won't because I'll be playing virtual instruments using pw-jack now.

Yes SUCCESS! My midi keyboard is playing Yoshimi synth in the Carla rack started with pw-jack Carla. And that's how it is all supposed to work.

So @rockedge I think KLV-Airedale-RT15 is put together just fine. I've got it so loaded up with my JackPipe 08-layer that it's a full fledged audio workstation now running on pipewire.

Thank you!

Oh and one question, is the modprobe persistent? Does it need to be added to a startup script somewhere?

Just thought of another question, I guess I should change that spot permission @fredx181 mentioned? I think I'll back up this copy first.

geo_c wrote:

is the modprobe persistent? Does it need to be added to a startup script somewhere?

I think we can put a script in /root/Startup to simply load it. We can adjust this as we learn more.

#!/bin/sh
modeprope snd-seq

geo_c wrote:

Just thought of another question, I guess I should change that spot permission @fredx181 mentioned?

Yes, to make sure, in a terminal:

chown -R spot:spot /home/spot
chown -R weedog:weedog /home/weedog

Next will be doing the same configuration in KLV-Spectr-RT which should also give excellent performance with any of the 6+ and possibly series 4+ and 5+ full real time kernels.

Should work, theoretically, fairly the same way.........

So @fredx181 Excellent news in the latest reports:

geo_c wrote: ↑Fri Jan 19, 2024 11:02 pm

So @rockedge I think KLV-Airedale-RT15 is put together just fine. I've got it so loaded up with my JackPipe 08-layer that it's a full fledged audio workstation now running on pipewire.

rockedge wrote: ↑Sat Jan 20, 2024 12:13 am

So @fredx181 Excellent news in the latest reports:

geo_c wrote: ↑Fri Jan 19, 2024 11:02 pm

So @rockedge I think KLV-Airedale-RT15 is put together just fine. I've got it so loaded up with my JackPipe 08-layer that it's a full fledged audio workstation now running on pipewire.

And it is running well, I'm going through all the jack applications available in Void and seeing what works well, and there's some pretty cool stuff, like LSP plugins which run standalone. When started with pw-jack these plugins show up as their own application in pipewire graphs.

but one small annoyance, even though I assigned all canine users to their proper owners, (weedog owns weedog, spot owns spot) I still get a policy error on more boots than not followed by no sound. A simple log out and login fixes it every time.

Which brings me to the question of the pulseaudio startup script in /Startup. Should it still be there, and if so maybe there's a timing issue with it on boot causing the polkit error?

geo_c wrote:

Which brings me to the question of the pulseaudio startup script in /Startup. Should it still be there, and if so maybe there's a timing issue with it on boot causing the polkit error?

If pipewire is running, startup of pulseaudio should be disabled (i.e. empty or non-executable script in ~/Startup) . Don't know if it has to do with the polkit error you get .
edit: I see now that ~/Startup/start_pulseaudio is not marked as executable in sr8 (-rw-r--r-- 1 root root 29 dec 21 2022 start_pulseaudio) , so pulseaudio not running by default.

correct! the start script in /root/Startup should be marked as non-executable and is still there because of the step by step approach we used to switch to pipewire from pulseaudio

rockedge wrote: ↑Sun Jan 21, 2024 5:42 pm

correct! the start script in /root/Startup should be marked as non-executable and is still there because of the step by step approach we used to switch to pipewire from pulseaudio

Yes that's true, the script is non-exectuable, and I had noticed that earlier, but wondering why it was there thought maybe there was a "backdoor" method of executing or referencing it.

I suppose the polkit issue still could be timing somewhere, since it clears up on logout/login the second time around.

@geo_c I have been running a KLV-Spectr-RT to check on the audio setup......and it's all good.

Added in the /root/Startup/load_snd-seq.sh to load the kernel module.

#!/bin/sh
modprobe snd-seq

Really have to say the performance running audio components seems outstanding. I do not have the necessary equipment to test it in depth but I have a good feeling it's going to be alright.

Must be the combination of KLV the RT kernel and light weight of the desktop environment.

What I need to do is have @Sofiya look over this version to do the magic polish. And make sure I have your key bindings and Spectrwm.conf. What I want to do is unify all of this into one KLV-Spectr-RT

but wondering why it was there thought maybe there was a "backdoor" method of executing or referencing it.

I think it is because to get sound to work in the first KLV's and run as root, we took a couple of less than official ways of starting pulseaudio. There are several places that could take precedence in directory hierarchy and perhaps a .desktop or start script was in one of those directories for what ever reason.

We didn't quite follow the recommended method from the manual so we can run primarily as the root user. So gotta double check there isn't some start mechanism still floating around.

I suppose the polkit issue still could be timing somewhere, since it clears up on logout/login the second time around.

I have experienced the same. Very seldom and it clears up immediately. During the early FirstRib and WDL (WeeDog) builds I saw quite a bit of this error. I do also think it is a timing issue in our case presently, and might have something to do with dBus.

To be sure if pulseaudio is running or not : run pidof pulseaudio

rockedge wrote: ↑Sun Jan 21, 2024 6:57 pm

There are several places that could take precedence in directory hierarchy and perhaps a .desktop or start script was in one of those directories for what ever reason.

We didn't quite follow the recommended method from the manual so we can run primarily as the root user. So gotta double check there isn't some start mechanism still floating around.

Well it doesn't look like pulseaudio is running since all pulse api applications show up in pw-cli output as pipewire-pulse.

rockedge wrote: ↑Sun Jan 21, 2024 6:51 pm

@geo_c I have been running a KLV-Spectr-RT to check on the audio setup......and it's all good.

Really have to say the performance running audio components seems outstanding. I do not have the necessary equipment to test it in depth but I have a good feeling it's going to be alright.

Must be the combination of KLV the RT kernel and light weight of the desktop environment.

If you're talking about Spectr-rc1, I have that mult-installed, so after I play around a little more Airedale-JackPipe I'll start loading jack apps into Spectr.

The RT-kernels and pipewire are performing enormously well. As I stated in the SHAKEDOWN topic, I was playing virtual instruments in Carla using Ardour to set the pw-jack buffer to 32. That's crazy low, and I ran a multi-sample instrument, sfz file, which is really resource intensive, and Airedale played beautifully with that, no Xruns. So extremely low latencies with pipewire/RT-kernel combination.

fredx181 wrote: ↑Sun Jan 21, 2024 7:12 pm

To be sure if pulseaudio is running or not : run pidof pulseaudio

I did this and got absolutely no verbose output, so I don't know that means.

root# pidof pulseaudio
root# 

I don't see anything in htop that says pulseaudio

geo_c wrote: ↑Sun Jan 21, 2024 7:17 pm

fredx181 wrote: ↑Sun Jan 21, 2024 7:12 pm

To be sure if pulseaudio is running or not : run pidof pulseaudio

I did this and got absolutely no verbose output, so I don't know that means.

Code: Select all

root# pidof pulseaudio
root# 

It means that it's not running (otherwise it would show a "pid" number).

fredx181 wrote: ↑Sun Jan 21, 2024 7:21 pm

It means that it's not running (otherwise it would show a "pid" number).

Let me look up that pidof command, because I should know how to use that! Basic stuff @geo_c does not know, but never lets his ingorance get in the way!

fredx181 wrote: ↑Sun Jan 21, 2024 7:40 pm

Code: Select all

root# pidof blahblablah
root#

Code: Select all

root# pidof geo_c
root#

Code: Select all

root# pidof Xorg
2230
root#

Ah yes, but there are also options!

root# pidof --help

Usage:
 pidof [options] [program [...]]

Options:
 -s, --single-shot         return one PID only
 -c, --check-root          omit processes with different root
 -q,                       quiet mode, only set the exit code
 -w, --with-workers        show kernel workers too
 -x                        also find shells running the named scripts
 -o, --omit-pid <PID,...>  omit processes with PID
 -t, --lightweight         list threads too
 -S, --separator SEP       use SEP as separator put between PIDs
 -h, --help     display this help and exit
 -V, --version  output version information and exit

For more details see pidof(1).
root# 

And this leads me down the rabbit trail to the ps command. Look at all these OPTIONS!

To see every process on the system using standard syntax:
ps -e
ps -ef
ps -eF
ps -ely

   To see every process on the system using BSD syntax:
      ps ax
      ps axu

   To print a process tree:
      ps -ejH
      ps axjf

   To get info about threads:
      ps -eLf
      ps axms

   To get security info:
      ps -eo euser,ruser,suser,fuser,f,comm,label
      ps axZ
      ps -eM

   To see every process running as root (real & effective ID) in
   user format:
      ps -U root -u root u

   To see every process with a user-defined format:
      ps -eo pid,tid,class,rtprio,ni,pri,psr,pcpu,stat,wchan:14,comm
      ps axo stat,euid,ruid,tty,tpgid,sess,pgrp,ppid,pid,pcpu,comm
      ps -Ao pid,tt,user,fname,tmout,f,wchan

   Print only the process IDs of syslogd:
      ps -C syslogd -o pid=

   Print only the name of PID 42:
      ps -q 42 -o comm=

And not only that. There is also pgrep!
https://unix.stackexchange.com/question ... -and-pgrep

Once you point @geo_c in the right direction, no telling what he'll do....

geo_c wrote:

Once you point @geo_c in the right direction, no telling what he'll do...

.
Oh My... We can expect miracles !!