<html><body><div style="color:#000; background-color:#fff; font-family:arial, helvetica, sans-serif;font-size:12pt"><div><span><br></span></div><div><br></div> <div style="font-family: arial, helvetica, sans-serif; font-size: 12pt;"> <div style="font-family: times new roman, new york, times, serif; font-size: 12pt;"> <div dir="ltr"> <hr size="1"> <font face="Arial" size="2"> <b><span style="font-weight:bold;">From:</span></b> Kaj Ailomaa <zequence@mousike.me><br> <b><span style="font-weight: bold;">To:</span></b> pd-dev@iem.at <br> <b><span style="font-weight: bold;">Sent:</span></b> Wednesday, May 29, 2013 4:29 AM<br> <b><span style="font-weight: bold;">Subject:</span></b> Re: [PD-dev] jack dbus?<br> </font> </div> <div class="y_msg_container"><br><br><br>On Wed, May 29, 2013, at 09:17 AM, IOhannes m zmoelnig wrote:<br><br>>> <br>>> i dimly remember some discussion (on LAD, iirc) why having jack with<br>>> d-bus enabled by
default was a bad idea.<br>>> maybe things have improved since then.<br>>> <br>>> <br>>> > <br>>> >> one of the problems of Pd i see is, that all the audio backends<br>>> >> are linked into the main binary. so if you have a binary with<br>>> >> jack/dbus support, you *must* install jack/dbus or you will not<br>>> >> be able to use Pd at all (even if you don't care for audio at<br>>> >> all).<br>>> > <br><br>>I think the situation with jack is somewhat problematic, since there are<br>>now three variants of jack, where jack1 and jack2 both can be run as<br>>jackd - but jack1 and jack2 do not support the same stuff, and where<br>>jackdbus, while a form of jack2 is not operated the way jackd is.<br>>Perhaps it is a sign of an organizational problem within the jack<br>>community? I would really make things easier if there was only one
jack.<br>>From pd point of view, I suppose one could argue there is only two forms<br>>of jack: jackd and jackdbus - would that be correct?<br>>Where jackd could be either jack1 or jack2.<br><br>It makes no difference wrt development of Pd audio/midi backend for JACK<br>because the same backend can connect to JACK no matter which of the<br>above implementations is being used.<br><br>Thanks for the rest of what you wrote-- I will play with jackdbus a bit here on<br>Wheezy when I get a chance.<br><br>-Jonathan<br></div> </div> </div> </div></body></html>