Oh lordy … so it is the poetterNIX effect again.?
Pulseaudio is the last PoetterNIX software I allow to run as all my problems the last 5 years were systenD/PoetterNIX, I mean everything.
As I understand, Pulseaudio … nice as it is is, is also a PoetterNIX creation.
But as all such things treats the rest of Linux with absolute disregard.
Replaces SYSVinit with horrible results for sysadmins trying to run SYSV scripts on the systemd INIT system. Completely drops @reboot support in CRON, with bad bad results. Most of the time you are not even aware that SYSVinit was not started but systemDinit instead. You install a small gnome app and low and behold without you noticing it also replases SYSV with SystemDInit and you usually dont notice. I now have cronjobs on all the servers I manage just looking out for PoetterNIX software installing without consent.
My systems stabilised nicely since I run NO systemD or PoetterNIX.
No I can only thank you, for asking pointed questions.
I can see where the fish rots now.
It seems that jack manages to wrestle Alsa out of the coils of Pulseaudio, but knowing the PoetterNIX software behavior I would not blame Ardour a bit !
The solution at this stage is to UNINSTALL Pulseaudio.
Pulseaudio is rather nice, but since it is PoetterNIX it has to go as it will bite, as it has.
Unless Ardour6 didnt fix this;
Is it possible that you can wrestle a bit harder in subsequent Ardour implementations to get Interface out of Pulse’s coils ?. You have my sympathy… This is technically not Ardour’s fault, but from my experience the PoetterNIX family of software is in general flux, break things/norms/customs and then just turns around and do something else in the next release.
I am pretty sure I am one of the few that uses Pulse with Alsa/Ardour. Alsa/Jack/Ardour