Re: [LAD] pipewire
Evening all. A timely thread, for me. I've just moved to a faster PC and, with an eye to getting pipewire working, I've installed VirtualBox (6.1.30) and made a VM of the same distro (Mint 20.3) as on the host. I'll clone it so it's easy to 'redo from start' when I mess it up. I've read differences of opinion about it. -- John. [Mint 20.3 Cinnamon, looks and feels excellent.] ___ Linux-audio-dev mailing list Linux-audio-dev@lists.linuxaudio.org https://lists.linuxaudio.org/listinfo/linux-audio-dev
Re: [LAD] pipewire
On 2022-01-17 14:56:30 (+0100), Fons Adriaensen wrote: > Hello all, > > I'd like to test pipewire as a replacement for Jack (on Arch), > and have been reading most (I think) of the available docs. > > What is clear is that I will need to install the pipewire > and pipewire-jack packages. > > And then ? With the pipewire currently in [testing] it would even be the only thing you need to do, as it replaces jack2 (or jack). A good place to look for answers in regards to pipewire would be its official wiki [1] and documentation [2]. Please note, that before pipewire-jack >= 1:0.3.43-4 is in [extra] you will need to use pw-jack to run applications with pipewire's jack implementation or override your ld.so.conf (see wiki on that [3]). It should be moved this evening though and I'll try to update the wiki afterwards to reflect this change. > How do I tell pipewire to use e.g. hw:3,0 and make all of > its 64 channels appear as capture/playback ports in qjackctl ? I *think* you need to use the "Pro Audio" configuration for your specific device to make that work. > Note: I do not have anything PulseAudio (like pavucontrol) > installed and don't want to either. If that would be a > requirement then I'll just forget about using pipewire. Pavucontrol would be one way of doing so. It's also possible via pw-cli [4] (Wim Taymans gave that example on IRC - #pipewire on oftc.net is a good resource too!). Best, David [1] https://gitlab.freedesktop.org/pipewire/pipewire/-/wikis/home [2] https://docs.pipewire.org [3] https://wiki.archlinux.org/title/PipeWire#JACK_clients [4] https://gitlab.freedesktop.org/pipewire/pipewire/-/wikis/Migrate-PulseAudio#set-card-profile -- https://sleepmap.de signature.asc Description: PGP signature ___ Linux-audio-dev mailing list Linux-audio-dev@lists.linuxaudio.org https://lists.linuxaudio.org/listinfo/linux-audio-dev
Re: [LAD] pipewire
I've heard of success stories -- most notably with Fedora -- and keep circling back to it. I'm using Pop!_OS 20.04 -- which is close 'nuf to Ubuntu 20.04 -- together with the KX Studio repositories. Cadence et all have been my friends... So. without knowing at all what I'm doing, I tried pipewire a few months ago and everything became an unusable mess. I uninstalled it all and tried again recently. While I'm not sure how to use it all, Catia now sees a whole bunch more than it used to, and various audio apps that I used to fuss with a bit seem to be working automatically. I found a couple of answers to "Replacing Pulseaudio with Pipewire in Ubuntu 20.04" https://askubuntu.com/a/1339897/2059 https://askubuntu.com/a/1365822/2059 to be particularly helpful in getting all the wee bits working right -- as near as I can tell. For what it's worth, summarized here, the latest iteration of my experiments in installing: sudo add-apt-repository ppa:pipewire-debian/pipewire-upstream sudo apt full-upgrade sudo apt install libspa-0.2-bluetooth sudo apt install pipewire-audio-client-libraries systemctl --user daemon-reload systemctl --user --now disable pulseaudio.service pulseaudio.socket systemctl --user mask pulseaudio systemctl --user --now enable pipewire-media-session.service systemctl --user --now enable pipewire pipewire-pulse sudo rm /etc/pipewire/pipewire.conf sudo apt reinstall pipewire pipewire-pulse ___ Linux-audio-dev mailing list Linux-audio-dev@lists.linuxaudio.org https://lists.linuxaudio.org/listinfo/linux-audio-dev
Re: [LAD] pipewire
On Mon, 17 Jan 2022 16:03:03 +0100 Lorenzo Sutton wrote: >Hi, > >Thanks for opening this thread, I find this topic very interesting and >been discussing it with some people :-) > >If it might be of help, I'm on Manjaro which is Arch derivative so >probably similar and I followed the Arch guide, and tried the >'substitution' - TL:DR: I eventually reverted back to pulseaudio+jack, >for now. > >On 17/01/22 14:56, Fons Adriaensen wrote: > >[...] > >> I'd like to test pipewire as a replacement for Jack (on Arch), >> and have been reading most (I think) of the available docs. >> >> What is clear is that I will need to install the pipewire >> and pipewire-jack packages. > >My problem with that set-up is that it seemed that something like Ardour >would need to be explicitly run via pw-jack so e.g. > >pw-jack ardour > >But then setting the samplerate (I have projects at different >samplerates), wasn't trivial. > >If I understand correctly eventually pipewire will be a drop-in and the >pw-jack shouldn't be needed. > >The other thing I wasn't able to figure out was how to use it as I >previously would use qjackctl > >> >> And then ? >> >> How do I tell pipewire to use e.g. hw:3,0 and make all of >> its 64 channels appear as capture/playback ports in qjackctl ? > >This was also unclear for me. I use 3 audio interfaces mainly and have >dedicated qjackctl 'profiles', and that works quite well for me, so >wasn't sure how this is handled in pipewire. > >If you'd be willing to share any results in this thread it would be >really useful. > >My current workflow is to launch jack when needed with the correct >device / samplerate configuration when needed, only _if_ needed open a >pulseaudio sink (e.g. browser audio needed while using jack). But I >understand that's might be a very 'personal' approach to it all :-) > >One interesting (yet still anecdotal?) aspect is that potentially >pipewire manages to provide better latency? > >Lorenzo I'm also on the 'wait and see' list. For me, Jack is just plug and play. I'd want pipewire to be the same. As for latency, this seems to be more to do with my USB soundcard than anything else. -- Will J Godfrey https://willgodfrey.bandcamp.com/ http://yoshimi.github.io Say you have a poem and I have a tune. Exchange them and we can both have a poem, a tune, and a song. ___ Linux-audio-dev mailing list Linux-audio-dev@lists.linuxaudio.org https://lists.linuxaudio.org/listinfo/linux-audio-dev
Re: [LAD] pipewire
Hi, Thanks for opening this thread, I find this topic very interesting and been discussing it with some people :-) If it might be of help, I'm on Manjaro which is Arch derivative so probably similar and I followed the Arch guide, and tried the 'substitution' - TL:DR: I eventually reverted back to pulseaudio+jack, for now. On 17/01/22 14:56, Fons Adriaensen wrote: [...] I'd like to test pipewire as a replacement for Jack (on Arch), and have been reading most (I think) of the available docs. What is clear is that I will need to install the pipewire and pipewire-jack packages. My problem with that set-up is that it seemed that something like Ardour would need to be explicitly run via pw-jack so e.g. pw-jack ardour But then setting the samplerate (I have projects at different samplerates), wasn't trivial. If I understand correctly eventually pipewire will be a drop-in and the pw-jack shouldn't be needed. The other thing I wasn't able to figure out was how to use it as I previously would use qjackctl And then ? How do I tell pipewire to use e.g. hw:3,0 and make all of its 64 channels appear as capture/playback ports in qjackctl ? This was also unclear for me. I use 3 audio interfaces mainly and have dedicated qjackctl 'profiles', and that works quite well for me, so wasn't sure how this is handled in pipewire. If you'd be willing to share any results in this thread it would be really useful. My current workflow is to launch jack when needed with the correct device / samplerate configuration when needed, only _if_ needed open a pulseaudio sink (e.g. browser audio needed while using jack). But I understand that's might be a very 'personal' approach to it all :-) One interesting (yet still anecdotal?) aspect is that potentially pipewire manages to provide better latency? Lorenzo ___ Linux-audio-dev mailing list Linux-audio-dev@lists.linuxaudio.org https://lists.linuxaudio.org/listinfo/linux-audio-dev
[LAD] pipewire
Hello all, I'd like to test pipewire as a replacement for Jack (on Arch), and have been reading most (I think) of the available docs. What is clear is that I will need to install the pipewire and pipewire-jack packages. And then ? How do I tell pipewire to use e.g. hw:3,0 and make all of its 64 channels appear as capture/playback ports in qjackctl ? Note: I do not have anything PulseAudio (like pavucontrol) installed and don't want to either. If that would be a requirement then I'll just forget about using pipewire. TIA, -- FA ___ Linux-audio-dev mailing list Linux-audio-dev@lists.linuxaudio.org https://lists.linuxaudio.org/listinfo/linux-audio-dev
