On Sat, Dec 27, 2008 at 04:48:44PM +0000, 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
