Today I’m trying to setup a server that makes my music available to any of my computers and operating systems in the LAN, and possibly even outside the local network. At the same time I would like to add last.fm again, however, not linked to each individual player, but only once, to the music server.

I stored my music files on an external network drive. This music folder is a Samba share and accessible from other computers on the network.

VLC is known for its network streaming features and I wrote a little about it back in May. While I use it occasionally to stream videos from one computer to another I was looking for a solution that could work better as a permanent configuration, well-suited as a music library. That’s how I stumbled upon the X-platform Music Multiplexing System 2, XMMS2.

XMMS2

XMMS2 is a client-server music platform which can be controlled via command line but also through a variety of other interfaces available on Linux, Windows as well as Mac. It allows you to play and manage your music collection on a local server or across the network. It is free, open-source and extensible with a growing number of plugins.

On my Ubuntu system, it was just a matter of seconds to install XMMS2. Ubuntu’s repositories already include everything you might need. I browsed the Synaptic package manager for…

• xmms2, the core application with server and command line client interface.
• xmms2-plugin-smb, a Samba transport extension I needed to get access to my music share.
• xmms2-scrobbler, used to submit data to Last.fm
• esperanza, a simple player, xmms2-client and graphical user interface
• xmms2-plugin-flac, to support the flac-format
• xmms2-plugin-mp4, to support the mp4-format

XMMS2′s command line interface is very easy to use thanks to its legible commands and parameters, just to mention a few:

• To start the server: xmms2-launcher
• To quit the server: xmms2 quit
• To add some music: xmms2 add /home/gerrit/Music/track.mp3
• To add a folder recursively: xmms2 radd /home/gerrit/Music/electronic/
• To add some music from my samba-share: xmms2 add smb://username:password@edmini/music/electronic/track.mp3
• To list the contents of the current playlist: xmms2 list
• To play: xmms2 play
• To stop playback: xmms2 stop

If the server is already running and you install new plugins, you may have to restart it before you can use the plugin. You can stop the server with xmms2 quit, or if that doesn’t work for some reason:

1. find the process-id with ps aux | grep xmms2d and
2. kill the process with sudo kill processid.

XMMS2 makes it easy to organize music in playlists:

• xmms2 playlist list lists all available playlists
• xmms2 playlist create myplaylistname creates a new playlist
• xmms2 playlist load myplaylistname loads an existing playlist
• xmms2 playlist active shows which playlist is currently active

With a separate set of media library commands you can also keep track of your artists, track and album titles, cover images, etc. To display a list of related commands: xmms2 mlib. To search for an artist: xmms2 mlib search artist:"Boards*". Standard wildcard characters like ‘*’ and ‘?’ are supported, too. It’s probably easier to use these mlib functions from an XMMS2 client software other than the command line. With a player like Esperanza you will find an easy-to-use graphical user interface for command line parameters.

To make the XMMS2 daemon reachable from other computers I added a tcp-socket to the configuration nano ~/.config/xmms2/xmms2.conf

unix:///tmp/xmms-ipc-gerrit;tcp://

More details on remote machines can be found in the FAQ. The default port is 9667. After restarting the xmms2d daemon I was ready to test my configuration from the other computer, a Windows system.

I installed the Windows built of XMMS2 and Esperanza which I found here, puzzle’s win32 folder. I had to make sure to use the version that matches the version of my server, in this example it was XMMS2-DrLecter.

I defined the following environment variable XMMS_PATH = tcp://192.168.1.43:9667 to let XMMS2 know where to find my music server.

The command-line version of XMMS2 works great on Windows, but I was still experiencing some problems with Esperanza (downloaded Esperanza-0.3.exe) which exited with a runtime error. Whenever I tried to launch Esperanza on Windows, the server responded with “Client ‘Esperanza’ with bad protocol version (1, not 11) connected”.

This looked like a similar conflict I experienced with the wrong XMMS2 version before, so I looked for another version. I found the DrLecter built Esperanza4-DrL.7z here. This version works great.

Now I was ready to play, stop, and control my XMMS2 daemon from my remote computers, may it run Windows or Ubuntu. However, this configuration didn’t actually stream music from my server to the remote machine. It only served as a channel to remote control the server’s playlist. The music was still played nowhere but on the server system.

Icecast2

Icecast2 is a streaming server, a package that will allow you to setup a simple Internet radio station. It, too, is readily available in Ubuntu’s repository and can be installed via Synaptic. After installation I updated two configuration files: sudo nano /etc/icecast2/icecast.xml

There I defined some passwords where the default was marked with ‘hackme‘. I also changed the ports to 9600/9601. No particular reason, other than having the Icecast2 ports relatively close to the XMMS2 default port. You can choose any port there. More details in the basic setup help. I left all the other settings alone and edited sudo nano /etc/default/icecast2 to set ENABLE=true. After that I could start Icecast2 with /etc/init.d/icecast2 start.

The Icecast admin-page should now show up with the url http://localhost:9600. But there still is no music to stream. In the next step I linked XMMS2 to Icecast, using the…

xmms2-plugin-ices

As part of the Ubuntu repository it was installed in a matter of a few seconds. It needed to be configured in the ices section of nano ~/.config/xmms2/xmms2.conf.

Make sure you stop the daemon before you make any changes, otherwise they might not be visible next time you restart. If you can’t find an ices section after a fresh installation, you can let XMMS2 and the plugin set a default section up for you. Try restarting the daemon. In the ices section I just set the password and portnumber (9600) to match what I defined for Icecast2 earlier. See also the XMMS2 wiki.

This didn’t want to work in the beginning. I received error messages about insufficient permissions. I think this was caused by the fact that XMMS2 and the plugin both ran as gerrit, Icecast2, however, as root. To solve this problem I copied the Icecast configuration (icecast.xml and admin, web-folders) to my home-folder, and changed the owner of all these files.

chown -hR gerrit ~/.icecast
sudo nano /etc/default/icecast2

Now I had to point the daemon to the new folder:

CONFIGFILE="/home/gerrit/.icecast/icecast.xml"

# Name or ID of the user and group the daemon should run under
USERID=gerrit
GROUPID=gerrit

Almost done. There still was a warning about the error- and access logfiles in /var/log/icecast2/. To solve this I had to change the owner of the log-files chown gerrit /var/log/icecast2/* and restart Icecast2 /etc/init.d/icecast2 start

Now I could set the output plugin to ices and start the playback with

xmms2 config output.plugin ices
xmms2 play

The radio stream is reachable with the following address for favorite media player: http://localhost:9600/stream.ogg.m3u, or http://192.168.1.43:9600/stream.ogg.m3u

Having turned the output to Icecast, you won’t be able to hear any music on the server, unless you open the stream. If you want to return to the standard sound output, use the following command:

xmms2 config output.plugin alsa

At this time, both output plugins can’t be activated together to hear music both on server and remote computer. You can only hear music if you connect to the Icecast server. The XMMS2 FAQ explains:

The possibility of multiple outputs involves a nontrivial solution. The biggest problem is keeping all of the outputs in sync with each other. Each output must pull audio data from a buffer following the last decoder or effect plugin in the xform chain at a rate determined by the samplerate of the underlying device. For example, streaming audio will have an exact bitrate since no actual audio hardware is used for obtaining audio data, but a soundcard’s samplerate may vary by a few Hertz with temperature, components, and voltage. We end up with an ever growing buffer (if the buffer holds data longer for slower outputs) or dropped samples (if the data is destroyed after the faster output has read it).

There are also smaller issues like that the xmms2 daemon takes into account the delays caused by the output plugin when showing the current playtime, but if there are multiple outputs these delays can vary. So one of them would have to be defined as a primary output to keep this feature in use.

Current plan to resolve the aforementioned problem with concurrent output and stream sourcing is to make it possible for effect plugins to keep a constant input format and stay alive through song changes. That way they can draw the data from the stream itself and it won’t have synchronizing problems because the whole chain is still simple and one-dimensional.

The current configuration works great now. I have a server that provides a stream of music. This stream is accessible from all other computers, and I am able to control this Internet radio stream using XMMS2 and Esperanza if needed, from any other computer running Linux or Windows.

At this point I could probably stop and let it be, but I want to integrate some web-services and social media tools. While I’m mostly just experimenting with a new range of Internet applications, I’m also interested in sharing my music favorites and creating some personal charts of my highlights, the most frequently played tracks, the most important artists, etc. A great tool to link my local music adventures to the web 2.0 world is last.fm.

Last.fm

To make my XMMS2/Icecast2 server talk with Last.fm I installed the xmms2-scrobbler plugin…as usual, from the standard Ubuntu repository. To configure this plugin I followed the instructions I found at sudosys.

The XMMS2 configuration is stored in ~/.config/xmms2, but the plugin tries to read it in ~/.xmms2. To work around this, I created a symlink ln -s ~/.config/xmms2 ~/.xmms2

Next, I created a new directory for the plugin configuration and created a config file with my credentials:

mkdir -p ~/.config/xmms2/clients/xmms2-scrobbler
nano ~/.config/xmms2/clients/xmms2-scrobbler/config

added

user: MY_LASTFM_USER
password: MY_LASTFM_PASS

I created another symlink for the actual xmms2-scrobbler script, so it gets executed when I launch XMMS2.

ln -s /usr/bin/xmms2-scrobbler ~/.config/xmms2/startup.d/

After restarting XMMS2 your music will show up on your last.fm profile.

Continuing from there you can expand your network by adding other services that access last.fm for your music statistics. On Facebook you can use a last.fm application to display your charts on your page or profile.

You can also integrate your last.fm data into your WordPress site with the LiveStream plugin. There is much more you can do, especially if you write your own applications, but this is how far my own configuration goes right now.

I hope you found any of these notes use- or helpful. As usual, please let me know if I forgot something or made a mistake somewhere. :]

So I looked around and quickly found discussions about the same or similar symptoms occurring on several releases of Ubuntu, from 8.x up to the 9.04 Jaunty Jackalope release I am using on this laptop. Some suggested to kill PulseAudio, but this didn’t help at all. It was most likely related to ALSA, the Advanced Linux Sound Architecture drivers.

I found this thread in the Ubuntu forums revolving around pretty much the same problem I experienced. The solution sounded pretty simple:

head -n 1 /proc/asound/card0/codec*
or
less /proc/asound/card0/codec#0

to find out what soundcard or chipset I’m using. For this Gateway model I got "Codec: SigmaTel STAC9205".

zless /usr/share/doc/alsa-base/driver/ALSA-Configuration.txt.gz

and looked for the section for "Module snd-hda-intel". In this section I was supposed to find STAC9205. I found the following models:

• ref Reference board
• dell-m42 Dell (unknown)
• dell-m43 Dell Precision
• dell-m44 Dell Inspiron

sudo nano /ect/modprobe.d/alsa-base.conf

Next I had to configure alsa to use the right model. None of the entries I found fit, but I started with “ref”, and added the following line:

options snd-hda-intel model=ref

I restarted, but nothing changed for me. I tried dell-m42, m43, m44 and even other (Gateway related) models I found in other sections. Sometimes I would get a headphone slider and/or checkbox in the volume control dialog, sometimes not, sometimes I would get no sound at all, and I never managed to get a beep out of my headphones.

I tried to follow some other leads I found in the Ubuntu forums, installed tools, helpers, and libraries, but none of them made a difference. Ultimately, everything led back to alsa.

I downloaded and installed the latest alsa-driver:

sudo apt-get install alsaconf
sudo apt-get install alsa-base alsa-utils
sudo apt-get install build-essential linux-headers-$(uname -r)
wget ftp://ftp.alsa-project.org/pub/driver/alsa-driver-1.0.20.tar.bz2
tar -xjf alsa-driver-1.0.20.tar.bz2
cd alsa-driver-1.0.20
./configure
sudo make
sudo make install

This didn’t seem to make much of a difference, so I looked around and tried a script I found here to download and install the latest snapshot. Again, this first didn’t seem to make much of a difference. Until I looked at the following list of models:

gedit /usr/src/Alsa-1.0.20/alsa-driver-1.0.20/alsa-kernel/Documentation/HD-Audio-Models.txt

This file reveals the following list of models for STAC9205/9254:

• ref Reference board
• dell-m42 Dell (unknown)
• dell-m43 Dell Precision
• dell-m44 Dell Inspiron
• eapd Keep EAPD on (e.g. Gateway T1616)
• auto BIOS setup (default)

Compared to the previous version that shipped with Ubuntu, there are two new entries, eapd and auto now. The eapd (external amplifier power down) option looks quite promising, so back to…

sudo nano /etc/modprobe.d/alsa-base.conf

and added the following line:

options snd-hda-intel model=eapd probe_mask=1 position_fix=1

Restart and success! The headphones finally work properly. If you were having similar problems and found this blog in the attempt to find a solution, I hope these steps could help you a bit further in your quest. I can imagine that other headphone issues could perhaps be solved as well, with an alsa-upgrade and adjustments to alsa-base.conf.

I have the following scenario now: On my desktop PC in the upstairs office I run VideoLAN as streaming server on Windows XP. The streaming session is initiated from the menu via Media/Streaming or Ctrl-S.

To make things easy I just use the UDP protocol to the destination address 192.168.0.100 (my downstairs client) and port 1234. As Encapsulation I choose MPEG-TS. I leave all the other settings at their default values.

Before I start to play the stream, I added a web-interface from the menu via Tools/Add Interface/Web Interface. This will allow me to control the player remotely from any web-browser. This worked only on localhost (the server) first. To give other computers access to the streaming server, I have to add their addresses or subnet to the hosts-file at C:\Program Files\VideoLAN\VLC\http\.hosts

Downstairs I have an Asus EeePC, originally running on Xandros Linux, now on Easy Peasy, an Ubuntu based operating system optimized for netbooks. The EeePC is connected to the television via an AVerMedia PC/Mac to TV Converter and uses VideoLAN as a client.

Since the streaming server is already sending the video to its IP address, all I have to do is to start playing the stream, from the menu at Media/Open Network or Ctrl-N. The protocol is UDP and the address can stay empty.

And that’s it. The video is now playing on the television set. I can also use any of the other laptops or web-enabled devices to launch the remote control interface at http://streamingserver-address:8080/ and pause, play, adjust volume etc.

So far so good, this works relatively well. However, the video sometimes skips or shows some visible artifacts, which I think are caused by the wireless network range all across the house. I was wondering if I could improve the playback quality by reducing the required bandwidth of the video stream. I experimented with the video and audio codec settings or different encapsulation settings in the stream output dialog box, but none of them really worked. With other settings the player starts to stream, but nothing visible (or audible or both) arrives at the other end. Sometimes VLC doesn’t start to stream at all, or even crashes with an exception. I have to read more about the individual settings and formats, and how I can activate and control them.

In this scenario above I let one server stream a video to one client with a known IP address. If you set the server to stream to a multicast IP address (e.g. 224.0.2.1), you can use a whole group of clients to play the video stream simultaneously. Not sure how often I will make use of this, but it works impressively well! I once played a video on both EeePCs and two desktop PCs.

The VideoLAN player starts the built-in web-server at port 8080 by default. If this port is already taken by another application, you can change it by launching VLC with the command-line parameter --http-host host:port. More information can be found in the documentation.

I knew I need my own fax-machine and I found the Sharp UXB800 fax-machine that was not only very cheap at $80, it can also receive faxes as TIFF and PDF and forward them to an email-address. Perfect for me: no paper and ink wasted.

The fax-machine has one problem, however: It doesn’t support any of the SMTP authentication methods needed to forward emails through my ISP, and there is no way to upgrade its firmware to add support. I found a workaround relaying the incoming faxes through a mail-server in my home network. This mail-server can be open for the fax-machine and be set up with the proper authentication needed for the ISP mail server.

First I used the free hMailServer for Windows, which worked very nicely and quietly as a background service. Later I decided to switch to a Ubuntu Linux based mail server running in our basement.

The following are a few (raw!) notes, originally just to myself and not really meant as a tutorial. Maybe some of these notes can be useful if you own a UXB800. If I have some time I might create a walk-through with screenshots and photos one day.

In my recent configuration I decided to give the fax-machine a static IP, but it works just as easily with DHCP.

• In your lan/dsl router, assign a name like faxmachine to a static ip-address like 192.168.1.80. This is optional, dynamically assigned ip-addresses via dhcp work as well. I found it a bit more convenient to treat the fax machine as a static device.
• In your fax machine settings, setup machine identification and network:
  Use DHCP: No
  IP Address: 192.168.1.80
  Subnet Mask: 255.255.255.0
  Default Gateway: 192.168.1.1
  DNS (Primary): 192.168.1.1
  DNS (Secondary): 192.168.1.1
  The settings-page can now be reached through http://faxmachine/.
• In your fax machine settings, setup email:
  SMTP Server: mymailserver
  Port number: 25
  No POP before SMTP: No
  Sender name: My Name
  Email-address: myname@mymailserver.mydomain.lan
  Email-subject: Incoming Fax
  Message: My message
  File Format: PDF
• You now need to setup a forwarding address. This cannot be done with the web-setup menu, but has to be done on the fax machine itself:
• Function/Rcv Fax to E-Mail:
  Act. Rcv Fax To Mail: 1 YES
  Print received fax: 2 NO
  Report Setting: 1 Print Error Only
  Forwarding Address: 2 CLEAR
  Forewarding Addr. Clr: 01 START
  Forewarding Addr. Clr: STOP
  Forwarding Address: 1 SET
  Forwarding Addr. Set: 01
  Forwarding Addr #01: START for all
  Email # Mode: myname@myserver.mydomain.lan START STOP STOP
• In your web-setup, add the email to the destination management page:
  Destination Name: My Name / Rapid 01
  E-mail Address: myname@myserver.mydomain.lan

Notes

If I remember right, the mail server worked pretty much out of the box in Ubuntu. On Windows I set up hMailServer as the following before:

• Installed hMailServer and chose external MySQL database to link to my local server instance.
• Database name: hmailserver
• Domain/General/Domain name:
  mydomain.lan & default-settings
• Domain/General/Add account:
  myname@mydomain.lan & default-settings
• Settings/Protocols: POP and SMTP
• Settings/Protocols/SMTP/Delivery of email:
  Hostname: mymailserver
  SMTP relayer: mail.myisp.domain
  Port: 25
  Server requires authentication
  Username/Password
• Settings/Advanced/IP Ranges/Add LAN:
  Priority: 25
  192.168.1.15 - 192.168.1.47
  Allow connections: SMTP
  Allow deliveries from: Local to Local, Local to external, External to external
  Other: Forwarding relay
• Settings/Advanced/IP Ranges/Edit My Computer:
  Priority: 15
  127.0.0.1 - 127.0.0.1
  Allow connections: SMTP, POP
  Allow deliveries from: all
  Other: Spam protection
• Settings/Advanced/IP Ranges/Edit Internet:
  Priority: 10
  0.0.0.0 - 255.255.255.255
  Allow connections: none
  Allow deliveries from: none
  Require authentication: all
  Other: Spam protection

I hope these notes could at least give an idea how to make this fax-machine work. These instructions will probably vary from one network or computer configuration to another.