Hello, is there a way to start qjackctl without appearing ? I want my raspberry pi to star qjackctl so that the patchbay config is active

would be better to have qjackctl run headless how can I run command lines equivalent to the patch bay defined in my .xml config ? On 12/05/2020 17:04, Kjetil Matheussen wrote: -- L'absence de virus dans ce courrier électronique a été vérifiée par le logiciel antivirus Avast. https://www.avast.com/antivirus JackAudio mailing list JackAudio(a)lists.linuxaudio.org https://lists.linuxaudio.org/listinfo/jackaudio

On Tue, May 12, 2020 at 6:36 PM tersewings <tersewings(a)protonmail.com> wrote: No, he wanted to run the patchbay.

On Tue, 12 May 2020, pfl wrote: See jack-plumbing. It has to be active permanently and parses a config file. Example: (connect "PortAudio:out_.*[13579]" "main:input_2") (connect "PortAudio:out_.*[02468]" "main:input_1") (disconnect "PortAudio:out_.*" "system:playback_.*") (connect "netjack:capture_1" "main:input_1") (connect "netjack:capture_2" "main:input_2")

Hi Phil, On 2020-05-08 18:10:16 (+0200), pfl wrote: This is because you run jackd as root. This is because you start jackd as your unprivileged user. This may have several reasons, but also it is absolutely not recommended to do that. It seems (but I'm not sure), that you are starting jackd in a systemd **system** service. This means, that you run jackd as root (which is not recommended) and naturally an instance of qjackctl, run by your unprivileged user can not interact with it. To read up on the differences, please refer to upstream documentation [1]. You can have a look at the default systemd **user** service [1], that is available in the jack2 repository (and depending on your distro is installed with jack2 or not). When installed (or copied to a user service location and modified to cope with the templating strings), you are able to start it with settings provided in one of the configuration files mentioned in `EnvironmentFile`. So, if you have `~/.config/jack/something.conf` with whatever configuration you want to use, you can start the service with systemctl --user start jack@something If you want to have this service start with your user session, enable it: systemctl --user enable jack@something If you want to automatically start the session of your user, on boot of the machine (might require elevated privileges to activate): loginctl enable-linger <your-username-or-uid> After reboot your user service (this is a **system** service running as your user) `user@<your-username>` should be started automatically (even **before** you log in with a graphical session). Below your `user@.service`, you should see a jack@something **user** service. If you want to have a look at this in the cgroups available on your system: systemd-cgls If you want to see jackd's stdout/stderr, you can use the user journal: journalctl --user -b0 -u jack@something or just the plain status of the service: systemctl --user status jack@something I hope this was of help. Best, David [1] https://www.freedesktop.org/software/systemd/man/systemd.unit.html [2] https://github.com/jackaudio/jack2/blob/develop/systemd/jack%40.service.in [3] https://github.com/jackaudio/jack2/blob/develop/systemd/example.conf

Hi Phil, On 2020-05-12 20:37:40 (+0200), pfl wrote: Yeah, running a **system** service as a user (using the `User=` directive) might also work, as long as you get the required directories in line. Have a look at the realtime related settings in the upstream user service [1]. They are also applicable to **system** services and basically allow your service to use realtime scheduling priority of up to 95. Otherwise any service either defaults to a setting from its parent or the system-wide default (set by your distribution). To read more about those settings, have a look at the upstream systemd.exec documentation [2]. Note, that for an unprivileged user you have to allow said user to use a specific realtime scheduling priority (e.g. 95) and unlimited memlock. On Arch Linux we have started making this available via the `realtime` user group [3] (on other distributions it's sometimes coupled to the `audio` group) by installing a configuration drop-in to /etc/security/limits.d/. However, this can also be set for your specific user only (see /etc/security/limits.conf for the syntax). Best, David [1] https://github.com/jackaudio/jack2/blob/develop/systemd/jack%40.service.in#… [2] https://www.freedesktop.org/software/systemd/man/systemd.exec.html#Process%… [3] https://git.archlinux.org/svntogit/community.git/tree/trunk/99-realtime-pri…

anyone ?