Hi, If there's a way to avoid this situation, I haven't found it. I console myself that the Speakup Connector isn't the only ill behaved audio application in this regard, but I'll spare us all chapter and verse on that topic. Suffice it to say that I now require a minimum of two audio devices to run screen reader support on Linux, one for Speakup and one for Orca. A third is minimal for other audio apps, imo. PS: One example of other hoggy apps would be Fluidsynth with aconnect. Janina Rob Hudson writes: > This really works amazingly well and I love it. However... > This does not seem to play well with pulse audio. When I run it, it hogs the entire > sound card to itself, causing me to have to switch the desktop to a different sound > card. Now this probably is not a big deal since I do in fact have other cards to > switch to, but is there a way to prevent it hogging the entire card to itself? > _______________________________________________ > Speakup mailing list > Speakup at linux-speakup.org > http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup -- Janina Sajka, Phone: +1.443.300.2200 sip:janina at asterisk.rednote.net Email: janina at rednote.net Linux Foundation Fellow Executive Chair, Accessibility Workgroup: http://a11y.org The World Wide Web Consortium (W3C), Web Accessibility Initiative (WAI) Chair, Protocols & Formats http://www.w3.org/wai/pf Indie UI http://www.w3.org/WAI/IndieUI/
