<br><div class="gmail_quote">On Fri, Apr 18, 2008 at 4:13 AM, schoappied <<a href="mailto:schoappied@gmail.com">schoappied@gmail.com</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="Ih2E3d">Rui Nuno Capela wrote:<br>
> schoappied wrote:<br>
>> Hi all,<br>
>><br>
>><br>
>> I have trouble with apps who only show up in jack connections when<br>
>> they start to play, eg VLC, audacity...<br>
>><br>
>> I'm not able to save the settings in the patchbay and make it active....<br>
>><br>
><br>
> that's just because those apps only open as jack clients when play is<br>
> hit.<br>
</div>I've tried alsaplayer and that app seems to show up directly in qjackctl<br>
and patchage (or it will stay as a jack client when the song in the<br>
player has come to an end.)<br>
So it must be possible for other apps (audacity, rezound, vlc) too,<br>
isn't it?<br>
<div><div></div><div class="Wj3C7c">_</div></div></blockquote><div><br>I think this is because, when your app is using oss or alsa, the
friendly thing to do is to stop using the sound card (since using the
sound card blocks other applications that would like to use it), and it
is easier to plug in your calls to the jack api in the same place as
the oss or alsa api calls, than it is to change your
connection/disconnection policy based on api.<br><br><br> </div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div><div class="Wj3C7c">______________________________________________<br>
Linux-audio-user mailing list<br>
<a href="mailto:Linux-audio-user@lists.linuxaudio.org">Linux-audio-user@lists.linuxaudio.org</a><br>
<a href="http://lists.linuxaudio.org/mailman/listinfo/linux-audio-user" target="_blank">http://lists.linuxaudio.org/mailman/listinfo/linux-audio-user</a><br>
</div></div></blockquote></div><br>