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

packaging.adoc: Improve wording of qjackctl behaviour

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

6
packaging.adoc
View File

@ -45,10 +45,10 @@ Both D-Bus launcher (jackdbus executable) and classic launcher (jackd executable
* Pros:
** If D-Bus session bus gets misconfigured/non-functional, user is able to fallback to jackd, with its pros and cons.
** User can start the JACK server both through jackdbus and jackd (and thus through qjackctl too).
** User can start the JACK server both through jackdbus and jackd (and also through qjackctl when configured without jackdbus supoprt).
** Audio card negotiation with PulseAudio if and only if jackdbus is used.
* Cons:
** non-dbus aware tools (like qjackctl) or auto-launching will start jackd, associated with:
** non-dbus aware tools (like qjackctl when configured without jackdbus support) or auto-launching will start jackd, associated with:
*** User is blind about what happens with JACK server execution if jackd is autolaunched.
*** No JACK D-Bus aware control/monitor applications can be used. They will claim JACK server is not started (cannot be contacted) even when JACK server is actually running and normal JACK applications are connected and probably using it.
*** PulseAudio will not know whether JACK server is running
@ -71,5 +71,5 @@ All different releases of JACK should be considered internally incompatible - th
* app that uses jack as only audio interfaces, (jack_keyboard for example), depends on "jack client library" package and on the "jack server frontend" virtual package
* app that uses jack as alternative (not the only) audio interface, (mplayer for exmaple), depends on "jack client library" and suggests "jack server frontend" virtual package
* ardour depends on "jack client library" and depends on "jackd" package, because it can start jack server through jackd binary.
* qjackctl depends on "jack client library" and depends on "jack server frontend" package, because it can start jack server through either jackd or jackdbus 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