Hi Fons,
thanky you very much for your help!
now it works.
I was already in the realtime and also in the audio group, in fact, I
had modified limits.conf manually when setting up the system, and
later, I guess, had also installed the realtime-privileges package.
also I checked the priority settings of the jack daemon. Somewhere I
read priority should be between 50 and 70 or so. so I had this set
already, too; maybe not for every soundcard, though.
but, what also seems to be important - quite logically, if I read your
recent hints on the realtime-settings - is to tell the jack daemon to
run in realtime mode. Here, in qjackctl the related checkbox was
unchecked; I did that because I recently tried to start linux with the
arch stock kernel instead of the realtime kernel, just to see how this
works with my audio usage. And I thought if I don’t run the rt-kernel,
I have to uncheck the realtime-setting in qjackctl, which may be a
misconception (?).
now, with it enabled, zita-ajbridge works very well.
again, thank you very much!
christoph
Am Freitag, den 20.12.2019, 21:49 +0100 schrieb Fons Adriaensen:
> Hi Christoph,
>
> Some extra info:
>
> In case your system does allow real-time, it could be
> that the maximum priority is set too low.
>
> Zita-ajbridge will run the thread talking to the ALSA
> device with a priority that is 10 higher than Jack's
> callback threads. So if your jack is configured for
> e.g. 80, and the system limit is 85, zita-ajbridge
> will fail.
>
> Ciao,
>
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user@lists.linuxaudio.org
https://lists.linuxaudio.org/listinfo/linux-audio-user
Received on Wed Jan 1 02:17:04 2020
This archive was generated by hypermail 2.1.8 : Wed Jan 01 2020 - 02:17:04 EET