- qjackctl does not find it running, but the same command ran on the command line works
- how to use jack so that it starts the qjackctl patchbay config, without running qjackctl ?
I don't know what you mean, the QjackCtl config file is usually located in ~/.config/rncbc.org/QjackCtl.conf and contain configuration for QjackCtl. That is only related when you run QjackCtl, and does nothing at all when you didn't use QjackCtl.
Maybe you mean the jackd configuration file? This one is in ~/.jackdrc and contain the jackd start parameters which are used (and saved) by Qjackctl.
if I don't run qjackctl, nothing works, programs dont receive midi and no sound gets to alsa
this is how the wonderful audio linux world works, and it has basicaly always been like that
so I was wondering if I could run that config file so the patchbay is active so the routing works
QjackCtl is "just" a graphical front-end for jackd. So, if you want to have jackd started as if it was started by QjackCtl, check the file ~/.jackdrc, it contains the exact command line QjackCtl use to start jackd. Beside that, QjackCtl may also start some scripts or applications, when set so in the option tab.
Surly you need to connect ports to be able to receive/send midi events and audio buffers between applications and the hardware port. You could do that on the command line (jack_connect) or, with a graphical frontend like qjackCtl. Some apps providing there own patchbay as well.
May 09 20:35:10 raspberrypi jackd[413]: JACK is running in realtime mode, but you are not allowed to use realtime scheduling.
May 09 20:35:10 raspberrypi jackd[413]: Please check your /etc/security/limits.conf for the following line
May 09 20:35:10 raspberrypi jackd[413]: and correct/add it if necessary:
May 09 20:35:10 raspberrypi jackd[413]: @audio - rtprio 99
May 09 20:35:10 raspberrypi jackd[413]: After applying these changes, please re-login in order for them to take effect.
May 09 20:35:10 raspberrypi jackd[413]: You don't appear to have a sane system configuration. It is very likely that you
May 09 20:35:10 raspberrypi jackd[413]: encounter xruns. Please apply all the above mentioned changes and start jack again!
May 09 20:35:10 raspberrypi systemd[1]: jackd.service: Main process exited, code=exited, status=255/EXCEPTION
May 09 20:35:10 raspberrypi systemd[1]: jackd.service: Failed with result 'exit-code'.
May 09 20:35:10 raspberrypi systemd[1]: Failed to start Jack audio server.
May 10 13:16:35 raspberrypi jackd[424]: JACK is running in realtime mode, but you are not allowed to use realtime scheduling.
May 10 13:16:35 raspberrypi jackd[424]: After applying these changes, please re-login in order for them to take effect.
May 10 13:16:35 raspberrypi jackd[424]: You don't appear to have a sane system configuration. It is very likely that you
May 10 13:16:35 raspberrypi jackd[424]: encounter xruns. Please apply all the above mentioned changes and start jack again!
May 10 13:16:35 raspberrypi systemd[1]: jackd.service: Main process exited, code=exited, status=255/EXCEPTION