Re: getting started with pipewire

2025-01-11 Thread Max Nikulin
Adding the mailing list back. The message was sent off-list by mistake, so overquoting. On 10/01/2025 19:15, Haines Brown wrote: On Fri, Jan 10, 2025 at 10:01:57AM +0700, Max Nikulin wrote: On 09/01/2025 21:15, Greg Wooledge wrote: Moral of the story: NEVER EVER run "wpctl". My guess is tha

Re: getting started with pipewire

2025-01-09 Thread Max Nikulin
On 09/01/2025 21:15, Greg Wooledge wrote: Moral of the story: NEVER EVER run "wpctl". My guess is that it may be a consequence of "wireplumber" you executed earlier. Having no notion what particular components of pipewire/pulse do, I would avoid running random commands supposed to be started

Re: getting started with pipewire

2025-01-09 Thread Geoff
Greg Wooledge wrote: On Thu, Jan 09, 2025 at 07:39:29 -0500, Haines Brown wrote: I have pipewire-pulse intstalled, not puleaudio. Maybe change that? hobbit:~$ dpkg -l | grep pulse ii libpulse-mainloop-glib0:amd6416.1+dfsg1-2+b1amd64 PulseAudio client libraries

Re: getting started with pipewire

2025-01-09 Thread pocket
> Sent: Thursday, January 09, 2025 at 9:15 AM > From: "Greg Wooledge" > To: debian-user@lists.debian.org > Subject: Re: getting started with pipewire > > On Thu, Jan 09, 2025 at 09:00:24 -0500, Greg Wooledge wrote: > > > $ wpctl status > > >

Re: getting started with pipewire

2025-01-09 Thread tomas
On Thu, Jan 09, 2025 at 09:15:16AM -0500, Greg Wooledge wrote: > On Thu, Jan 09, 2025 at 09:00:24 -0500, Greg Wooledge wrote: > > > $ wpctl status > > > Could not connect to PipeWire > > > > hobbit:~$ wpctl status [...] > I tried everything I could immediately think of, including logging out

Re: getting started with pipewire

2025-01-09 Thread Greg Wooledge
On Thu, Jan 09, 2025 at 09:00:24 -0500, Greg Wooledge wrote: > > $ wpctl status > > Could not connect to PipeWire > > hobbit:~$ wpctl status > ^C > > It just "hung" with no output. > > After I pressed Ctrl-C, my audio stopped working. I'm never going > to do this one again! > > > # syste

Re: getting started with pipewire

2025-01-09 Thread Greg Wooledge
On Thu, Jan 09, 2025 at 07:39:29 -0500, Haines Brown wrote: > I have pipewire-pulse intstalled, not puleaudio. Maybe change that? hobbit:~$ dpkg -l | grep pulse ii libpulse-mainloop-glib0:amd6416.1+dfsg1-2+b1amd64 PulseAudio client libraries (glib support) ii li

Re: getting started with pipewire

2025-01-09 Thread Haines Brown
Now I get these lines from systemctl --user status pipewire.service Jan 02 09:39:26 iskra systemd[1518]: Started pipewire.service - PipeWire Multimedia Service. Jan 07 11:14:49 iskra pipewire[1534]: spa.alsa: 'front:0': playback open failed: Device or resource busy Jan 07 1

Re: getting started with pipewire

2025-01-08 Thread Haines Brown
On Wed, Jan 08, 2025 at 09:35:03AM +0700, Max Nikulin wrote: > On 08/01/2025 00:08, Haines Brown wrote: > > I have no idea how to use pipewire. Do you simply run the comand $ pipewire > > to > > get an interface like alsamixer? > > Why are you trying to start pipewire manually? Systemd should do

Re: getting started with pipewire

2025-01-07 Thread Greg Wooledge
On Wed, Jan 08, 2025 at 09:35:03 +0700, Max Nikulin wrote: > On 08/01/2025 00:08, Haines Brown wrote: > > I have no idea how to use pipewire. Do you simply run the comand $ pipewire > > to > > get an interface like alsamixer? > > Why are you trying to start pipewire manually? Systemd should do it

Re: getting started with pipewire

2025-01-07 Thread Max Nikulin
On 08/01/2025 00:08, Haines Brown wrote: I have no idea how to use pipewire. Do you simply run the comand $ pipewire to get an interface like alsamixer? Why are you trying to start pipewire manually? Systemd should do it for you as a part of user session. It is not an application with GUI. Y

Re: getting started with pipewire

2025-01-07 Thread Haines Brown
On Thu, Jan 02, 2025 at 10:15:18AM -0500, Haines Brown wrote: > Thanks to your heldp, with the help of the correct guide it seems I was able > to install > pipewire successflly. To apply it I had to reboot. I did the reboot and this was the result > $ pipewire > [E][00304.248813]

Re: getting started with pipewire

2025-01-02 Thread Haines Brown
Thanks to your heldp, with the help of the correct guide it seems I was able to install pipewire successflly. To apply it I had to reboot. I assumed that once rebooted I should restart the pipewife daemon with the command as follows. Howerver it gave me errors: $ pipewire [E]

Re: getting started with pipewire

2025-01-01 Thread Haines Brown
On Wed, Jan 01, 2025 at 10:31:47AM -0700, Charles Curley wrote: > 0.3.65 is the version on Debian 12. Why are you following the > instructions for Debian 11 if you are on Debian 12? Oops! The wiki did not explicitly say it was for Debian 11 and I as not sufficiently cautious. I find many directi

Re: getting started with pipewire

2025-01-01 Thread Charles Curley
On Wed, 1 Jan 2025 12:01:52 -0500 Haines Brown wrote: > It says to start of by doing: > > # touch /etc/pipewire/media-session.d/with-pulseaudio > > The problem is that I have no /etc/pipewire/ although it is installed: > > $ pipewire --version > pipewire > Compiled with

getting started with pipewire

2025-01-01 Thread Haines Brown
I have ALSA and PulseAudio installed, but intend to use PipeWire as principle server and so installed that as well, although I gather pipewire is automatically installed in bookworm. I follow the guidance of https://wiki.debian.org/PipeWire but get into trouble right at the start. It says to