Hello, Kevin: I'm responding because I'm pursuing a similar set of concerns in similar circumstances. I am a Speakup and an Orca user (console and gui screen readers). However, I have little recent jack experience as I'm just now getting back into music-making on Linux. I can tell you that it's possible to run both Speakup and Orca without pulseaudio. Perhaps that might help? It might be worth a test, in any case. More details on my setup, if you ask. My current goal is to discover how to enable pulseaudio, but to restrict it to a particular device only. I want to do this because the preferred Orca environment is to run with pulseaudio--though, afaik, all one loses without it are the earcons. In any case, I certainly don't want pulseaudio to have access to all my devices, just as I don't want jack running on the audio devices I use for Speakup and for Orca (two separate devices, unfortunately, because of driver compatibility issues). In any case, this is a moderate priority project at the moment for me, so I do spend time on it as I have time. So far I have come to believe it would be possible to restrict pulseaudio either via its client.config or in udev, but I haven't tried any of this yet. Janina Kevin Utter writes: > Hi all. I hope this hasn't already been covered, but I've been searching the internet and can't find answers yet. > > I'm running Ubuntu 12.10 which came with PulseAudio. I chose Jack2 as I have a newer system, I believe with multi-processor support, and I understood it might cooperate with PulseAudio better. I use braille and speech for the screen reader, which is currently routed through PulseAudio. And I want to use Jack through the command line rather than through Qjackctl gui. I used to do this on my older Ubuntu system with Jack1, but things have changed quite a bit since then. Jack2, Jackdbus, and module-jackdbus-detect seem to be working. PulseAudio seems to be re-routing. I don't have Jack running at startup, as I always used to start it manually, and so I could re-start it when necessary. I currently start it with "jack_control start". When I do, "jack_lsp" shows jack ports, but my old friend jackctl.py won't show any ports or make connections. Running "jackd" as I used to seems to generate errors about not being able to start the server. I don't have specifics in front of me, b > ut I can come back with them if it helps. I used to use ~/bin/j.ctl to start jack with the appropriate parameters I believe from ~.jackrc, but that looks as if it relies on something like jack.ctl which no longer exists. > > So after all the details here, I'm wondering if I should have gone with Jack1 instead, and found some way of doing without PulseAudio, or if my current Jack2 needs to run without Dbus support, and whether I need a newer jackctl.py if one exists? Or are there other things I should be doing? I'm sorry, but I feel just a little lost here. I know just enough to be dangerous, but not quite enough to know how to fix it. > > Thanks for any help. I'm sorry to be so long winded, but I thought the details might be necessary to know why I'm doing what I'm doing. Any suggestions would be greatly appreciated. Thank you again very much. > > Kevin > > _______________________________________________ > Linux-audio-user mailing list > Linux-audio-user@xxxxxxxxxxxxxxxxxxxx > http://lists.linuxaudio.org/listinfo/linux-audio-user -- Janina Sajka, Phone: +1.443.300.2200 sip:janina@xxxxxxxxxxxxxxxxxxxx Email: janina@xxxxxxxxxxx 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/ _______________________________________________ Linux-audio-user mailing list Linux-audio-user@xxxxxxxxxxxxxxxxxxxx http://lists.linuxaudio.org/listinfo/linux-audio-user
