Thanks, I'm not new to any of this stuff. My tests aren't "random", nor are they "tests" as such, I'm seeing issues during my normal daily usage. I don't *only* use Ardour, it's a multi-purpose workstation, and PulseAudio gives me a lot of useful flexibility which I'm not going to give up unless it's intrinsically too buggy to use. By and large, the pulseaudio-jackdbus integration is great.
In any event, even after jack is disabled, the lockups seem to have continued. I say "seem to", because I'm testing old audio files, some of which are corrupt from an old bad hard disk, so I need to make sure that any strange behaviour is the same as I've seen earlier.
I also don't remember such lockups with pulseaudio and jackdbus and my old interface (the supposedly crappy Behringer UCA202 which never caused me any trouble), although both hardware and software have changed since then, so who knows...
On 14 April 2017 at 22:00, Ralf Mardorf <ralf.mardorf@xxxxxxxxxxxxx> wrote:
When troubleshooting something, even a broken radio or coffee machine,
you should check on thing after the other.
Why do you do random tests running two sound servers at once?
You mentioned you want to use Ardour. At least for testing purpose
consider to use Ardour just with ALSA, explicitly without launching
jack and/or pulseaudio at all.
Btw. I'm very surprised that so many people need to do real-time audio
recording with pulseaudio. I know, thousands of people want to record
skype interview or watch youtube tutorials.
I don't know if http://github.com/i-rinat/apulse helps with skype
interviews, but at least http://rg3.github.io/youtube-dl/ helps with
tutorials.
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user@lists.linuxaudio.org
http://lists.linuxaudio.org/listinfo/linux-audio-user
_______________________________________________ Linux-audio-user mailing list Linux-audio-user@xxxxxxxxxxxxxxxxxxxx http://lists.linuxaudio.org/listinfo/linux-audio-user
