LADI
/
jack-audio-connection-kit-docs
1
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

packaging.adoc: Add section about JACK server auto-start behaviour of libjack.so

This commit is contained in:
Nedko Arnaudov 2023-05-27 20:12:44 +03:00
parent fa680667a0
commit 158b3d2879
1 changed files with 6 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
packaging.adoc
View File

@ -73,3 +73,9 @@ All different releases of JACK should be considered internally incompatible - th
* ardour depends on "jack client library" and depends on "jackd" package, because it can start jack server through jackd binary.
* qjackctl if build without jackdbus support (unsupported scenario in LADI project) depends on "jack client library". If build with jackdbus, it depends on "jack server frontend" package. qjackctl can start jack server through either jackd or jackdbus binary.
* laditools depend on "jackdbus" only
== JACK server auto-start behaviour of libjack.so
While jackdbus can be configured with auto-start of JACK server (through jackdbus) and this will cause by creation of automatic studio in ladish, autolaunching is better to not be used in jack modular scenarios with ladish. Instead, initial auto-created studio can be achieved by starting jack server manually through "jack_control start".
In case ladish is not in effect, autos-tarting behaviour of libjack depends on packager's choice.