Going back to the OP… If you’re using Ubuntu isn’t there some kind of Ubuntu Studio overlay or Audio Utilities you could install to make this work better instead of all this thrashing in the dark…? The butchery of how (some) mainstream Distros handle PipeWire is kinda unbelievable… 
It’s literally a one-liner ldconfig command to make PipeWire JACK work invisibly like JACK1/2
That is your mistake. Never, and I mean NEVER trust any of these current AI tools.
They will deceive you, and gaslight you, and get you in all sorts of trouble, especially when dealing with something like Linux where users have a tremendous amount of power to change things (which also means tremendous power to mess things up)
If you have some knowledge of the subject, AI tools can be useful. But only if you can cajole them into giving you sensible answers, which means having enough knowledge to know when they are misleading you.
But if you don’t have that knowledge, using AI is a sure recipe for disaster.
It is, (or should be) far easier than messing around with installing individual packages, which appears to be what you were doing. Although it seems you were doing so by blindly following instructions from an AI.
Adding a PPA is really just adding a new software source to your software manager. The instructions are on the page I linked, 2 commands:
Cheers,
Keith
I thought that pipewire was invented to make things easier and ‘just work’ on linux.
When i read all this i think pipewire is a big failure and i will stick with ALSA…zero problems, just some inconveniences.
Then you clearly haven’t read Paul’s comments, for instance.
Pipewire works really well for most people. The main issue is mostly that people sometimes don’t know how to use it properly and that the distros may have fairly old versions.
If ALSA works for you, despite its inconveniences, it’s a good choice as well.
What kind of comment is this? Be serious! There’s nothing that “just works” if you don’t know how to make it work! Even using a coffee maker requires some level of skills…
Please note that I’m having a lot of trouble setting up and using Pipewire, like I said on my last post here on the forum, so I’m not on any side of a holy war about it. PW is probably a good project but in my opinion is not mature enough to be used straight away. I clearly remember when ALSA didn’t just work at all, back the early 2000’s… Now, after decades, it is stable enough to say: it just works.
Then you should look at a specialised distro like AV Linux, Ubuntu Studio etc. where these things are already set up.
Debian made a decision to set up pipewire so you need to type this prefix to launch jack apps through it. It then filters down through the distros based on it and derivatives. Others such as Fedora and Opensuse don’t have this quirk. So, as mentioned, it depends how the distro is set up to how many problems there are.
Thanks, yes, good point. I have a laptop I occasionally use for recording performances with Ub.Studio. I upgraded it to 24 some months ago and so came face to face with plasma for the first time. A fresh install of Studio on my desktop computer might be worth it in the long run. Does the choice of desktop i.e. plasma, gnome… matter to Ardour in any way? And does X11 vs. Wayland matter to Ardour?
It’s not, I believe.
You’d probably need some additional tweaks to achieve decent Ardour performance under Wayland. And using Ardour on Wayland is generally discouraged by the devs (for good reason). I’d stick with X11 for professional audio production anyway, unless you’re using Wayland native apps like PreSonus StudioLive.
I have run Ardour fine in both X11 and XWayland (what wayland uses to run X programs).
You need to state the reason otherwise you’re just spreading FUD.
There was discussion in a different thread recently of a few X features which XWayland does not currently implement. It depends on your usage patterns how much those bother you.
So did I. Out of the box Ardour performance on Wayland was terrible in my case. After some tweaking (the ‘Use intermediate image-surface to render canvas’ option was crucial, if I remember correctly) performance was comparable to X11 – though still with slightly higher CPU usage on Wayland. Anyway, I dropped Wayland not because of Ardour, but because of overwhelming flux of issues in other apps on my Debian/Trixie workstation. And I consider myself a power user. If your mileage differs, that’s fine.
As @ccaudle mentioned, there was a rather lenghtly discussion about this topic recently. I don’t consider most of the arguments presented there to be a FUD. Anyway, I don’t despise Wayland – quite the opposite. I still believe it’s future of Linux. But it is just not ready for the prime time yet. And yes, that’s just my personal opinion – but it’s based on direct experience, not on obscure superstitions or hearsay.
That thread is not relevant to the question asked. If there’s some issue with using Ardour on Wayland, then say what it is rather than just allude to something that may be anything and was actually nothing. Not everyone is a forum “power user” able to telepathically understand what you are talking about.
