XMMS comes with a plugin for that. Some distributions which include XMMS may have separated it to another package ("xmms-cdaudio" for example). There are also two other 3rd party plugins, which are old and should be avoided. Below included is an extract from XMMS's README concerning configuration of CD Audio plugin: Device: The actual device of your CD-ROM unit. Usually /dev/cdrom is a symlink to the correct device.

There is a 3rd-party plugin available, but be warned that it is somewhat broken and does not support streaming. For obvious reasons it also does not support DRM'd files. A slightly updated version of XMMS-MP4 tarball is available here. Updates include: fixed buildsystem, updated version of libmp4ff.

Yes and no. There exists one WMA-plugin that MAY or MAY NOT work properly. It uses WMAv1/v2-codec from FFMPEG, which has few flaws in decoding-tables that sometimes result in audible glitches. There are also two MPlayer-related plugins that may or may not work better (since MPlayer is able to use the binary Win32 DLL-codecs under x86-32): XMMS-MPlayer and XMMPlayer.

Let's start with ls /dev/dsp*. If you get a list like this (and you probably will, most modern sound cards will be auto set up this way) you're already good to go: /dev/dsp /dev/dsp0.0 /dev/dsp0.2 /dev/dsp0 /dev/dsp0.1 /dev/dsp0.3 If you only have dsp + dsp0, or possibly dsp0.0, you need to set some things up by hand. Put the following two lines into /etc/sysctl.conf: hw.snd.pcm0.vchans=4 In the KDE Control Center, tell arts to use /dev/dsp0.1. If you use esd, tell it to use /dev/dsp0.

This is probably due to one of two things (assuming you've checked the volume and speaker/headphone cables): you are using the Disk Writer plugin; select the preferences and change output plugin to the Solaris one. This is not an issue as of version 1.2.4 of XMMS as it will, by default, use the Solaris plugin on Solaris machines. You haven't selected the correct output ports. Solaris audio has 3 outputs; headphones, line out and speaker (ie, the internal speaker).

Like XMMS, the Solaris plugin is distributed under the GNU Public License. I don't really have much choice in this as a lot of the code was ripped off from, er, based on the original OSS code from XMMS.

Our tournaments are held at the best courses in each city. All tournaments are played by USGA rules and handicaps are tracked on each player to ensure the integrity of each flight. The competition allows members to play under pressure just like the Pros.

The above mentioned plugins are broken crap and should be avoided. Nobody has volunteered to re-write those plugins, so any improvement in this situation seems quite unlikely. Whatever may be the case, do not ask us/complain about them. Using Gentoo? These are related to russian character set patch added by Gentoo packagers to the XMMS package they distribute. To solve the problem, please remove ALL the patches added and recompile XMMS. Or install a vanilla version from tarball.

Yes, some functionality is available via standard XMMS commandline, for more advanced things you can use use xmms-shell. (See also next item below.)

Not really; XMMS1 is tied to Gtk+ and X. There are few possibilities, though: You can use a 'dummy' X server (xvfb or similar), not very ideal solution. Also, some people have forked XMMS codebase to create GUI-less versions, like noxmms, but these tend to have problems with non-converted plugins. If you really want a player which does not require X11, there are several much better alternatives, designed from ground up for that. These include XMMS2 and MPD (Music Player Daemon).

Well, theoretically you MIGHT get XMMS compiled and working under Cygwin, but that is a very advanced issue and requires much knowledge. So don't ask us, we're not interested in such crazy things. However, Google might help you find some fellow crazy men, maybe they have done it.)

Its visual outlook is based on the interface of WinAmp2 and XMMS supports WinAmp2 skin format, but there is no code from WinAmp used in XMMS.

Theoretically you can use SOME WinAmp visualization plugins with XMMS via XMMS-WinAmp emulation plugin, but that ONLY works on 32-bit Linux/x86 platform, so if you're on some other platform (including 64-bit x86), you are out of luck.

The WinAmp3 skin-format is overly complex and will (probably) never be supported in XMMS. Unless someone is mad enough to reverse-engineer WinAmp3's skin engine and bolt that into XMMS. That is very unlikely to happen, though. However, XMMS2 will have it's own format that offers features similar to WinAmp3 skins. Also due to XMMS2's client/server-architecture, someone might write a client which supports WinAmp3 skins..

Most likely it is a bug in your respective window manager. XMMS uses rather exotic features of NetWM, and this might be problematic for some WMs. least Oroborus and KWin (KDE's window manager) have been known to suffer from XMMS-related problems in past.

Outline moving works by drawing a rectangle of inverted pixels around a window. When you move the mouse, the old rectange is erased (by inverting the pixels again) and a new one drawn. Fluxbox grabs the display to freeze all the applications display windows. If it doesn't to this, then window changes can occur which change bits of the rectangles, ultimately leaving sections of rectangle randomly around the screen.

Since a majority of our performances are private functions, your best bet is to call us about our upcoming schedule. Usually it is OK to come out to a wedding and listen to/view the band. You must be appropriately attired in dress clothes. Each function and facility has its own guidelines for viewers, including some that do not allow any viewers. Please also refer to our band rehearsals.