Review: SliMP3
So what is it? Its a small MP3 player with no internal storage of its own. It has an ethernet port, RCA audio outputs (you'll need an external amp!), and a power plug. It has a really bright little screen for displaying song information and a remote. It's about the size of a car stereo faceplate, but a little thicker.
It doesn't have a fancy plastic box. The backside is simply an exposed circuit board. But thats sorta the idea: this is a toy that can work for users, but is also hugely designed to be a hacker toy.
Configuring the device is easy. The latest version has DHCP, but I tested it on a network that lacked the protocol. I put the IP in of my 'Server' and gave the unit its own IP and I was off and running. The server is a perl program you download from the Slim Devices web site. It supposedly will run on on Linux, Windows, MacOS, FreeBSD, BeOS, and MacOSX. It worked great on my linux box. Trivially easy. This unit was the easiest to set up of any MP3 player I have ever used. Of course, I was already running Linux and had Perl ;)
You can control the SliMP3 with a remote control, but the server optionally can just serve up HTML on a high port number and set your playlists up via an acceptable web interface. And since its perl, its all ready for you to hack yourself. The code itself is fairly legible... there's a mailing list, and it is actively being developed.
The closest competitor to the SliMP3 is the Audiotron. The audiotron is almost the same price, has an optical output, a more developed HTML interface, and is physically a nice stereo component. It is a far more mature product. But the audiotron uses SMB file sharing and controls everything within itself. The SliMP3 uses an open source server program to stream the audio to the player. So the smarts are mostly on the PC. Which of course lends itself to easy hacking.
The interface currently is pretty sparse. Some places display filenames where ID3 tags would be preferred. I was unable to get it to load a 20,000 track playlist. But the server software is under active development, and these things should both be resolved in a not-so-distant release.
There are a variety of cool projects that could conceivably be hacked into this thing. A GTK-Perl interface would be super smooth. Cross-fade functions. Intelligent playlist creation. Tivo style thumbs up-thumbs down track rating for music playback. And this is the first MP3 player I've seen that things like this are possible because the code is right there and ready to rip apart. It's even legible!
If you need a pretty box, or demand optical connections to your reciever, go with the audiotron. If you want something tiny, or just want to hack at your MP3 player stereo component, this is a great way to go.
Does this really mean anything, considering the source? I've never looked at Slashcode, but I've heard rumors...
Building one of your own players:
http://www.pjrc.com/
Pretty cool, but I'm waiting for a player that supports ogg files too, since all my own music is encoded that way. Once there's a nice high storage player that supports oggs too, I'll go for it.
:-)
I also see a fairly limited use for this sort of thing, since most people probably want a player that has a fair amount of local storage. While this thing is really cool if you're on a network, most of us don't really have the capability to use it. I wish I was on the kind of network that would allow this to be useful though.
Now totally OT, but I'm glad Taco's been posting today again. He's still got the best story choices of all the editors.
"I may not have morals, but I have standards."
What is the point of controlling it from your computer? Why not use WinAmp? If you're running ethernet to your stereo so you can use this little device, wouldn't it be cheaper to just run audio cable to the stereo? It's a cool product, I guess, but I just couldn't see shelling out that much money for a device that will give me zero extra functionality over a PC with a soundcard, especially when that device still requires the PC.
___
The way to see by faith is to shut the eye of reason. --Ben Franklin
$250+ for an MP3 player that doesn't have it's own storage with a display that doesn't exactly look as professional as other MP3 players on the market...
And it's not even availiable yet! I wonder how CmdrTaco got his. A "free" review copy perhaps?
For $10 you can get PalmAmp software to operate WinAmp/XMMS remotely. Add some extra-long speaker cables, and you've got a more functional version of this for a whole lot less. But this is still pretty cool.
The Apple iPod is:
- Height: 4.02 inches (102 mm)
- Width: 2.43 inches (61.8 mm)
- Depth: 0.78 inches (19.9 mm)
- Weight: 6.5 ounces (185 g)
Has 5 gigs of storage (4.66 formated). Thats alot of memory plus it has 20 minute skip protection. The case is also pretty strong, I just dropped mine on to a NYC street from 3 feet with only minor cosmetic damage and major heart skippping.Strange women lying in ponds distributing swords is no basis for a system of government.
These are beer-guided MP3 players, evidinced by the second photograph down.
Not sure I want my MPEG decoder chips soldered by some beer-swilling hacker... :)
Potato chips are a by-yourself food.
CmdrTaco, why on earth would you want to have a 20,000 song playlist? I can see having that many mp3s, and even wanting to load them all in the same playlist, but damn, what happens if you have an alphabetized list and you're listening to something in "A", and you want to listen to something in "S" ? You're going to be holding the down key on that remote for a LOOONG time. This leads me to an idea, maybe at some point in a high number of songs, your playlist should (maybe it already does, I don't know, I don't have anywhere near that many mp3s) instead of displaying the name of every track, to instead just display the album titles, then when you select an album title, it expands to a song list. that would cut down the listing from 20,000, to probably less than 1,000.
I guess the beauty of this product is that you could just modify the script and have it produce something like that.
-- Dan
The closest competitor to the SliMP3 is the Audiotron.
:)
I'm amazed how few people know of the Rio Receiver. It's a great little box, can be found on eBay fairly cheaply, and there's even a couple of Linux servers out for it (check out JReceiver for a hideously-complicated but wicked-cool mpeg server back-end. It's designed to interface to multiple types of systems, and could probably even have an interface built for the SliMP3.)
$250+ for an MP3 player that doesn't have it's own storage
I'm further amazed by how many people on slashdot apparently don't have networks. If I've got 30G (or more, maybe, haven't looked at the total lately) of MP3s, I don't want to have to deal with replicating that collection on different MP3 players scattered all over the house. Put it all on one box, and let smart devices do the playing. That's what SliMP3, AudioTron, and Rio are all about. Store once, play anywhere.
Now if we could only get this to be a VideoLAN client, too...
I wrote a playlist generator and a frontend for it that has a thumb up/down feature. :) I thought you might enjoy it. You could easily adapt ti for use in such an app for the SliMp3.
m s/ sondra/
source, screenshots (of frontend), etc:
http://www.csh.rit.edu/~benjamin/desktop/progra
-Benjamin Meyer
Do you changes clothes while making the "chee-chee-cha-cha-choh" transformation sound?
Just over one year ago, Rob posted a story about my little Open-Source MP3 Player Project... which also isn't the first open-source design (but it may be the first open-source player that you can buy the hardware instead of buying all the individual chips and soldering them yourself).
Well, enough shameless self promotion for one day....
PJRC: Electronic Projects, 8051 Microcontroller Tools
You could always hook this thing directly into a WAP, and then bridge that to the WAP at your PC. I know its not the cheapest or easiest way to do it, but it *would* work.
DId anyone else see the 5000 capacitors that they installed by hand. Suprised someone didn't go postal.
III.IIVIVIXIIVIVIIIVVIIIIXVIIIXIIIIIIIIVIIIIVVIII