3 Oct
2019
3 Oct
'19
3:10 p.m.
Yes jackd2 works perfectly, I did it some years ago with systemd scripts ,
Warning: I am not a specialist in systemd, and also I didnt know if it is
better jackd as dbus-run-session or systemd dbus script.
Anyhow better, use User-session: A better way to start/stop applications is
to use "user sessions" (systemd --user) and not system-wide service, but didnt
change since it worked as before.
maybe this helps, comments are appreciated.
mfg
winfried
Am Dienstag, 1. Oktober 2019, 21:54:03 CEST schrieb Paul Davis:
On Tue, Oct 1, 2019 at 1:08 PM Steven Kruyswijk
<stevenkruyswijk(a)gmail.com>
wrote:
--
Ritsch, Winfried, Ao.Univ.Prof. Dipl.-Ing.
Institut 17 Elektronische Musik und Akustik
Inffeldgasse 10/III, 8010 Graz, Austria
E-Mail: ritsch(a)iem.at - http://iem.at/~ritsch - mobil ++436642439369
Ah... I only now realize that I need to utilize
jackd1. Raspbian comes
with
jackd2 as standard.
jack1 can't do anything that jack2 can't do (with respect to this problem).
it's just that the zalsa_{in,out} functionality is implemented as an
internal client in jack1, which makes it easier to invoke directly from the
command given to start the JACK server.
you can do the same thing using the separate zalsa_{inlout} clients with
jack2.