Pulse may be some people's idea of the wave of the future, but Speakup users aren't the only ones who find pulse very problematic. Also in this category are: * People who do professional level work with audio composition. * These folks use jack, not pulseaudio. Jack was rejected for use * as a mainstream approach because it wasn't sufficiently * lightweight. I'll leave for others to judge whether pulse is * actually lightweight I've had conversations with Planet CCRMA people, for instance, so that I can categorically report that pulse is removed from all their computers at Stanford University. It only gets in the way. http://ccrma.stanford.edu/planetccrma/software/ * People running games, where latency really matters. Of course, * latency also matters to us. This second point may be an architectural failure on the part of pulse. Well, what can I say? They never asked our requirements before they designed and implemented pulse, so how can it be assumed that our requirements are met? It's the old: "Nothing about us without us" that got violated again. Janina John G. Heim writes: > I'm no expert in this area but don't you guys worry that you are > trying to hold back the ocean with a teaspoon? You can't fight the > march of technology. If pulse is the wave of the future, I would > tend to want to get started working with it rather than tossing it > aside. > > I just started working with sonar linux last week. I put it on my > backup desktop at work. In my limited testing up to this point, it > seems to be rock solid. I plan to continue trying it on my backup > workstation at work and on my machine at home for a few more days > before converting the machine I use to earn my bread and beer. > > I can understand an attitude of saying that you need to postpone an > upgrade because the technology just isn't there yet. That's why I'm > typing this message on a machine still running debian squeeze. But > as soon as I am sure I can switch to a newer distro that works, I'm > doing it. > > On 11/30/13 22:38, Janina Sajka wrote: > >Yes, screen rocks! > > > >I do keep the gui, mainly for firefox even though it requires that I use > >a second audio device. > > > >Everything else is tty's and screen terminals. About half of my tty's > >launch subject specific screen sessions with multiple terminals. In all > >of those, I have aliases for mplayer to talk to several additional audio > >devices, or ecaplay, or aplay. All works like a charm. > > > >Janina > > > >Doug Smith writes: > >> > >> > >>I really have quit a bit to say here. I have also terminated pulse with extreme prejudice on this system. I have also terminated the entire > >>graphical user interface with the same finality. I am using debian testing without the desktop on it. > >> > >>The way it works is that, when you use the text-based installer to install the system, it uses alsa for the sound. I have speakup system wide and I > >>have a fully functioning sound system on here that performs perfectly. I can use multiple audio sources, and I have nothing to worry about because I > >>do not have to, if I do not want to, switch between consoles. Where it works well, I just use screen and there is no problem for me to play my > >>descriptive movie, program and whatever else all at once. > >> > >> > >> > >>Hope this helps. > >> > >> > >> > >> > >>-- > >>Doug Smith: Special Agent > >>S.W.A.T Spiritual Warfare and Advanced Technology > >>Forever serving our LORD and SAVIOUR, JESUS CHRIST. > >> > >>_______________________________________________ > >>Speakup mailing list > >>Speakup at linux-speakup.org > >>http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup > > > > -- > --- > John G. Heim, 608-263-4189, jheim at math.wisc.edu -- 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/
