<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> IOhannes m zmoelnig <zmoelnig@iem.at><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 3:17 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>>> <br>>>> personally i would prefer to *not* pull in additional<br>>>> dependencies if possible. afair, d-bus is notorious for pulling<br>>>> in an
entire desktop environment.<br>>> <br>>> it does not depend on an entire desktop environment.<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>Probably.<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>>> I must be reading different documentation than you because AFAICT <br>>> jack d-bus is a user-facing option for how to get JACK to interact<br>>> with the system. Recommending it as the preferred way to connect<br>>> doesn't require any backend
coding.<br><br>>maybe it's not clear from what i've written so far: i personally do<br>>not use jack/d-bus (or i am not aware of it).<br>>i was under the impression that it would require some linking against<br>>a different libjack, but it seems like that is all wrong.<br>><br>>obviously i have absolutely no problems against *recommending* a given<br>>setup that works with the given Pd-binaries.<br><br>>sorry if i gave the wron impression<br><br>>> That's a fine goal, as it would solve the problem about requiring<br>>> JACK/ALSA dependencies even if the user doesn't want audio. But<br>>> given a limited amount of time and money,<br><br>>well i have done a prototype of said plugable audio (and midi) backend<br>>support for Pd-0.43, and it's available on github.<br><br>>code was only tested on linux and some users reported problems with<br>>the portaudio backend (which i had problems to
reproduce, since i<br>>never use the portaudio backend (as it comes with Pd-vanilla) since i<br>>cannot remember that it ever worked for me...but then i didn't try<br>>that often after initial disappointments, being quite happy with what<br>>alsa and jack had to offer directly)<br><br>Ok, sounds like you have two things: a) code that adds support for<br>pluggable audio/midi backends, and b) a pluggable portaudio backend.<br><br>Does the backend have to be written differently than the s_audio_*.c stuff<br>to be pluggable?<br><br>-Jonathan<br><br>fgnsdart#<br>IOhannes<br>-----BEGIN PGP SIGNATURE-----<br>Version: GnuPG v1.4.12 (GNU/Linux)<br>Comment: Using GnuPG with Icedove - <a href="http://www.enigmail.net/" target="_blank">http://www.enigmail.net/</a><br><br>iEYEARECAAYFAlGlq20ACgkQkX2Xpv6ydvRgHgCfSz2SN0ZOaN0IerBPxfeqExLD<br>1ywAnj6AI9rpWupkl61sO/ta08mHN3PY<br>=FmUR<br>-----END PGP
SIGNATURE-----<br><br>_______________________________________________<br>Pd-dev mailing list<br><a ymailto="mailto:Pd-dev@iem.at" href="mailto:Pd-dev@iem.at">Pd-dev@iem.at</a><br><a href="http://lists.puredata.info/listinfo/pd-dev" target="_blank">http://lists.puredata.info/listinfo/pd-dev</a><br><br><br></div> </div> </div> </div></body></html>