Last updated: 28-09-2005

Copyright © 2005

WinAmp Remotely 2.1 Documentation
By Søren Dreijer

Table of Contents
Table of Contents ..........................................................................................................................................1 Package Contents ..........................................................................................................................................1 Distribution Notice .......................................................................................................................................1 Disclaimer .....................................................................................................................................................1 Version History ............................................................................................................................................ 2 About WinAmp Remotely............................................................................................................................ 3 Why Make Such An Application? ................................................................................................................ 4 How WinAmp Remotely Works .................................................................................................................. 4 Setting Up WinAmp Remotely .................................................................................................................... 4 Setting up the client ................................................................................................................................. 4 Setting up the server ................................................................................................................................ 5 How To Use WinAmp Remotely.................................................................................................................. 5 The Control WinAmp Window .................................................................................................................... 6 Known Issues ............................................................................................................................................... 7 The WinAmp Remotely Client crashed and now all my music files are associated with WinAmp Remotely instead of WinAmp ................................................................................................................. 7 When enqueing songs through Windows Explorer multiple WinAmp instances are created on the server ........................................................................................................................................................ 8 Bug Reporting, Suggestions and Contact Info ............................................................................................ 8

Package Contents
WinAmp Remotely Server.exe WinAmp Remotely Client.exe Documentation.pdf (this document)

Distribution Notice
You’re free to distribute this application to whomever you desire. However, you must always let this document follow the application no matter how you choose to distribute it.

Disclaimer
Blacksmith Studios takes no responsibility for any harm WinAmp Remotely might cause to your system. You use the application at your own risk!

Page 1 of 8
http://www.blacksmith-studios.dk

Added right-click Play and Enqueue support for . Page 2 of 8 http://www.1 (released 2005) Corrected a bug which made the client update itself every time it was launched. - Version 1. pause.4 (released 2005) Fixed bug with association of WinAmp files (like .0. Bitmaps done by [PR]JazzD. Double clicking a music file in the Control WinAmp window’s playlist now makes the server play the music file. It is now possible to select all the files in Windows Explorer and add them to the playlist all at the same time. Server can now be minimized to the tray.e.mp3). Windows 98 and Windows ME. When the playlist is modified all clients' playlists are updated as well. Implemented a Settings dialog where the user can specify which folders should be shared. The WinAmp Control window now opens automatically when a connection has been established. Fixed bug when trying to add more than three songs at the same time. Fixed some minor GUI bugs.3 Fixed bug which made the client application use 100% CPU and the server around 50%. now it’s enough to just share the folder that contains the file (this is now an obsolete feature in version 2.0 instead of the real IP. previous and next buttons have been added.2 The Control WinAmp dialog has been completely redesigned and a lot of new features to control the playback on the server have been added: . Thanks go out to Benjamin Christensen! Version 2.Play.0). Fixed the issue in the server when a client disconnected in which the client’s IP appeared as 0. The message window now autoscrolls as new events occur. more free screen space.A check box named “Hide main window” makes it possible to hide the main window while the Control WinAmp window is still visible.dk . stop. The application now automatically checks for an updated version online. . i. Version 1.m3u files. Version 1.Volume controller has been added making it possible to control the volume on the server. Now the client won’t have to share the entire drive on which the music file resides. The application no longer runs on Windows 95.Last updated: 28-09-2005 Copyright © 2005 Version History Version 2.A playlist has been added providing the user with visible information about what has been added to the server (supporting large playlists). Added a Welcome Wizard.0 (released 2005) Added a log to the application.blacksmith-studios.0. . . Added support for direct network paths.

The purpose of WinAmp Remotely is to enable computers on a LAN to play and enqueue songs in WinAmp on a computer acting as a server. It’s important to note that WinAmp Remotely can only be used when residing on a LAN where computers have direct access to other computers’ music files through Windows shares. So don’t get frustrated if the main window seems to freeze while it’s connecting. The application features support for multiple clients. WinAmp Remotely is now integrated with Windows Explorer. Page 3 of 8 http://www. which makes it possible for several people to manipulate the same playlist at the same time. Version 1. Requirements WinAmp Remotely runs on the following operating systems: • • • • • • Windows XP Windows 2000 Professional Windows NT Workstation Windows Server 2003 Windows 2000 Server Windows NT Server About WinAmp Remotely WinAmp Remotely was my first attempt on making a WinSock application.0 (released 2003) Playback of files residing on either the server or client machine. Fixed some minor bugs.dk . which means that while the client is trying to connect to a server the application will not update the main window. It’s using blocking sockets. You could then use WinAmp Remotely to control the PC’s playlist to avoid placing a keyboard and mouse in front of it. Version 1. Fixed a LOT of bugs.Last updated: 28-09-2005 Copyright © 2005 - Tray icon appears when the application is minimized providing fast access to the application.1 Support for multiple clients connected to the server. You’ll just have to wait until the connection attempt has been completed. Another use might be if you have a PC in your living room which is connected to your stereo set.blacksmith-studios. In other words. WinAmp Remotely supports playback of music files residing on either the server’s machine or the clients’ machines.

In the following two sections the available settings in both of them will be described. That is.Last updated: 28-09-2005 Copyright © 2005 Why Make Such An Application? The idea of making WinAmp Remotely originates from an issue I had every time I went to one of my friends to do some coding. As can be seen on Figure 1 Bob has shared two folders: C:\Music and C:\Music\Tenacious D. How WinAmp Remotely Works One computer on the network acts as a server. This also means Bob has several possibilities when it comes to sharing his music files. it let’s you set up your computer’s shares as described in the previous section. it ensures it resides inside a folder on Bob’s computer which is shared on the network. a client and a server. All this sharing can be managed directly from WinAmp Remotely as described in the following section. Setting up the client The first time the client starts a Welcome Wizard appears. In order for the server to play other computers’ music files they need to be located in a shared folder on the network which the server has access to. This computer should have WinAmp installed and have a pair of speakers connected. Furthermore. C:. If the files are scattered all over his hard disk he might consider sharing his entire disk. which meant I continually had to ask him politely to play a specific song every time I wanted to have any influence on what was being played. Its main purpose is to tell the user about the application. Bob also has a music folder on his local disk C: called My Music and he wants to add one of his music files to the server’s playlist. Page 4 of 8 http://www. That was the birth of WinAmp Remotely since I needed to be able to control the playlist on my friend’s computer from my own. Setting Up WinAmp Remotely WinAmp Remotely consists of two parts. Let’s take an example. of course.dk . The idea is that other computers on the network connect to this server and manipulate its WinAmp playlist by either adding or enqueing music files. Bob’s computer has an IP of 10. He might also be the paranoid type and instead choose to share only a few of his music albums.0. kind of redundant since the first one covers the second one but it nevertheless proves the point that you can specify exactly which folders you would like to share. When he’s adding the music file WinAmp Remotely verifies that the path to the file is valid. Those two shares are.blacksmith-studios.2 and he connects to a server. Since I never brought my own speakers we simply had to play all music from his computer.0.

This is done by clicking Start->Run. You should also avoid adding a password to the share.Last updated: 28-09-2005 Copyright © 2005 Figure 1 It’s important to notice that all shares created by WinAmp Remotely only allow read-only access to remote users to avoid security risks. Setting up the server By default the server is listening on port 6000.g. enter the following in the Run dialog box: “c:\ WinAmp Remotely Server. If you wish to change this you will have to run the application with an additional command line argument. How To Use WinAmp Remotely Page 5 of 8 http://www.exe” is the path to the application and 80 is the desired port number. Windows Explorer you will have to refresh WinAmp Remotely’s internal share list by opening the Settings window.exe” 80 where “c:\ WinAmp Remotely Server. Also. NOTE: Remember to use quotes (“ ”) around the path to the executable if it contains spaces.dk . To start the server on port 80. if you manually add network shares through e.blacksmith-studios.

Each item refers to the numbers in Figure 2. 6000 (to change the listening port.exe. This will execute the server on the default port. when you have spotted the music file(s) you would like to add to the playlist right click on it/them and select either Play in WinAmp Remotely or Enqueue in WinAmp Remotely. When the server is online the executable WinAmp Remotely Client. To connect to the server. This is the recommended way! Alternative method The second way is to add the path to the music file manually in the WinAmp Remotely client by using the Browse-button located on the WinAmp side window (see Figure 2) which is shown as soon as you have connected to a server.blacksmith-studios. Then. NOTE: As mentioned earlier the application will freeze until the client is connected to the server or the connection attempt has timed out! This happens because the application uses blocking sockets and it is nothing you should be worried about (apart from me being too lazy to get rid of blocking sockets altogether). As soon as the client is connected you can start adding or enqueing music files. This is handy if you would like to save some screen space. This button hides the main window (that is. 1. Windows Explorer. see the previous section) and will allow clients on the network to add and enqueue music files on the server as soon as they have connected.Last updated: 28-09-2005 Copyright © 2005 The computer that is running WinAmp and the one that has speakers attached to it should run the file WinAmp Remotely Server. Page 6 of 8 http://www. This will automatically add the song to the server’s playlist. enter the IP or hostname and the port of the server in the appropriate fields at the bottom of the window and then hit the Connect-button to start a connection attempt.exe should be run on all the other computers. the window where you specify connection settings and where all server messages are listed) so only the Control WinAmp window is visible. which makes it very easy to play and enqueue songs from e. The Control WinAmp Window Following is a quick reading of the most important features provided by the Control WinAmp window. which can be done in one of two ways as described below: Recommended method WinAmp Remotely automatically associates itself with the most common music file types.g. This approach is described in the next section. Browse to your music folder in Windows Explorer.dk .

. 4. as described in How To Use WinAmp Remotely. 1 6 5. Figure 2 However. You can pick an action to perform in the “Play song in WinAmp. the recommended way of playing and enqueing music files is by using Windows Explorer. You should do this from time to time to keep the list up-to-date since the person controlling the server’s playlist is able to manually manipulate the list such as removing or moving songs up and down. The song title highlighted in blue indicates which song is currently playing on the server machine (remember to update the list from time to time. Controls the volume on the server machine. If you select a song and then right-click on it. a shortcut menu appears with two options: Play Song should be pretty intuitive. The WinAmp Remotely Client crashed and now all my music files are associated with WinAmp Remotely instead of WinAmp Page 7 of 8 http://www.dk . There are other functions included in the program as well. 2 3 4 5 6. see 5.Last updated: 28-09-2005 Copyright © 2005 2. Known Issues The following issues have been identified in the latest version of WinAmp Remotely.). but you’re encouraged to experience them by yourself. 3. If you double click a song in the list it is played on the server as well. Update list asks the server to send the current playlist.blacksmith-studios. They should be pretty self-explanatory. Buttons to control the playback on the server machine.” combo box and select the desired music file by clicking the Browse-button.

The original associations will have been restored. If a client then enqueues music files quickly after each other the latency that occurs when WinAmp tries to read information about the file (such as length) from the remote computer multiple windows might pop up. even though these machines only have public IPs they can still use WinAmp Remotely with the slight change that everything might be slowed down due to the network traffic that needs to go to the ISP and back. For instance. if the client crashes those associations aren’t reset to its original values. Windows Explorer. This prevents WinAmp from looking up information about music files when they’re added to the playlist. However.dk .dk/?p=5 NAT (Network Address Translation) LAN (Local Area Network) 3 ISP (Internet Service Provider) 1 2 Page 8 of 8 http://www.g. Select the option box named “Read metadata only when file(s) are played”. However. Description The issue has been identified on networks which are directly connected to the Internet without a router providing NAT 1 to the LAN 2 . though.Last updated: 28-09-2005 Copyright © 2005 Description When the WinAmp Remotely Client has successfully connected to a client it associates some common music file types with itself. It might cause the songs to take a little longer to load when played. When enqueing songs through Windows Explorer multiple WinAmp instances are created on the server Please note that this issue occurs even though WinAmp’s “Allow multiple instance” setting is disabled. This is to make it very easy for the user to play and enqueue music files from e.blacksmith-studios. Solution Just run the WinAmp Remotely Client again and close it. Suggestions and Contact Info Please report any bugs and suggestions online at http://www. Solution Open WinAmp’s Preferences dialog and click on General Preferences->Titles. an ISP 3 might provide a customer with two public. Bug Reporting.blacksmith-studios. dynamic IPs which allows for only two machines to be online at a time per household.