Slashdot Mirror
MagicPlay: the Open Source AirPlay
New submitter JonLech writes "Ever since Apple launched AirTunes in 2004 (later renamed AirPlay) they have remained unchallenged in the Wi-Fi music streaming market. With various manufacturers releasing AirPlay-only Wi-Fi speakers, Android and other non-Apple device users have been left out in the cold. Today that changes with the release of MagicPlay, an open standard for music streaming (think 'HTTP for music') with a BSD-licensed open source reference implementation that any app developer or hardware manufacturer can integrate into their products. For the Linux fans out there, I've written up some instructions on how to turn your Raspberry Pi into a MagicPlay device."
If it's not compatible with AirPlay what's the point? My Linux music server already supports AirPlay, so does my MythTV, so does my iPhone. Why do we need yet a different new standard, especially if it doesn't work with existing devices?
There's no -1 for "I don't get it."
UPnP AV is one of the most awful standards ever developed. I don't know about the AVTransport spec, but the rest of it is just horrible crap.
Never Ever Bloody Refer To UPnP AV As A Good Thing.
You are implying that you would like hardware manufacturers to make a de-facto standard by selling devices first, and then open it up.
This is the route AirPlay went so far, and where all vendor lock-in happens.
A standard allows multiple parties to come together (hardware vendors, software devs, sellers) and have a common ground / interface, so everyone knows what they are talking about. So progress on spreading a open solution should be accelerated by defining a standard first.
NB: The message above might reflect my opinion right now, but not necessarily tomorrow or next year.
It's already dead, unless Google themselves back it and get device manufacturers on board. I have a Yamaha audio receiver that already does DLNA and airplay, what niche does this fill? There's no way that AV receiver is going to get a bios update to support this, and there's no way I'm re-buying $1000 of equipment that already supports 4k resolution so I can have maybe 1 more format be supported. Linux already supports Airplay, this is typical ideological chest beating over open standards. Reinventing something that already works on Linux and Android is stupid and why Open code is having such trouble gaining adoption. You have to lead in innovation not play catch-up to the big boys. Don't try to get airplay remade, rather try to make 3d content stream,or something else that hasn't been done by the competitors.
I'm implying that declaring "the new standard in xyz" is not news worthly unless it is actually picked up and implemented by more than a handful of irrelevant people who made a pretty website and metioned the Raspberry Pi.
The summary goes on to talk about only being able to buy AirPlay speakers. Where can I buy MagicPlay speakers? Nowhere? thought so. Not really a standard then is it? It's not recognised by any standards institutes. It's just someones pet OSS project at the moment. Because its open, they're declaring it a standard.
Slashdot.org is not a newsfeed for Pintrest and Best Buy shoppers. It's for technical people that are interest in geeky stuff that may or may be available at your local retailer yet.
All standards come out long before actual products. 4K TV? 802.11ac? MiraCast? All these are technologies that are built on standards that have just been introduced in the last couple years. Yet people on here have been talking about them before products are actually introduced? Why? Because this is a fucking website geared toward shit like that.
It is quite funny how some people, such as the guy you're responding to, honestly seem to believe if they just wish something hard enough it'll become the truth. There also seems to be a Wikiality component involved.
#DeleteChrome
HDMI is proprietary too, but I'd have a hard time arguing that a competing open standard would improve the current landscape.
The HDMI Founders are Hitachi, Matsushita Electric Industrial (Panasonic/National/Quasar), Philips, Silicon Image, Sony, Thomson, RCA and Toshiba.[15] Digital Content Protection, LLC provides HDCP (which was developed by Intel) for HDMI.[16] HDMI has the support of motion picture producers Fox, Universal, Warner Bros. and Disney, along with system operators DirecTV, EchoStar (Dish Network) and CableLabs unlike AirPlay (previously called AirTunes when it was for audio only is a proprietary protocol stack/suite developed by Apple Inc.
Did you spot the chasm of difference between the two.
But what good is knowledge if it is not wrapped in a consumer product!?
Unbelievable.
Does this attitude stem from the fact that "geek" now includes a vast swath of electronic entertainment consumers who have no interest in how things work under the hood? Or is it the impulse to piss on anyone who tries to do something that is not immediately amenable to generating profits?
Writing the code before the spec (i.e., what you are intending to have the code do) means that whatever buggy-ass shit the coder writes as his version 0.1 ends up being the "spec". Which means that when the bugs are fixed (if they are ever fixed, as they're part of the spec now!), it breaks the spec.
I run: Windows, OS X, Linux, FreeBSD. Just because you have a hammer, doesn't mean everything is a nail.
The summary goes on to talk about only being able to buy AirPlay speakers. Where can I buy MagicPlay speakers? Nowhere? thought so. Not really a standard then is it?
Wow. I'm often critical of slashdot users for missing the forest for the trees, but rarely do I find slashdotters who are simultaneously as clueless, willfully ignorant, and aggressively obnoxious in a single post.
Well done, sir. You're a complete and utter fucktard.
People who say "sheeple" have about as much sophistication as an AOL user, and in fact are probably actually AOL users.