Hi
I just compiled Jamulus on Linux-Mint 19.1. Running it results in what is shown in the attached screenshot. QJackCtl reports the parameters as set, that jackd is running, but under "messages" shows
09:07:12.247 Statistics reset.
09:07:12.285 ALSA connection change.
09:07:12.526 D-BUS: Service is available (org.jackaudio.service aka jackdbus).
09:07:12.550 JACK connection change.
09:07:12.563 Client activated.
09:07:12.563 Patchbay deactivated.
Cannot lock down 82280346 byte memory area (Cannot allocate memory)
inotify_add_watch("/home/me/.config/qt5ct") failed: "No such file or directory"
09:07:12.921 JACK connection graph change.
09:07:35.019 JACK connection graph change.
09:17:43.981 JACK connection graph change.
09:18:15.358 JACK connection graph change.
Can anyone assist?
I found I got the warning message a couple of times when I first started, even though the QJackCtl setting was correct. I lazily just rebooted my machine and then it was fine. No idea why though.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
normally it can happen that qJackCtl runs twice, especially if you have two sound interfaces, so maybe you should have done a "killall jackd" on the terminal console and restart ony one instance
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi
I just compiled Jamulus on Linux-Mint 19.1. Running it results in what is shown in the attached screenshot. QJackCtl reports the parameters as set, that jackd is running, but under "messages" shows
09:07:12.247 Statistics reset.
09:07:12.285 ALSA connection change.
09:07:12.526 D-BUS: Service is available (org.jackaudio.service aka jackdbus).
09:07:12.550 JACK connection change.
09:07:12.563 Client activated.
09:07:12.563 Patchbay deactivated.
Cannot lock down 82280346 byte memory area (Cannot allocate memory)
inotify_add_watch("/home/me/.config/qt5ct") failed: "No such file or directory"
09:07:12.921 JACK connection graph change.
09:07:35.019 JACK connection graph change.
09:17:43.981 JACK connection graph change.
09:18:15.358 JACK connection graph change.
Can anyone assist?
In QJackCtl settings you have to make sure that the sample rate is set to 48 kHz.
And QJackCtl reports that the sample rate IS 48k.
Kind Regards,
Edwin Humphries
On 2 Apr. 2020, 4:57 pm, at 4:57 pm, Volker Fischer corrados@users.sourceforge.net wrote:
Hmm. I never had this issue. If I set it to 48 kHz in QJackCtl, Jamulus is happy. Maybe someone else has an idea what could go wrong here...
I found I got the warning message a couple of times when I first started, even though the QJackCtl setting was correct. I lazily just rebooted my machine and then it was fine. No idea why though.
Selected device ?
normally it can happen that qJackCtl runs twice, especially if you have two sound interfaces, so maybe you should have done a "killall jackd" on the terminal console and restart ony one instance