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...
--
On Sun, Dec 28, 2008 at 02:53:17PM +, Christian Weisgerber wrote:
> Jacob Meuser 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 ha
On Sun, 28 Dec 2008, Christian Weisgerber wrote:
> Jacob Meuser 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 ab
Jacob Meuser 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/a
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 t
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 termina
