2009/10/27 Jonathan E. Brickman <span dir="ltr">&lt;<a href="mailto:jeb@joshuacorps.org">jeb@joshuacorps.org</a>&gt;</span><br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">





<div bgcolor="#ffffff" text="#000000">
OK.  I have two theories.  The first is a question:<br>
<br>
1.  I know what libasound_module_pcm_jack.so does -- but what does <a href="http://libasound_module_pcm_jack.la" target="_blank">libasound_module_pcm_jack.la</a>
do?  It has been said that the ALSA2Jack plugin won&#39;t work at all
without the .la file, but it was working perfectly over here without
it.  Is the .la something Ubuntu-specific?  Or...?<br>
<br>
2.  Theory #2 is the better because it accounts for the fact that it
was working pretty well:  might the ALSA2Jack plugin have trouble
handling multiple streams at once?  If so, is there a streams-mixing
plugin I can use before ALSA2Jack, to make this work better?<br>
<br>
J.E.B.<br></div></blockquote><div><br></div><div>1) It has been said wrong. It&#39;s not that it doesn&#39;t work without the libtool file, but it&#39;s because what&#39;s being done is using the library (*.so) off of somewhere and not one which was meant and built for your system (differing versions). Libtool helped here by making sure libraries are properly linked.</div>

<div><br></div><div>Open up a *.la and you&#39;ll see what I mean.</div><div><br></div><div>2) No. Every alsa app registers a port with JACK when the plug-in is active. Those that don&#39;t are defective.</div></div>