<div class="gmail_quote">2010/10/14 Stephen Sinclair <span dir="ltr"><<a href="mailto:sinclair@music.mcgill.ca" target="_blank">sinclair@music.mcgill.ca</a>></span><br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
Afaik there tends to be a lot of mixed appreciation of PulseAudio; at<br>
least on the Linux Audio Developer list, it seems to be a point of<br>
contention. Personally I don't find it affects my usage of the OS<br>
very much, although maybe it does things in the background that I'm<br>
not always aware of. (Like mixing outputs of different applications.)<br></blockquote><div><br>My main motivation was that with the ALSA and Jack backends, as far as I know, you can't have two instances of stk applications running, or any program using the soundcard and an stk application. <br>
For example, if you run two instances of projects/examples/crtsine, you get:<br><br>RtApiAlsa::getDeviceInfo: snd_pcm_open error for device (hw:0,0), Device or resource busy.<br>RtApiAlsa::probeDeviceOpen: pcm device (hw:0,0) won't open for output.<br>
<br>In other frameworks (for example GStreamer's ALSA and Jack plugins), this is not the case. It could just be a simple matter of improving RtApiAlsa and RtApiJack, rather than implementing a whole other backend. I think this would enhance Stk's overall usability tremendously.<br>
<br></div></div>-- <br>Tristan Matthews<br>email: <a href="mailto:tristan@sat.qc.ca" target="_blank">tristan@sat.qc.ca</a><br>web: <a href="http://tristanswork.blogspot.com" target="_blank">http://tristanswork.blogspot.com</a><br>