<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 11:32 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>>i have two things:<br>>- - code (API+ implementation) that adds support for pluggable<br>>audio/midi backends<br>>- - converted all the existing backends to use the new
API (though they<br>>are still linked statically into the Pd-binary)<br><br>What did you have to convert?<br><br>Also-- you mentioned people had tested Portaudio as pluggable backend.<br>Have you tested using a known configuration (like with the ALSA backend)<br>with your changes?<br><br>>the code was only updated to Pd-0.43, and i haven't updated it to Pd-0.44.<br><br>>> Does the backend have to be written differently than the<br>>> s_audio_*.c stuff to be pluggable?<br><br>>not really<br>.<br>>the idea was to have an API that builds on top of the current<br>>implementation of s_audio_... (which is pretty consistent throughout<br>>the various backends)<br><br>>so it's mainly adding a few wrapper functions that register a given<br>>backend to the core.<br><br>>you can have a look at it at [1]<br><br>Thanks, I'll check it out.<br><br>-Jonathan<br><br></div> </div> </div> </div></body></html>