Another Potential Slave... I mean Programmer
I am considering writing a Wine Driver for esd. I am wondering basically where I start. I know esd is high latency (which may not be the best for such a thing), but I think it would be easier than trying to do alsa drivers. (I know ALSA has oss compatible drivers, but I can't get them to do a thing under wine... do work uner other programs.) Anyways, that leads me to here and me trying to help. Joe Tennies
I am considering writing a Wine Driver for esd. I am wondering basically where I start.
I'm not trying to start a Gnome/KDE flame war, but as far as I know, esd is unmaintained and the Gnome developpers are thinking about switching to aRtsd. Wouldn't it be more useful to write an aRts driver ? Laurent Pinchart
I'm not trying to start a Gnome/KDE flame war, but as far as I know, esd is unmaintained and the Gnome developpers are thinking about switching to aRtsd. Wouldn't it be more useful to write an aRts driver ?
Actually if I'm not mistaken - GNOME people are moving to gstreamer, if I'm not mistaken. I'm not sure since I work with KDE here... Hetz
On Sat, 2002-02-02 at 05:42, Hetz Ben Hamo wrote:
I'm not trying to start a Gnome/KDE flame war, but as far as I know, esd is unmaintained and the Gnome developpers are thinking about switching to aRtsd. Wouldn't it be more useful to write an aRts driver ?
Actually if I'm not mistaken - GNOME people are moving to gstreamer, if I'm not mistaken. I'm not sure since I work with KDE here...
Hetz
Actually, I just looked at gstreamer. It lies above aRts, esd, alsa, and oss. It is a platform independent (well, not ported to everything yet, but working on it) system. I think KDE SHOULD be heading this way and am impressed that GNOME is. I think that gstreamer would be the way to go for WINE.
On Sat, Feb 02, 2002 at 02:14:08PM -0600, Joe Tennies wrote:
On Sat, 2002-02-02 at 05:42, Hetz Ben Hamo wrote:
I'm not trying to start a Gnome/KDE flame war, but as far as I know, esd is unmaintained and the Gnome developpers are thinking about switching to aRtsd. Wouldn't it be more useful to write an aRts driver ?
Actually if I'm not mistaken - GNOME people are moving to gstreamer, if I'm not mistaken. I'm not sure since I work with KDE here...
Hetz
Actually, I just looked at gstreamer. It lies above aRts, esd, alsa, and oss. It is a platform independent (well, not ported to everything yet, but working on it) system. I think KDE SHOULD be heading this way and am impressed that GNOME is. I think that gstreamer would be the way to go for WINE.
Layer after layer after layer... Are there any particular reasons that the authors of gstreamer believe that all of the existing audio APIs are unacceptable, or is this yet another case of the NIH syndrome that GNOME and KDE developers seem to suffer from all too frequently? And if there are problems with the existing APIs, what reason do we have to think that gstreamer will get it right? If people have issues with the existing sound daemons, their time could almost certainly be better spent working on the implementations /behind/ the APIs instead of creating the sound library du jour. It seems a terrible waste of programmer time to try to maintain as many as four library layers interposed between Wine programs and the audio hardware. Steve Langasek postmodern programmer
On Sat, Feb 02, 2002 at 03:52:32PM -0600, Steve Langasek wrote:
If people have issues with the existing sound daemons, their time could almost certainly be better spent working on the implementations /behind/ the APIs instead of creating the sound library du jour. It seems a terrible waste of programmer time to try to maintain as many as four library layers interposed between Wine programs and the audio hardware.
IIRC, gstreamer is a audio video framework, that provides data in and *synchronized* audio and video out. So you should not compare it with esound, alsa etc but with xine-lib or something like that. They just provide autio out for those drivers. ciao Jörg -- Joerg Mayer <jmayer(a)loplof.de> I found out that "pro" means "instead of" (as in proconsul). Now I know what proactive means.
Yeah, aRtsD can run stand alone without KDE. I do believe artsd is superior to esd in that the output doesn't sound like a scratchy shortwave radio. On my machine, aRtsD does have slightly more overhead (according to top), but it's hardly noticeable on my box. --- Derek. On Sun, 3 Feb 2002, Laurent Pinchart wrote:
I am considering writing a Wine Driver for esd. I am wondering > basically where I start.
I'm not trying to start a Gnome/KDE flame war, but as far as I know, esd is unmaintained and the Gnome developpers are thinking about switching to aRtsd. Wouldn't it be more useful to write an aRts driver ?
Laurent Pinchart
According to the gnome plan, they are still using esound for 2.0. So I guess that means... esd still? On Sun, 2002-02-03 at 05:32, Laurent Pinchart wrote:
I am considering writing a Wine Driver for esd. I am wondering basically where I start.
I'm not trying to start a Gnome/KDE flame war, but as far as I know, esd is unmaintained and the Gnome developpers are thinking about switching to aRtsd. Wouldn't it be more useful to write an aRts driver ?
Laurent Pinchart
participants (6)
-
Derek Witt -
Hetz Ben Hamo -
Joe Tennies -
Joerg Mayer -
Laurent Pinchart -
Steve Langasek