Several people have asked for a demonstration of the ability to play a remote stream.  I've always found this a little tricky to explain and get going - it could be made easier, which may attract more people to squeezebox products.

It's the chicken and the egg situation to get going - initially you can't stream any music because there's nothing selected to play, and you can't select to play anything because there's no remote stream.

At the moment, the following steps are required to get a remote stream to play:

1. Open a media player, and point it to the server's URL eg. http://www.abc.com:9000/stream.mp3
2. The stream will connect and indicate that it is playing, but no music has been selected, so there's no sound.
3. Open the web browser (eg http://www.abc.com:9000) and select some music to add to the remote stream player.
4. Stop the remote stream playing in the media player.
5. Start playback of the selected music for the player in the WebUI.
6. Open the remote stream in the media player again.

If this is the first experience a potential customer has of "squeeze" products, I have found that they are a little apprehensive as it seems overly complicated.

What I suggest to ease this initial setup is for the provision of a default playlist that is automatically selected when new remote streams initially connect to SqueezeCenter:

1. Open a media player, and point it to the server's URL eg. http://www.abc.com:9000/stream.mp3
2. The stream will connect and start to play the default playlist defined within the server.
3. Open the web browser to select different music to stream to the player.

The default playlist for new remote streams could be one of several things:
1. An mp3 file that has spoken instructions on how to connect to the web browser and select different music to play.
2. A user-configured playlist - one from his my music/playlist list
3. A favourite.
4. Random songs.

I have also experienced remote stream problems due to bitrate limiting.  Either you have to change the bitrate limit within the player or as a query string on the stream (I don't know if this is still supported).  The former requires you to change the bitrate after the connection has been established, so I think if the user changes it, he needs to then stop the stream and restart.  Therefore I think it would be wise to default the bitrate limiting option for new remote streams to something lower, to ensure the stream and be established easily.

I would also suggest defaulting the new player to be in repeat all mode, as if the stream completes, the remote stream seems to stop but indicates that it is still playing. If new music is then queued up, it doesn't seem to play - the stream needs to be restarted in the media player.