ANNOUNCE: BEAST/BSE v0.5.1

Tim Janik <timj <at> gtk.org>
2003-04-13 23:06:07 GMT

BEAST/BSE version 0.5.1 is available for download at:
ftp://beast.gtk.org/pub/beast/v0.5
or
http://beast.gtk.org/beast-ftp/v0.5
BEAST (the Bedevilled Audio SysTem) is a graphical front-end to
BSE (the Bedevilled Sound Engine), a library for music composition,
audio synthesis and sample manipulation. The project is hosted at:
http://beast.gtk.org
This new development series of BEAST comes with a lot of
the internals redone, many new GUI features and a sound
generation back-end separated from any GUI activities.
Note, the .bse file format hasn't completely stabilized yet,
so incompatibilities with future versions may occur.
Overview of Changes in BEAST/BSE 0.5.1:
* Added support for LADSPA plugins
* Improved synthesis network router display
* Documentation fixes
* Added support for dsp[0-3] and midi[0-3] devices
* Fixed memory leaks during playback
---
ciaoTJ

GStreamer "Proven to be true" 0.6.1 released

GStreamer "Proven to be true" 0.6.1 released
The GStreamer team is proud to announce an updated version in the
ABI-stable 0.6.x series, which features many bugfixes and some feature
improvements over the previous 0.6.0 release.
At this point in time GStreamer is fully functional for creating
audio-based applications, as shown by applications such as
gnome-sound-recorder, net-rhythmbox, sound-juicer and nautilus-media.
The video part is known to be somewhat less functional than the audio
part, but applications such as gst-player works very well, and a port of
Totem is in progress in GNOME CVS.
We will also be releasing a development 0.7 release series, in which we
will work on such things as the remaining issues, such as the
interactivity support which is needed for DVD menus and SWF (Flash).
This means developers working on apps needing these services can use the
0.7 series for development and then enable 0.6 support as these
additions optionally get backported to 0.6 once they are stable and work
well.
The GStreamer applications we ship all check for both gstreamer-0.6,
gstreamer-libs-0.6 and gstreamer-play-0.6; if those aren't found the 0.7
version of those files are checked for. We suggest anyone making
GStreamer-based apps do the same.
We are starting to have a really nice collection of applications under
development using GStreamer. If you are looking for something specific
check out our growing applications status page:
http://gstreamer.net/status/?category=2

GStreamer plans and TODO

Hi,
Hi 0.6.1 out there door I felt it was time to think aloud on what we
want to do in moving GStreamer and particularly the 0.6.x series
forward. I am sending this both to GStreamer-devel, but also to
gnome-multimedia and gnome-love since many of the integration tasks
should be rather good projects to get started on for people who hasn't
worked so much with GStreamer before.
This list will probably be converted into a updated TODO page on
gstreamer.net, so anyone who has any comments and additions be sure to
speak up.
So as mentioned this list is an attempt to put together the most
important pieces we need to get into GStreamer 0.6.x and GNOME 2.x
series for it to provide maximum service to the applications that people
use with it. This list is put together with the needs of these
applications in mind:
Gst-player and Totem
Sound Juicer
GNOME Media
Nautilus/Nautilus-Media
Rhythmbox,Net-rhythmbox, Lymric
Marlin
GStreamer plugins that needs fixing for gst-player/totem:
Make auparse work in gst-player
Make flxdec work in gst-player
Make Make swfdec work in gst-player
Make audiofile plugin work so it can provide aiff support to player, or
make an aiffparse plugin

Re: [gnome-love] GStreamer plans and TODO

Bastien Nocera <hadess <at> hadess.net>
2003-04-19 13:34:23 GMT

On Sat, 2003-04-19 at 11:19, Christian Fredrik Kalager Schaller wrote:
> Hi,
> So as mentioned this list is an attempt to put together the most
> important pieces we need to get into GStreamer 0.6.x and GNOME 2.x
> series for it to provide maximum service to the applications that people
> use with it. This list is put together with the needs of these
> applications in mind:
> Gst-player and Totem
> Sound Juicer
> GNOME Media
> Nautilus/Nautilus-Media
> Rhythmbox,Net-rhythmbox, Lymric
> Marlin
Happy to see that Totem is on the map now :)
> GStreamer plugins that needs fixing for gst-player/totem:
> Make auparse work in gst-player
> Make flxdec work in gst-player
> Make Make swfdec work in gst-player
> Make audiofile plugin work so it can provide aiff support to player, or
> make an aiffparse plugin
>
> Hook up ffmpeg decoders for WMA, Quicktime, Real and ASF
That's an afternoon's job for a clueful person. Real and ASF would need
demuxer before they're actually any use.
<snip>

Re: [gnome-love] GStreamer plans and TODO

Bastien Nocera <hadess <at> hadess.net>
2003-04-19 13:55:22 GMT

On Sat, 2003-04-19 at 14:45, iain wrote:
> On Sat, 2003-04-19 at 14:34, Bastien Nocera wrote:
>
> > Output should be autodetected, and capplets scrapped. ("Just work")
>
> I think I've already given an example about why that doesn't work.
And I've already explained that a hidden configuration option was good
enough for those 1% that need to work around crappy drivers, or bugs in
the sound output plugins/frameworks.
--
--
Bastien Nocera <hadess <at> hadess.net>

Re: [gnome-love] GStreamer plans and TODO

Jeff Waugh <jdub <at> perkypants.org>
2003-04-19 13:58:51 GMT

<quote who="Bastien Nocera">
> On Sat, 2003-04-19 at 14:45, iain wrote:
> > On Sat, 2003-04-19 at 14:34, Bastien Nocera wrote:
> >
> > > Output should be autodetected, and capplets scrapped. ("Just work")
> >
> > I think I've already given an example about why that doesn't work.
>
> And I've already explained that a hidden configuration option was good
> enough for those 1% that need to work around crappy drivers, or bugs in
> the sound output plugins/frameworks.
And for the sake of the argument, a distributor would pretty much grok all
of the variables in their sound support stuff anyway, and will be able to
deal with any strange needs on their platform ahead of time. Things may not
"just work" for people who use odd compilations of crap, but then, they are
most likely capable of setting it up correctly for themselves.
- Jeff
--
--
GU4DEC: June 16th-18th in Dublin, Ireland http://www.guadec.org/
"I can't imagine anyone telling Emma Bunton to shut up. It would be
rather like slapping Bambi."

Re: GStreamer plans and TODO

iain <iain <at> prettypeople.org>
2003-04-19 14:06:41 GMT

On Sat, 2003-04-19 at 14:55, Bastien Nocera wrote:
> On Sat, 2003-04-19 at 14:45, iain wrote:
> > On Sat, 2003-04-19 at 14:34, Bastien Nocera wrote:
> >
> > > Output should be autodetected, and capplets scrapped. ("Just work")
> >
> > I think I've already given an example about why that doesn't work.
>
> And I've already explained that a hidden configuration option was good
> enough for those 1% that need to work around crappy drivers, or bugs in
> the sound output plugins/frameworks.
I said it wasn't a driver issue or a bug in the sound output
plugins/frameworks. Its a simple case that my soundcard simply does not
handle certain (common) audio formats.
Other reasons why a capplet might be useful, given a system with OSS,
Alsa, ARTS, ESD, MAS installed, how does one automagically decide which
to use?
iain
--
--
"Miss Celine Dion sings lovesongs while our cities burn"

Re: GStreamer plans and TODO

Bastien Nocera <hadess <at> hadess.net>
2003-04-19 14:21:20 GMT

On Sat, 2003-04-19 at 15:06, iain wrote:
> On Sat, 2003-04-19 at 14:55, Bastien Nocera wrote:
> > On Sat, 2003-04-19 at 14:45, iain wrote:
> > > On Sat, 2003-04-19 at 14:34, Bastien Nocera wrote:
> > >
> > > > Output should be autodetected, and capplets scrapped. ("Just work")
> > >
> > > I think I've already given an example about why that doesn't work.
> >
> > And I've already explained that a hidden configuration option was good
> > enough for those 1% that need to work around crappy drivers, or bugs in
> > the sound output plugins/frameworks.
>
> I said it wasn't a driver issue or a bug in the sound output
> plugins/frameworks. Its a simple case that my soundcard simply does not
> handle certain (common) audio formats.
So that's either a bug in the driver, that doesn't advertise correctly
which formats are supported, or in the framework for not testing
properly if these formats are supported.
> Other reasons why a capplet might be useful, given a system with OSS,
> Alsa, ARTS, ESD, MAS installed, how does one automagically decide which
> to use?
That's another discussion altogether... On a GNOME/Linux platform, it
would properly test for the presence and current use of the sound
servers, then ALSA, then OSS.
xine plugins use "priorities" for that.

Re: [gst-devel] Re: [gnome-love] GStreamer plans and TODO

On Sat, 2003-04-19 at 15:34, Bastien Nocera wrote:
> Happy to see that Totem is on the map now :)
My pleasure, just do the job to keep it there ;)
> > GStreamer plugins that needs fixing for gst-player/totem:
> > Make auparse work in gst-player
> > Make flxdec work in gst-player
> > Make Make swfdec work in gst-player
> > Make audiofile plugin work so it can provide aiff support to player, or
> > make an aiffparse plugin
> >
> > Hook up ffmpeg decoders for WMA, Quicktime, Real and ASF
>
> That's an afternoon's job for a clueful person. Real and ASF would need
> demuxer before they're actually any use.
>
> <snip>
>
> > New plugins that would be nice for Soundjuicer, Sound-recorder and maybe
> > Marlin:
> > an au encoder
> > an aiff encoder
>
> I don't actually think these would be any use to Sound Juicer.
>
> > Fixes that would be nice for Rhythmbox and relatives
> > Ape metadata/tag collection
> > Flac metadata/tag collection
> > Writing of metadata using GStreamer