The biggest issue with Pipewire IMHO is that it does not support Ubuntu 18.04 LTS. That will be a big obstacle to growth until 18.04 is no longer supported, which is still about two years away. I don't know what's involved in doing a backport, but I for one would use Pipewire if it was working on 18.04. On Wed, Jun 30, 2021 at 3:59 PM Robin Gareus <robin(a)gareus.org> wrote: -- Borasky Research Journal https://www.znmeb.mobi Markovs of the world, unite! You have nothing to lose but your chains!

On Thu, 1 Jul 2021 07:01:31 +0100 Keith Edmunds <kae(a)midnighthax.com> wrote: Is pipewire runnable on the raspberry Pi? Anyone tried it? -- 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.

Let me say a bit more about my situation. I run a mix of Windows 10/11 (including Windows Subsystem for Linux) and Linux audio software. Some is proprietary with a corporate support model, some is bundled with hardware (NVIDIA Jetsons and Bela) and supported by the hardware vendor, and some is open source projects, either my own or publicly accessible in more recent versions than what's on the distro. The particular incident that relates to Pipewire arose from the latter category - I saw some interesting writing about Pipewire and wanted to experiment with it on the NVIDIA Jetsons. They ship with an NVIDIA-supported operating system called Linux for Tegra (L4T), which is arm64 Ubuntu 18.04 LTS "Bionic Beaver" with some modifications and enhancements for the hardware platform. When I downloaded Pipewire and tried to install it from source, it did not build because some libraries on 18.04 are too old. In this case I do *not* have the option to upgrade to 20.04 until NVIDIA gets around to upgrading L4T to 20.04, which seems like a major problem in the making for all of their other users who've built on 18.04. I'm guessing it would also be a major problem for Pipewire to backport to the 18.04 libraries - they may depend on functionality not present.But if they could backport it, I'd certainly test it if it offers something better than JACK on the hardware. On Thu, Jul 1, 2021 at 4:03 PM bill-auger <bill-auger(a)peers.community> wrote: -- Borasky Research Journal https://www.znmeb.mobi Markovs of the world, unite! You have nothing to lose but your chains!

On Wed, 30 Jun 2021 16:11:47 -0700 M. Edward (Ed) Borasky wrote: I've just seen a response from SOURAV DAS posted on 11 May to: https://ubuntuhandbook.org/index.php/2021/05/install-latest-pipewire-ppa-ub… Saying "Hi, the PPA maintainer here. Now added supports for Ubuntu 18.04 also." Linux Mint 20.1 (Ubuntu 20.04) here, so haven't tested it. -- John. It's better to be an outlier than an out and out liar.

On Wed, 30 Jun 2021 15:48:31 -0700 Yuri wrote: [...] Yes. I've used it for a whole day now, on Linux Mint 20.1 Ulyssa base (Ubuntu 20.04 focal). Everything seems to just work. The only thing I had to set was the Profile for the CM106 Like sound device I use, in PaVuCtl to Digital Stereo Duplex (IEC958). One small problem for me is that jack_transport locate doesn't work, but I expect it will soon. May be related to Jackdbus support which is "very tedious to implement" Wim Taymans said. https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/819 -- John. More diplodocus than diplomatic.

On Thu, Jul 01, 2021 at 06:57:59PM -0400, bill-auger wrote: The distro is at fault for not packaging it. Is there anything that prevents you from compiling and building pipewire on 18.04? If not, then it is a distro problem. They have not packaged pipewire for 18.04, and they probably won't package it since 18.04 is a stable release so major new changes won't be made. It would be possible to add it in as a backport, that could optionally be added. -- Gordonjcp

Le Thu, 1 Jul 2021 18:57:59 -0400, bill-auger <bill-auger(a)peers.community> a écrit : Distros do what they can. If your favourite software is not included, you can contribute to it by at least making a bug report asking for its addition. Software developers make software, not distribution. They like when a distribution support their software, but they are not responsible for that. Also, if a given software builds and works on a given distribution, as example the distro(s) of the dev(s), it should work with all other distributions where the dependencies are satisfied. For pipewire, as systemd is an optional run time depend, it should builds and works on all distributions providing alsa, dbus, python and meson, which must be something like all not very old distributions. So again, if your favourite distro did not include pipewire, you can consider to contribute to it, or for an outdated distribution, to one of its external repository or overlay. Cheers, Dominique

On Tue, Jul 06, 2021 at 10:04:28AM +0100, Will Godfrey wrote: I've started moving away from systemd on all systems. Not finished yet but getting close. Had a look at the PW docs, and really didn't like what I saw. The thing looks horribly complicated, lots of abstraction for its own sake, and dependencies all over the place (dbus, polkit, systemd,...) On a more fundamental level, I don't want the 'desktop' and 'pro' audio systems to be unified. It would be even worse than having all those pesty autoconnecting Jack apps. And for the 'pro' side, I'd prefer something as simple and autonomous as possible. Ciao, -- FA

On Tue, 6 Jul 2021 15:27:53 +0100 I wrote: Now wailing with joy having found a workaround. Simply need to send 'play' to jack_transport after any 'locate'. Strange, but true. -- John.

New problem. I run jack_capture, at certain times, via cron. Can run the script manually and it works fine, but just doesn't start from the cronjob. I have no idea why. Same story with arecord and pw-record (which has no -d duration). Script works fine from command line, but no joy from the crontab (the thing I do at the same time on the next line, works). It's a head scratcher. Something I'm missing, but it's definitely staying, even if I have to set my alarm clock to remind me to run my script. -- John.

On Sat, 3 Jul 2021, John Murphy wrote: 18.04 is of interest because... after that Ubuntu drops 32 bit ... everything they could get away with. It is for this reason I have switched at least one of my computers to debian. Not of interest to linux audio in general, except this 32bit laptop did save a recording session when the "recording machine" with win 10 showed up without the proper driver for the interface which worked just fine on this linux box because the interface was usb 2.0. However, to be more inline with the topic: beware that if you wish to use pipewire on ubuntu, the above ppa is required because none of the releases keep up with this quickly changing software. Also, be aware that (last I heard) the ffado backend is not supported. The expectation is that the alsa drivers will just work. If the current kernel will actually load the snd-<fwcardtype> (mine does not right now), the performance is even worse than usb boxes. So for firewire, jack is still king and usb 2.0 audio can still not match most firewire devices despite their age. With a properly setup pipewire, pipewire should auto bridge to jackd... I have not achieved this yet but I have not had time really either. Getting a boat in the water so the family could spend last week "messing about with boats" has been more important ;) -- Len Ovens www.ovenwerks.net