Projects / XMMS2

XMMS2

XMMS2 is a redesign of the XMMS music player. It features a client-server model, allowing multiple (even simultaneous!) user interfaces, both textual and graphical. All common audio formats are supported using plugins. On top of this, there is a flexible media library to organize your music.

Tags
Licenses
Operating Systems
Implementation

Recent releases

  •  23 Apr 2009 09:54

    Release Notes: Support for several new audio formats and many changes "under the hood", making it easier to develop clients.

    •  15 Jun 2008 20:44

      Release Notes: This release has new plugins and support for Ruby 1.9.

      •  20 May 2007 19:46

        Release Notes: A lot of big changes have been merged, including the long awaited Collections API. This release has switched to a new build system.

        •  03 Dec 2006 03:58

          No changes have been submitted for this release.

          •  16 Jul 2006 14:11

            No changes have been submitted for this release.

            Recent comments

            23 May 2005 22:12 nateatmyballs

            Re: I don't think this wise.
            Thanks, that does make a little more sense.

            22 May 2005 08:45 nano

            Re: I don't think this wise.


            > Python is a required dependency, since

            > it's required for scons, and is required

            > to generate some code

            > (generate-converter -> converter.c)

            > during the build process.

            That is, python is only necessary during build.

            The real dependencies for the produced binary are:

            glib - Easier to port. xmms2 currently compiles on BSD, Linux, Darwin, Windows* without thousands of ifdefs.

            sqlite - The medialib.

            Then you probably want some way to play music..for example:

            mad - Responsible for MP3 playback

            vorbis - Responsible for Ogg/Vorbis.

            flac - Responsible for flac.

            * Windows doesn't really work yet, see the wiki/bts if you want to help.

            21 May 2005 22:27 eleusis

            Re: I don't think this wise.


            > Ruby and Python should not get involved

            > in something that should be so simple,

            > why would you need two extra languages

            > involved? Just leave it as C.

            If you look carefully, you'll notice that Ruby is an optional dependency. It's needed if you want to build the Ruby bindings to the XMMS2 client library. There are more optional dependencies than this, for various plugins, but I haven't listed them.

            Python is a required dependency, since it's required for scons, and is required to generate some code (generate-converter -> converter.c) during the build process.

            21 May 2005 18:14 nateatmyballs

            I don't think this wise.
            I don't really want to completely nay-say you here, but the idea of having excessive dependancies seems a foolhardy choice to make.

            Ruby and Python should not get involved in something that should be so simple, why would you need two extra languages involved? Just leave it as C.

            Anyways, I know you must have your reasons, but to me it doesn't make any sense to use three languages to make a music playing programme, or suite as you have it.

            Screenshot

            Project Spotlight

            OpenStack4j

            A Fluent OpenStack client API for Java.

            Screenshot

            Project Spotlight

            TurnKey TWiki Appliance

            A TWiki appliance that is easy to use and lightweight.