[LAD] Proposal about support for multiple jack-dbus servers

Zlobin Nikita cook60020tmp at mail.ru
Fri Feb 7 18:33:39 UTC 2014

I looked to MPRIS specification in order to write jack transport client with 
this interface, and noticed solution, which could be used for jackdbus too.

Currently jack serice name is fixed: org.jackaudio.service
In MPRIS naming is like <prefix string>.<instance name> (e.g. 

For jack it could have this form: org.jackaudio.<server name> or 
org.jackaudio.service.<server name>. Older name may be kept for compatibility, 
and most likely to be created by first jack server, appearing in user session.

With such approach it could be possible for other daemons, e.g. ladish, to 
expose jack-like interfaces in more common way.

Of course, currently it is done as essential (using of different service 
names), but it is not standard. With proposed approach it may be possible even 
to browse jack services. Control tools like qjackctl could even propose some 
menu (sidebar in patchage) or even (sic! =) transport control rack for better 

More information about the Linux-audio-dev mailing list