Rolling Your Own Jukebox System? 48
Nurgled asks: "I've been tasked with implementing a client-server jukebox-like system using normal bits of PC equipment. The general idea is to have a central server with all of the music available and then one or more clients which have a kiosk-type interface for browsing the available music and enqueueing it on the central server, all connected to a normal ethernet network. It's important that none of the kiosks should be able to perform any operation other than enqueue new tracks, but it would also be handy if there was a separate administrative console where tracks can be skipped, which would then be available to the venue owners. The kiosks don't have very fancy hardware and most don't have touch-screens, so ideally it should support both mouse and keyboard-based operation. Is there any software already out there that can do this, or am I going to have to write my own? I'd prefer an integrated solution, but I also wouldn't mind separate client and server software as long as I can tweak both to make them work together. Any ideas?"
Streamsicle (Score:3, Informative)
Its open source, runs on Win32 or Linux, and is still being devoloped.
http://streamsicle.com/ [streamsicle.com]
Re:Streamsicle (Score:2)
XBox works best (Score:4, Insightful)
Not only that, in newer versions you can even get weather forecasts, and listen to Internet radio. Xbox Media Center truly does rock. Keep all of your music/media on a central server and just mount it with SMB.
Re:XBox works best (Score:1)
Re:XBox works best (Score:3, Informative)
Microsoft will send you one for free if you pay for shipping and handling: linky [xbox.com].
Re:XBox works best (Score:1)
It is 2005 right?
Re:XBox works best (Score:2)
It is 2005 right?
My bad... I thought it was going on forever because they've been offering it for the price of shipping for the last couple of years or so.
Re:XBox works best (Score:1)
Is Linky related to Clippy in any way?
Re:XBox works best (Score:2)
Re:XBox works best (Score:1)
I'm sorry, I don't understand. Which bit of that surprises you?
Re:XBox works best (Score:2)
The part where MS actually uses something non-propritary, perhaps?
Re:XBox works best (Score:2)
What was old is new again (Score:1)
Here [slashdot.org] was my answer then.
A Quick Google Search... (Score:2)
... for the following:
And I found this [thwartedefforts.org] as the fourth link.
Grind (Score:5, Informative)
It is beta software because more metainformation in media files needs to be supported, along with perfecting its automatic installation proceedure. That said, I use it almost daily with no problems at all.
The main feature that sets Grind apart from other jukebox software is that it supports intellegent autoqueuing. Grind monitors what songs, artists, and albums you frequently listen to, and which songs you frequently skip. The user can then set Grind basically in autopilot (autodj?) mode and it will automatically play songs from your favorite and similar artists. There may be another open source project that does that, but I've yet to find one.
Zina (Score:1)
Re:Dear Slashdot (Score:2)
I know I like to see real life experiences about products, preferably from people who have tried more than one solution.
Asking on Slashdot may be only one step in this person's search for a solution. It isn't necessarily the entire effort this person is putting into their research.
Seems reasonable to me.
SlimServer (Score:5, Informative)
Just use SlimServer [slimdevices.com] and be done with it. Read about it here [slimdevices.com], but to repeat the main features:
It's intended to be the interface software for the same company's Squeezebox [slimdevices.com] network audio player, which explains why they're willing to give it away under the GPL -- they make their money of the hardware. That also explains some of the unusual design decisions that went into SlimServer, namely, that unlike some other network streaming setups (Apache::MP3 [apachemp3.com], iTunes DAAP streaming [sourceforge.net], etc) which let each client listen to their own selections, the SlimServer architecture allows multiple clients to have a say over the one stream that's being used centrally. For a management interface to a central home audio system, or for the system described in this article, that design decision is a perfect fit.
Really, give it a try. I tried setting it up on a LAN for coworkers to listen to mp3s on their headphones, and while everyone liked the interface a lot, it was annoying that everyone listened to the same thing. But if you want to provide a way for everyone to set what is being played on a central system, this is exactly the way to do it.
Re:SlimServer (Score:3, Insightful)
It's interesting that you say you couldn't enable multiple clients to listen to different audio, as they clearly intend you to be able to do that with the squeezeboxes. From the FAQ:
Can I use multiple Squeezeboxes with a single server?
Yes, you can have any numbe
Re:SlimServer (Score:2)
It's been a while since I played with it, but my impression was that it was serving different things based on the client IP address, but if all the clients appeared to have the same IP (e.g. different subnets being bridged by a gateway server, so to the SlimServer the clients all appear to be 192.168.0.1 or something) then they'd all get
Re:SlimServer (Score:1)
I made a jukebox system (Score:1)
This was originally my senior independent work in the Comp Sci department at Princeton, advisor Brian Kernighan.
I am looking to open source the project when I get around to it. I built it on OS X 10.2, using PHP, AppleScript and iTunes.
Doing this already (Score:2)
Contact me at anthony@opensource-strategies.com for information and pricing.
Re:Doing this already (Score:1)
Letting someone know they can get the service/goods elsewhere for nothing is a troll?
You, Moderator, are a jackass. (or have some connection w/ the site and think it'll actually turn a profit) Eiter way, you're clueless.
I'm ready to by a network-enabled, clue-by-four, anyone have some available?
What about old school? (Score:1, Offtopic)
A couple of folks have made suggestions that answer the original post. I'm more curious about what the communication protocols for the jukeboxes that were used in diners in the 50s. Each remote station (table/booth) could add a song to the queue of the master jukebox. They'd have to transmit the song ID to the master. Was this done serial? Parallel? What was the encoding used? And how did the master jukebox implement a FIFO queue?
Curious, and fairly ignorant of pre-solid-
Re:What about old school? (Score:4, Informative)
Older Rowe and Seeburg boxes had a mechanical queue. Jukebox idle, you choose A1 and D1. A1 starts playing. If nothing else happens, it will play D1. But if I choose C1 (while A1 is playing), C1 will play before D1, because the mechanical scanner comes to it first.
When I put in my money and choose C1, a 9-notched mechanical thingie, about the length of a toothpick, will be pushed in to the first notch, for position C1. When song A1 finishes, it scans the 'next thing to play' mechanical queue, and plays the first thing it comes to. In my example, it plays C1 (and the notched thingie goes back to the 0 position) and then goes on to song D1.
The 9-notch thing means that a song can be chosen 9 times but no more - and that the scanner will scan the rest of the jukebox queue first. If I had chosen C1 twice (and nothing else selected), song order would be A1, C1, D1, C1. If I had put in lots of coins and chosen C1 twenty times, it would only play 9 times.
Details differ on different brands, of course. Slightly newer ones (in the late 1970s) started storing the playlist in a true FIFO queue electronically.
Re:What about old school? (Score:2)
Arcade Controls (Score:1)
Here's a list of software for you. (Score:1)
You might find something to help you there. Hopefully there'll be no
There also a forum at http://forum.arcadecontrols.com/index.php/board,5. 0.html [arcadecontrols.com]
mserv + mserv-php (Score:1)
http://www.mserv.org/ and http://dougiamas.com/mserv/
music player daemon (Score:1)
I have it running at home and I can control it through a web browser from wherever I happen to be. Permissions can be set by user, and playlist control is incredibly easy.
I searched for this same thing for a while for myself and tried a number of systems, and have stuck with MPD because it just works, always.
Re:music player daemon (Score:2)
Tunez (Score:3, Informative)
We use tunez at our LAN's so anyone can pick a song to play.
Where do you want the music to play? (Score:2)
XMMS Control (Score:1)
BossOgg (Score:2)
NetJuke (Score:1)
Globecom Jukebox (Score:2)
I started looking for a jukebox solution about 3 years ago. I've got ~15000 tunes online and of all the ones I looked at, this one seemed to be the most scaleable.
It is written in PERL, and uses a MySQL database backend. It has a themeable Web based frontend driven by Apache and PHP. You can use any browser to search for songs and manage the playlist. I went with one of the very simple themes (not the default) and then customized it to
Re:Globecom Jukebox (Score:2)