Modartt user forum - qjackctl trouble, again

Re: qjackctl trouble, again

null@example.com (stuartmacg) — Fri, 05 Aug 2022 21:24:40 +0000

All OK now. Prodded the update software anywhere I could and ran updates. Now moved from qjackctl 0.50 to 0.94, and other jack stuff, firmware etc. updated - different interface and all works (so fat at least)

Re: qjackctl trouble, again

null@example.com (stuartmacg) — Fri, 05 Aug 2022 17:14:14 +0000

I installed ubuntu studio, years ago.
If I start jack using the ubuntu studio controller, pt does not see jack.
May try a clean install.

Beco wrote:

Hi Stuart,
I have no idea what is going on in your system. But I would suggest that you should install a rt kernel (5.10.0-16-rt-amd64 #1 SMP PREEMPT_RT Debian - I am using this one), so you can run in a very low latency and direct from alsa (which is better). I am running PT at 128 polyphony and at 128 samples - 2.9 ms without any glitch, I could could go further but I prefer to keep safe.
You can try and I hope that works.
Best wishes

stuartmacg wrote:
was working fine: yamaha n1x and pt 7.5.4 with PC running ubuntu 20.04.4 LTS and qjackctl 0.5.0. (After an OS update) jack and pt now repeatedly connect and disconnect with a period of around a minute (not timed).
Sometimes pt gets midi input, but is not connected to the sound output. Other times pt keys do not move. Periodically pt it bursts into glorious life (playing with n1x sound enabled to allow me to continue playing when pt not active)
Tried looking at qjackctl messages - but high message volume even with no keys touched, no idea what it is saying - nothing clearly relevant.
The setup had been working for years, till this spring. It stopped working, then started again after an OS update. Now it has gone odd again.
I see qjackctl version is old - should I install new from source - would that need jack update too ...?
Are there some magic settings for either piece of SW? I have jack on a low latency setup (44 kHz, frames/buff 128, buff 2) and alsa enabled ...

Re: qjackctl trouble, again

null@example.com (Beco) — Fri, 05 Aug 2022 02:33:09 +0000

Hi Stuart,

I have no idea what is going on in your system. But I would suggest that you should install a rt kernel (5.10.0-16-rt-amd64 #1 SMP PREEMPT_RT Debian - I am using this one), so you can run in a very low latency and direct from alsa (which is better). I am running PT at 128 polyphony and at 128 samples - 2.9 ms without any glitch, I could could go further but I prefer to keep safe.

You can try and I hope that works.

Best wishes

stuartmacg wrote:

was working fine: yamaha n1x and pt 7.5.4 with PC running ubuntu 20.04.4 LTS and qjackctl 0.5.0. (After an OS update) jack and pt now repeatedly connect and disconnect with a period of around a minute (not timed).
Sometimes pt gets midi input, but is not connected to the sound output. Other times pt keys do not move. Periodically pt it bursts into glorious life (playing with n1x sound enabled to allow me to continue playing when pt not active)
Tried looking at qjackctl messages - but high message volume even with no keys touched, no idea what it is saying - nothing clearly relevant.
The setup had been working for years, till this spring. It stopped working, then started again after an OS update. Now it has gone odd again.
I see qjackctl version is old - should I install new from source - would that need jack update too ...?
Are there some magic settings for either piece of SW? I have jack on a low latency setup (44 kHz, frames/buff 128, buff 2) and alsa enabled ...

qjackctl trouble, again

null@example.com (stuartmacg) — Wed, 03 Aug 2022 23:08:21 +0000

was working fine: yamaha n1x and pt 7.5.4 with PC running ubuntu 20.04.4 LTS and qjackctl 0.5.0. (After an OS update) jack and pt now repeatedly connect and disconnect with a period of around a minute (not timed).

Sometimes pt gets midi input, but is not connected to the sound output. Other times pt keys do not move. Periodically pt it bursts into glorious life (playing with n1x sound enabled to allow me to continue playing when pt not active)

Tried looking at qjackctl messages - but high message volume even with no keys touched, no idea what it is saying - nothing clearly relevant.

The setup had been working for years, till this spring. It stopped working, then started again after an OS update. Now it has gone odd again.

I see qjackctl version is old - should I install new from source - would that need jack update too ...?

Are there some magic settings for either piece of SW? I have jack on a low latency setup (44 kHz, frames/buff 128, buff 2) and alsa enabled ...