Re: audio/esound breakage
Jacob Meuser jake...@sdf.lonestar.org wrote: just curious, what ports actually *need* esound? I would be willing to convert them to sndio so we can toss this garbage in the dumpster where it belongs. For me, esound's attraction has always been the ability to carry audio over the network. That's something sndio/aucat can't do (yet?). But since I have now for several years been unable to get this to work on the occasions I tried, I'm not feeling the esound love any more. Firefox has an esound run dependency whose use I don't know. GNOME used to rely on esound as a multiplexer; I don't know what's up with that nowadays. -- Christian naddy Weisgerber na...@mips.inka.de
Re: audio/esound breakage
On Sun, 28 Dec 2008, Christian Weisgerber wrote: Jacob Meuser jake...@sdf.lonestar.org wrote: just curious, what ports actually *need* esound? I would be willing to convert them to sndio so we can toss this garbage in the dumpster where it belongs. For me, esound's attraction has always been the ability to carry audio over the network. That's something sndio/aucat can't do (yet?). But since I have now for several years been unable to get this to work on the occasions I tried, I'm not feeling the esound love any more. Firefox has an esound run dependency whose use I don't know. GNOME used to rely on esound as a multiplexer; I don't know what's up with that nowadays. GNOME is totally fine without esound now. It is even recommended not to use it anymore. -- Antoine
Re: audio/esound breakage
On Sun, Dec 28, 2008 at 02:53:17PM +, Christian Weisgerber wrote: Jacob Meuser jake...@sdf.lonestar.org wrote: just curious, what ports actually *need* esound? I would be willing to convert them to sndio so we can toss this garbage in the dumpster where it belongs. For me, esound's attraction has always been the ability to carry audio over the network. jack has network support, and new versions supports CELT. supposedly it's reliable enough that it can even be used over DSL. Firefox has an esound run dependency whose use I don't know. I'm not opposed to keeping things around if they are *needed*. but we don't need 4 different audio backends in every port. -- jake...@sdf.lonestar.org SDF Public Access UNIX System - http://sdf.lonestar.org
Re: audio/esound breakage
On Sun, 28 Dec 2008, Jacob Meuser wrote: Firefox has an esound run dependency whose use I don't know. I'm not opposed to keeping things around if they are *needed*. but we don't need 4 different audio backends in every port. Esound should RIP IMHO. And yes, I used to only use esd... -- Antoine
Re: audio/esound breakage
On Sat, Dec 27, 2008 at 04:48:44PM +, Christian Weisgerber wrote: What works: * Playing audio through the local Unix domain socket. esd esdplay foo.wav What doesn't work: * Playing over the network. esd -tcp esdplay -s localhost foo.wav This terminates immediately without sound. I've tried a number of variations: using ESPEAKER instead of -s, using the numeric address 127.0.0.1, specifying port 16001, adding -promiscuous when starting esd, removing ~/.esd_auth. None of this has any effect. ktracing esdplay shows that it reads ~/.esd_auth, writes the contents to a network socket, and exits. * I can't get a startup beep. esd -beeps Doesn't beep. I know -nobeeps is very popular, but when testing it's nice to have confirmation that audio is actually routed to your speakers/headphones. hmm, seems like the update broke this. at least -beeps was working with the sndio backend. I didn't test networking. just curious, what ports actually *need* esound? I would be willing to convert them to sndio so we can toss this garbage in the dumpster where it belongs. -- jake...@sdf.lonestar.org SDF Public Access UNIX System - http://sdf.lonestar.org
Re: audio/esound breakage
On Sat, Dec 27, 2008 at 09:58:43PM +, Jacob Meuser wrote: On Sat, Dec 27, 2008 at 04:48:44PM +, Christian Weisgerber wrote: What works: * Playing audio through the local Unix domain socket. esd esdplay foo.wav What doesn't work: * Playing over the network. esd -tcp esdplay -s localhost foo.wav This terminates immediately without sound. I've tried a number of variations: using ESPEAKER instead of -s, using the numeric address 127.0.0.1, specifying port 16001, adding -promiscuous when starting esd, removing ~/.esd_auth. None of this has any effect. ktracing esdplay shows that it reads ~/.esd_auth, writes the contents to a network socket, and exits. * I can't get a startup beep. esd -beeps Doesn't beep. I know -nobeeps is very popular, but when testing it's nice to have confirmation that audio is actually routed to your speakers/headphones. hmm, seems like the update broke this. at least -beeps was working with the sndio backend. I didn't test networking. just curious, what ports actually *need* esound? I would be willing to convert them to sndio so we can toss this garbage in the dumpster where it belongs. well, this is intersting: http://ftp.gnome.org/pub/gnome/sources/esound/0.2/esound-0.2.41.changes all those went in on the same day? if so, not surprised some things got broken. hmmm ... Do never play beeps when esd has just been spawned. -- jake...@sdf.lonestar.org SDF Public Access UNIX System - http://sdf.lonestar.org
