MP3 Jukebox Software With Networking? 10
Milo_Mindbender asks: "I need a jukebox that supports networking with copies of itself on other computers. The main feature I'm looking for is the ability to have different MP3 files on different computers but keep a single master catalog covering all songs on all the jukeboxes you can access. If you request a song that isn't on your machine, the jukebox that has it would stream or copy it to you. I've seen a number of packages but the documentation isn't clear enough to tell if they have this feature and how well it works. The setup of each package is too involved for me to try them all. Any recommendations from people who have actually used this kind of software would be appreciated."
Re:Why not file share?? (Score:1)
Also, my program has the ability for different users to assign adjectives (categories) to different songs.. so you may call one thing "electronica" where I might call it "bristol breakbeat"
The whole application is basically a data-driven user-centric mp3 catelog that also happens to serve up Mp3 files.
I should have at least a beta available in the next few months. I have a lot of functionality already in place, it's just a matter of bringing it together.
My personal pick (Score:2)
ftp based..... (Score:1)
I'll probably be posting something on Freshmeat in a few weeks..
webplay (Score:1)
http://webplay.sourceforge.net/
Like someone else mentioned, the solution you're probably looking for is to NFS mount or SMB mount the drives on the other machines, then have a linux box serve all the files up.
At the heart of them, all your mp3 player apps are going to be just about the same. The compelling feature of webplay, for me, is the ability to stream mp3s to you at any desired bitrate. So on the local net, I just do native bitrate. But when away, I stream at 96kbit, because my pokey DSL upsteam can't handle much more. On-the-fly bitrate changing is handled via Lame on the server.
I'm building one (Score:1)
There are a few features that the existing ones don't have that I have put in mine
I haven't decided if I will opensource it yet. I expect to be complete with at least a beta within the next two months. I'm hoping the free J2EE servers will be robust enough to handle EJBs by that time. Enhydra, last I checked, doesn't.
anacron
A better way (Score:2)
The second method has the advantage that you can push playlists to the client, and allow the client to move through the playlists without having to change anyone else's stream. That is, you basically have N streams running for N users, and each user can navigate their own stream independently.
In the shoutcast model, you have 1 stream for N users, and changing the stream (by controlling it through the jukebox) affects all users.
I personally prefer the Mp3.com model, as it allows more control over the end user, but it's not as scalable as the shoutcast model.
anacron
Mp3Mystic - Close (Score:1)
-Jason
mymusic/mp3sb + NFS? (Score:2)
If that doesn't do the trick, I'm sure that minor tweaking of the code of either project should get you there.
Why not file share?? (Score:1)
Having a jukebox with some serving ability makes it easier to control load, like how many streams you send at a time. Also, I was hoping for something that was (or could be made) cross-platform and nearly transparent to the user so users don't have to go through setting up NFS or other filesharing stuff.
It seemed like the best approach would be to have a jukebox with a batch of "local" songs and a web-style cache of popular "non-local" songs and the ability to send/receive realtime playable streams between jukeboxes. Hook that up to a database of what's on other people's machines with an automatic transfer to your local cache and you've got something that can cheaply serve huge amounts of content, without a central site.
Why? (Score:2)
--Bud