Apart from the usual jackdbus addition, this release contains fix for the missing control.h file in the vanilla tarball. This release provides both the new jackd.py (D-Bus bound and available in the vanilla tarball) and jackdbus. Tarball containing D-Bus patched jack 0.120.2 is available here: http://nedko.arnaudov.name/soft/jack/dbus/ http://nedko.arnaudov.name/soft/jack/dbus/jack-audio-connection-kit-dbus-0.… http://nedko.arnaudov.name/soft/jack/dbus/jack-audio-connection-kit-dbus-0.… A patch against vanilla 0.121.0 is available here: http://nedko.arnaudov.name/soft/jack/dbus/jack-audio-connection-kit-0.121.0… http://nedko.arnaudov.name/soft/jack/dbus/jack-audio-connection-kit-0.121.0… After applying the patch you have to run autoreconf. D-Bus modifications add optional autodetected support for the D-Bus based server control system. D-Bus is object model that provides IPC mechanism. D-Bus supports autoactivation of objects, thus making it simple and reliable to code a "single instance" application or daemon, and to launch applications and daemons on demand when their services are needed. * Simplified single thread model for control and monitor applications. Various D-Bus language bindings make it trivial to write control and monitor applications using scripting languages like Python, Ruby, Perl, etc.. * JACK has log file (~/.log/jack/jackdbus.log) that is available for inspection even when autoactivation happens because of first JACK application is launched. * There is real configuration file used to persist settings that can be manipulated through configuration interface of JACK D-Bus object. * Improved graph inspection and control mechanism. JACK graph is versioned. Connections, ports and clients have unique (monotonically increasing) numeric IDs. * High level abstraction of JACK settings. Allows applications that can configure JACK to expose parameters that were not known at compile (or tarball release) time. Currently there are some minor differences between jack1 jackdbus and jack2 jackdbus: * There is no parameter constraints support (no enums and no ranges) * Settings file (in ~/.config/jack/) is conf-jack1.xml instead of conf.xml, because jack1 and jack2 settings and not really compatible. When configured with D-Bus support, jack_control is installed. jack_control is simple commandline interface for jackdbus. Other tools that can communicate with JACK through D-Bus: * LADItools (tray icon, configuration, etc.) * Patchage (and lpatchage too) * LASH 0.6.x * ladish * QJackCtl -- Nedko Arnaudov <GnuPG KeyID: 5D1B58ED>