12:59 a.m.
With alsa 1.0.9rc3, dmix is enabled by default and it works (with
gstreamer too).
There are several applications which depend on esound which seems weird,
as I thought these use gstreamer:
libesd.so.0 is needed by (installed) nautilus-2.10.0-3.i386
libesd.so.0 is needed by (installed) gnome-media-2.10.0-2.i386
libesd.so.0 is needed by (installed) gok-1.0.3-1.i386
libesd.so.0 is needed by (installed)
control-center-2.10.0-4.i386
libesd.so.0 is needed by (installed) smpeg-0.4.4-9.i386
libesd.so.0 is needed by (installed) libgnome-2.10.0-2.i386
libesd.so.0 is needed by (installed) gnome-session-2.10.0-2.i386
esound >= 1:0.2.27 is needed by (installed)
libgnomeui-2.10.0-1.i386
Should I file upstream bugs for these to remove direct esound depencies
and require only gstreamer?
These depencies seem ok to me until esound is dropped, as these are
sound systems:
libesd.so.0 is needed by (installed) arts-1.4.0-1.i386
libesd.so.0 is needed by (installed)
gstreamer-plugins-0.8.8-5.i386
Note1: alsa-lib 1.0.9rc3 will be in updates soon, now only at
http://people.redhat.com/stransky/alsa-lib/
Note2: dmix doesn't solve "sound over network" problem. This still
requires a sound server (e.g. MAS, Jack, esd), but the sound server can
be implemented at gstreamer framework level, not application level.
--
Marius Andreiana
5:10 a.m.
Hi,
On Wed, 2005-05-04 at 07:59, Marius Andreiana wrote:
There are several applications which depend on esound which seems
weird,
as I thought these use gstreamer:
libesd.so.0 is needed by (installed) nautilus-2.10.0-3.i386
libesd.so.0 is needed by (installed) gnome-media-2.10.0-2.i386
[..]
esound >= 1:0.2.27 is needed by (installed)
libgnomeui-2.10.0-1.i386
[..]
Should I file upstream bugs for these to remove direct esound
depencies
and require only gstreamer?
No. The only actual dependency is in libgnome/&ui, and the others solely
depend on esd because libgnome/&ui do. The libgnome/&ui people are aware
of the problem and may at some point be ported to GStreamer; the problem
isn't so much the patching itself, because patches are available, but
the amount on which we want to drop an unstable API of a huge library
into the GNOME developer platform (*). Once ported, that will remove the
esd dependency from the others, too.
Ronald
(*) that doesn't mean it won't be accepted; it just means it'll take
some time. ;).
--
Ronald S. Bultje <rbultje(a)ronald.bitfreak.net>
8:37 a.m.
On Wed, 04 May 2005 12:10:28 +0200, Ronald S. Bultje wrote:
No. The only actual dependency is in libgnome/&ui, and the others
solely
depend on esd because libgnome/&ui do.
In other words building with --as-needed would eliminate most of those
esound dependencies. Unfortunately esound is exposed in libgnome so cannot
be dropped unless a fully compatible replacement is produced. But that's
no big deal. Esound isn't that large.
thanks -mike
9:36 a.m.
On Wed, 2005-05-04 at 14:37 +0100, Mike Hearn wrote:
On Wed, 04 May 2005 12:10:28 +0200, Ronald S. Bultje wrote:
> No. The only actual dependency is in libgnome/&ui, and the others solely
> depend on esd because libgnome/&ui do.
Unfortunately esound is exposed in libgnome so cannot
be dropped unless a fully compatible replacement is produced. But that's
no big deal. Esound isn't that large.
Quoting Marius Andreiana ...
"Note2: dmix doesn't solve "sound over network" problem. This still
requires a sound server (e.g. MAS, Jack, esd), but the sound server can
be implemented at gstreamer framework level, not application level."
gnome has an esound replacement, gstreamer. gstreamer is what needs to
talk to a network audio server.
thanks -mike
6956
days inactive
6956
days old
3 comments
4 participants
participants (4)
-
Marius Andreiana -
Matthew Lenz -
Mike Hearn -
Ronald S. Bultje