WWWinamp 4.2 Build 3018

Publisher's Description:

WWWinamp is a simple Web server-like application that allows remote control of Winamp via any Web browser. It manages a database of files and/or URLs that can be queued into a running Winamp. It supports most standard Web browsers, and includes a special mode (that conserves bandwidth and screen space) for Windows CE devices. It supports two optional levels of password protection. The first level lets you control who can search the database and queue files, and the second lets you control who can do things like remove files from the queue, pause playback, and so on.

Latest Changes:

• [HTTP] Added ability to handle 302 Redirect on directory requests without trailing slash (example: http://localhost/images)
• [HTTP] Added ability to submit variables to a default file (example: http://localhost/?q=play)
• Added several new commands to control EQ, Seek and Winamp UI (see sdk.txt)
• Added new script tags to get Repeat, Shuffle and EQ status (see sdk.txt)
• Changed Repeat and Shuffle commands (see sdk.txt)
• Improvements to the Winamp IPC code (up to date with latest WinAmp 5.34 SDK)
• Fixed issue when adding first folder found to the playlist when displaying all, the first file was omitted
• Fixed issue when trying to move the first file in the playlist up or last in the playlist down

Latest User Reviews:

Reviewer:	Somnambulator	Apr 8, 2008
Version:	4.2 Build 3018
im almost positive Winamp 5.5x has this functionality built-in by defualt. unless this offers dramatically more features and easier use, i dont see a reason for any remote winamp applications when Winamp Remote is bundled free with winamp.
Rating:

Reviewer:	preinterpost	Jan 30, 2008
Version:	4.2 Build 2948 Beta
I guess comptetition is good but no problems here using AjaxAmp, which seems less bloated while more functional - hence no reason to change.
Rating:

Reviewer:	enusbaum	Aug 11, 2006
Version:	4.0.0 Alpha 4
I appreciate the critique of my program, especially the in-depth review previously by The MAZZTer. I'm flattered by everyone's kind words on WWWinamp v4.0 this far. Feedback on the skin is of course welcome but the one provided is really just a proof of concept and a starting point for other users with more web development savvy than I to create their own skins. I look forward to everyone's feedback and thank you all for your support.
Rating:

Reviewer:	coolticker	Aug 9, 2006
Version:	4.0.0 Alpha 4
version 4 switched to .NET :-( So it will use much mmore memory than version 3. I hate .NET !
Rating:

Reviewer:	The MAZZTer	Aug 8, 2006
Version:	4.0.0 Alpha 4
Needs major work. Frontend uses JavaScript, but no AJAX. Utilizing AJAX, this could be used to have the entire playlist download in the background and fill up the list, and then it need not be reloaded on every click. Should have more JavaScript to bring the interface to life, EX the sliders for balance and volume could be made to match Winamp's behavior in a browser instead of being static. Right now all that JavaScript is really being used for is for page navigation through the library and building a search string URL. This is unnecessary and can be done server-side. If JavaScript is going to be required it should be enticing enough to get the user to want to turn it on. There is a position counter, but it is easily disrupted by using normal Winamp controls. AJAX could be used to check with Winamp every second for more precise timing. Needs tighter Winamp integration, possibly through a Winamp plugin. It should be able to determine which extensions Winamp supports automatically, as well as get Winamp's Media Library. The Playlist also does not accurately reflect Winamp's playlist (it shows what was playing the last time you started up/shut down Winamp, not what is on the playlist now). Something really neat that could be done with this is dynamic ripping of skin resources from the current Winamp skin to create the GUI instead of using the current static images from Winamp Classic... this would require parsing the Winamp skin format though, and some skins would not support all the views needed for this to be useful. A more sane alternative would probably be to upgrade the frontend to show Winamp Modern as the GUI. The HTML/CSS seems solid from a quick glance, which is always nice. :) But if you are going to make a Web interface to control something in realtime, using "Web 2.0" stuff like AJAX is really a must to keep all the data synced and make a good web app that could pass for a desktop app. Also, I don't see any mechanism to restrict access without using an external program like a firewall. This should be a no-brainer. Also this is not much of a problem for me, but some sort of GUI or GUI wrapper (by this I just mean a tray icon and hiding the console window, nothing fancy) would be nice. Even better, the author might want to consider remaking this as a purely Winamp plugin, although then you lose the ability to run it when winamp is closed. Summary: - JavaScript can be used to give the interface more pop. - Needs closer Winamp integration -- Grab Winamp file associations from the registry, use these to determine which files winamp supports. -- Winamp plugin to obtain more winamp information / control more settings through the Web UI --- Even better than grabbing winamp's file associations from the registry, grab them from winamp itself. Or even better, just grab the freaking media library instead of scanning for your own on every run. -- AJAX can be used to keep data in sync in the Web UI even when winamp is controlled directly. It can also allow for the entire library to be loaded at once in the background, and for winamp to be controlled without a single page reload. - Needs more user-friendlyness -- Consider remaking as a purely winamp plugin -- If not, use a tray icon -- Oh yeah, try using an installer (NSIS is a good choice)
Rating: