MagicPlay: the Open Source AirPlay 177
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."
its not news yet (Score:4, Insightful)
If there isn't wide spread hardware adoption, its a useless 'standard'
Re:its not news yet (Score:5, Insightful)
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.
Re:its not news yet (Score:5, Insightful)
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.
Re: (Score:2)
Where can I buy MagicPlay speakers? ... 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.
I think you can already use it if you have a media center setup (connected to speakers), and then stream from laptop & phone.
Re: (Score:2)
Why would you use AirPlay then, if you can just connect a macbook to everything and use plain old itunes?
Re:its not news yet (Score:5, Insightful)
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.
Re:its not news yet (Score:4, Insightful)
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?
Re: (Score:3)
Standards become standards when a group decides on it.
802.11ac? That group was IEEE.
4K TV? I guess that's covered under the HDMI supported resolutions.
MiraCast? That would be the Wi-Fi Alliance.
Re: (Score:2)
Slashdot.org is not a newsfeed for Pintrest and Best Buy shoppers
That might have been true a few years ago...
Re: (Score:1)
this is idiotic
you do know like basically most every network-enabled device also had firmware that is updatable right?
I'm not saying it will actually happen, but saying that sony couldn't add support to all their receivers and TVs with a firmware update is silly.
Re:its not news yet (Score:5, Insightful)
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.
Re: (Score:2)
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.
OK, let's write up the business plan. Pick an existing, successful, and widely implemented technology. Come up with an alternative.
Approach a venture capitalist with your business plan that includes the phrases "and all the consumer has to do is buy a Raspberry Pi and roll their own homebrew adapter" and "will have a subset of the functionality of the existing, successful product".
Let me know how big of a check they write you.
Re: (Score:1)
Re: (Score:2)
Right. I think I said something like:
and "will have a subset of the functionality of the existing, successful product".
Re: (Score:2)
This is slashdot. It is supposed to be a site about up and coming technologies, not just about established technologies.
Re: (Score:2)
I checked the references, this is Qualcomm trying to get in to the wireless streaming market.
Re: (Score:2)
Re: (Score:2)
And there won't be, as no hardware company would dare cross the Apple juggernaut. They would be punished by being frozen out of all future liscensing deals, if not by outright lawsuits,.
And this is why practical monopoly is so destructive.
Re: (Score:2)
Useless to mindless consumers, yes. It's only of interest to creative technical people who build things.
I think "Ow! My Balls!" is on another channel.
Re: (Score:1)
Seems like Miracast will be much more likely to be the alternative: http://en.wikipedia.org/wiki/Miracast [wikipedia.org]
Nope. Shitty name.
Just because it's there doesn't mean it'll be used (Score:2)
accessory manufacturers are desperate (Score:1)
While it's great an alternative to AirPlay had been released, I doubt it'll get much support from accessory manufacturers unless the likes of Samsung decide to integrate it with their phones.
Right now Apple accessories that used to be *everywhere* are increasingly only seen as sad sale items, in those wire bins by the counter collecting discount stickers, after Apple shafted its customers with another proprietary connector...at least they get to give *more* money to Apple...and they do need it, avoiding paying any tax in the UK much of cost them a small fortune in..accountants.
Accessory Manufacturers are desperate to tap into none apple products simply because they outnumber Apple products six
Re: (Score:1)
Yes, if only iPod wasn't the number 1 music player.
Or if the iPhone wasn't the number 1 smartphone in the US.
Or if the iPad wasn't the only tablet being sold in volume.
It's so sad!
Re:accessory manufacturers are desperate (Score:5, Insightful)
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.
Re: (Score:2)
Not until Netcraft confirms it.
Incompatible with AirPlay? (Score:5, Insightful)
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?
Re: (Score:2)
Wish idiots would understand how to quote (Score:3)
Obligatory XKCD [xkcd.com].
The joke is about creating a standard to replace multiple incompatible standards...simply adds to the standard. This is about pragmatism; its about creating an open version of Apple Inc proprietary protocol stack/suite.
Re:Incompatible with AirPlay? (Score:5, Insightful)
Um, because AirPlay is proprietary.
There are people who's media world doesn't revolve around an iPhone. And while there are various stop gap measure for those users - including using AirPlay in unauthorized ways - it is still a proprietary protocol, and this is Apple so we know they will release the lawyers when the time comes.
I actually find it remarkable that I should have to argue that an open standard that does something like AirPlay would be a good thing if it were done right and caught on.
Re:Incompatible with AirPlay? (Score:4, Informative)
Um, because AirPlay is proprietary.
There are people who's media world doesn't revolve around an iPhone. And while there are various stop gap measure for those users - including using AirPlay in unauthorized ways - it is still a proprietary protocol, and this is Apple so we know they will release the lawyers when the time comes.
I actually find it remarkable that I should have to argue that an open standard that does something like AirPlay would be a good thing if it were done right and caught on.
You are 100% correct in everything you say. But he still has a point.
Being Apple compatible is the "sexy" thing to do in the manufacturing world these days, and this is all rather useless if you can't go to Best Buy and pick up a device that supports it.
Add to that the fact that there is an existing standard that can already do this stuff (UPnP/DLNA), and do it better. And those standards actually have some device support, although the implementations all seem like they were a quickly hacked together afterthought.
That said, being outside of the Apple world, I have found that Plex media server + Roku + Plex Android app handles all of my media streaming needs just fine.
Re: (Score:1)
To the best of my knowledge, DLNA does not support the AirPlay behavior. DLNA provides a fairly generic menu-based system to browse advertised media libraries, and to allow clients to request a file be streamed. It's not a bad system, though the fact that it's broadcast-only is annoying for anyone with non-flat network.
But I'm not aware of any DLNA component that allows a system with local media to select an advertised client and force it to start playing a stream. Unless I've missed something DLNA doesn't
Re: (Score:2)
But I'm not aware of any DLNA component that allows a system with local media to select an advertised client and force it to start playing a stream. Unless I've missed something DLNA doesn't even require clients to advertise, let alone to allow remote control.
It's definitely part of the spec. I've even found a few android apps that implement the "remote control" part, as in using your phone to tell your TV to play a movie stored on your file server in the basement.
What's unfortunate, is that to I've not been able to find examples of all 3 components (server, player, controller) that are anywhere close to being a workable setup. Unless you count Plex, which does do all 3, but unfortunately doesn't seem to play nice with non-Plex DLNA apps.
Re: (Score:3)
A DLNA device can be both a client and a server, and you can instruct servers to play content you have chosen. I'm pretty sure I've done this XBMC's DNLA implementation, controlled from my PC.
Re: (Score:2)
To the best of my knowledge, DLNA does not support the AirPlay behavior.
I should probably clarify my original post.
When I said that DLNA "does it better", I was referring to the fact that it also handles video while MagicPlay is at this point music only. I didn't mean it more closely mimicked AirPlay behavior.
Re: (Score:2)
And being inside the Apple world, I've found that iMac w/ Plex media server + roku + Plex iOS app + Win7 w/ Plex media server covers all my media streaming needs.
Plex is amazing... and it's even available in some "smart TVs" now too!
Re: (Score:2)
I actually find it remarkable that I should have to argue that an open standard that does something like AirPlay would be a good thing if it were done right and caught on.
So like DLNA? That we already have and is widely supported.
Re: (Score:2)
Except for the fact that there are some VERY well done DLNA servers that handle real time transcoding just fine, and do it based on the formats that the playing device supports.
Re: (Score:2)
Serviio [serviio.org].
Re: (Score:2)
So is SMB. So are Skype and Google Hangouts. So is MP3. And yet all of those have alternatives based on open standards.
Thing is, open standards are all well and good -- but if nobody uses them, who gives a shit?
SMB alternative (Score:2)
Re:SMB alternative (Score:4, Funny)
TuxRacer, of course!
Re: (Score:2)
True, FTP and NFS are open alternatives to Server Message Block to an extent.
NFS, eh, sorta, but it's a stretch. FTP? Not even close.
Re: (Score:1)
Poor Analogy (Score:5, Insightful)
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.
Re: (Score:1)
Did you spot the chasm of difference between the two.
Nope. I can walk into Best Buy or Walmart and purchase AirPlay and HDMI devices. In neither store can I find MagicPlay/HDMI-open-alternative devices.
Do you see the glaring similarity?
Re:Poor Analogy (Score:5, Insightful)
The difference is that you'd be struggling to buy a TV in Best Buy/Walmart that didn't support HDMI. The proportion of network-connected media players that support AirPlay is not even close to universal.
Re: (Score:2)
Nope. I can walk into Best Buy or Walmart and purchase AirPlay and HDMI devices. In neither store can I find MagicPlay/HDMI-open-alternative devices.
Do you see the glaring similarity?
There was a time not long ago when you couldn't buy an AirTunes/AirPlay device (other than from Apple) for all the Bitcoins in the world.
How the @#$% do you think standards get established? Hint: it's not overnight.
Re: (Score:1)
Developed by apple. Supported by a big list [wikipedia.org] including a bunch of open source implementations. Tell me again how I should give up something that works, screw around wtih beta software that doesn't support the same feature set and potentially re-purchase hardware to operate with this new protocol?
And if your argument is "but Airplay is proprietary!" then try again. Outside of slashdot, very few people in the real world actually care, and are more than willing to pay the couple of dollars per device if re
Re: (Score:2)
Well, this is Slashdot and here we do care, so piss off.
If we can't buy something better than AirTunes, we'll fucking build it.
Re: (Score:2)
Re: (Score:2)
Great, can you please point me to an airplay implementation for my android phone and tablet?
Re: (Score:3)
http://www.knowyourmobile.com/android-apps/18049/best-airplay-apps-android [knowyourmobile.com]
That was the top hit, I'm sure if you can figure out Google you will find more. Once Apple's Airplay keys leaked a bunch of apps were built for Linux and obviously Android too. the XBMC community talked about this awhile ago when XBMC implemented Airplay but having an IOS device I've never had to worry about it except when Apple has stupidly tried to interfere with the compatibility - that never lasts long :-)
Incompatible with Upnp (Score:2)
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?
I don't think you understand (Well actually I think you do) from Wikipedia "AirPlay (previously called AirTunes when it was for audio only[1]) is a proprietary protocol stack/suite developed by Apple Inc. that allows wireless streaming of audio, video, and photos, together with related metadata between devices."
I find it somewhat ironic that your defending Airplay...against more open standards like UPnP or DNLA...as someone who uses MythTV SMB works better...but then you have an iPhone and Apple stuff *only
Re: (Score:3, Insightful)
Because Airplay does so much more than UPnP or DLNA. Whether you like apple or not, i can start playback on one device, move it to another mid-steam and not skip a beat. It does video. I can use it to do desktop mirroring.
Whilst nerds on slashdot bitch about "proprietary garbage", real people are actually using and enjoying technology like this that has compatible hardware on the shelf (not just from apple) and actually works.
Lots of protocols for music over the network (Score:2)
There are lots of protocols to play music over the network. This summary suggests there was none but AirPlay.
Re: (Score:2, Insightful)
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 somet
Re: (Score:2)
Mod this up +100, AC or not.
Re: (Score:2)
I have only been able to find two systems that play synchronous music, both proprietary. The first is Airplay and the second is Sonos. Everything else that I've tried plays out-of-sync to multiple speakers. Airplay has been cracked and there are Android clients for it. Airport Express wall warts are under $100, so I have gone that route for now. I am excited by the potential here with an open competitor. I believe some people have experimented with making UPnP synchronous, but have not run into any practica
Re: Lots of protocols for music over the network (Score:2)
What does synchronous mean in this context?
Re: (Score:2)
The AC explained it well. If I have a system on my deck and a system in my family room and a system in my dining room/kitchen, I'd like to stream to all 3 at once during, say, a party. With Airplay or Sonos, this works perfectly. With UPnP and other streaming solutions, the speakers get out of sync and you'd be surprised how bad that sounds. Like you are in an old echoey stadium.
Re: (Score:2)
I see.
Indeed, I do not know of any solutions that allows to remotely play music on several devices synchronously. I know see the point of this technology, thanks.
Already dead on arrival. (Score:5, Insightful)
Open-ness is the point. (Score:1)
Reinventing something that already works on Linux and Android is stupid and why Open code is having such trouble gaining adoption.
Maybe "adoption" is not the point (especially when "adoption" means another avalanche of redundant consumer goods).
The point is the principal of creating a standard can be the basis of understanding the technology and extending its capabilities that is open to anyone rather than locked up in some corporate lawyer's file cabinet.
Re: (Score:2)
The point is the principal of creating a standard can be the basis of understanding the technology and extending its capabilities that is open to anyone
Oh, to be young, naive, and ideological again....
No, that's NOT the point.
THE POINT is that if it can't add numbers to a companies bottom line, it will fade into obscurity in favor of something that does.
That's how the world actually works.
Re: (Score:2)
You do realise that most media centres run XBMC, which would have no problem supporting this standard.
HUH???
"MOST" media centers run a cable or satellite box. The "geeky" consumers *might* have a Roku.
XBMC is about as niche as you can get. Probably the only thing more niche would be MythTV. (Ignoring a bunch of also-rans that have about 7 users each.)
Re: (Score:2)
Umm not so much. I run multiple XBMC boxes and multiple friends of mine do as well. With the advent of cheap boxes like the Pivos it's cake to setup a dedicated XBMC box to stream all sorts of stuff. Adding in a Plex client allows them to stream from friend's Plex servers too. While XBMC may not dominate the average couch potato's home XBMC is pretty popular.
BTW that Roku box will also run a Plex client if you want to spend even less than a Pivos costs ($99).
Re: (Score:2)
Actually, all of them if you want to pay for it. I own a Roku XS 2 but I'm no longer a fan of the company after their last forced update now uses half the main menu for ads.
Re: (Score:2)
You do realize media centers running XBMC have AirPlay support already, right? And they actually support video and audio, where as this only supports audio.
I've had a Raspberry PI running XBMC with airplay support for at least a year, why would they want to downgrade to something that doesn't support video?
Re: (Score:2)
http://www.knowyourmobile.com/android-apps/18049/best-airplay-apps-android [knowyourmobile.com]
guess that means they all can?
I run Airplay on two stereo receivers and 3+ different XBMC boxes. I'll admit I've not bothered to put an Android implementation on my toy tablet but I guess I'll try it out. Airplay works great from both iPad and iPhone here though - to Linux\XBMC and to my Yamaha receivers.
No specs? (Score:4, Insightful)
The docs directory on github is essentially empty. If they can't even provide a formal specification they are no better than reverse engineered versions of airplay. What a fucking joke.
Specifications vs Code (Score:2)
The docs directory on github is essentially empty. If they can't even provide a formal specification they are no better than reverse engineered versions of airplay. What a fucking joke.
Unfortunately I and I suspect most here are in the camp of understanding *code*(especially if its well designed) over a *formal specification*, and had a working implementation. The whole point of Airplay is to replace it, because its a proprietary protocol stack/suite developed by the most litigious company on the planet.
Re: (Score:2)
Unfortunately I and I suspect most here are in the camp of understanding *code*(especially if its well designed) over a *formal specification*, and had a working implementation.
That's a little hard to parse - are you trying to rationalize standardization without a formal spec? Code is full of bugs and idiosyncrasies - it is in no way a reasonable basis for a standard.
Re: (Score:2)
Unfortunately I and I suspect most here are in the camp of understanding *code*(especially if its well designed) over a *formal specification*, and had a working implementation.
Well I'm certainly not. Documentation is invaluable. You know what we don't need? More re-implementations / re-imaginings of existing things (protocols, new languages, etc etc). You know what we do need? More and better documentation - and possibly better tools too.
Also I don't understand your use of the term 'Unfortunately' here. Are you saying that your position here is unfortunate? And if so, why don't you change your position? Or are you saying that it's unfortunate for those that do think documentation
Re: (Score:2)
But what part of the code is code, and what part is spec? That's the problem. If I decide that since I see a "2" that means the number of channels, can I insert "8" because I want to send
Re:No specs? (Score:4, Insightful)
You are obviously interested in documentation of this project.
Yes, I wanted to know how many channels, what resolutions, what formats and what sorts of latencies "maigcplay" could handle. So I went looking for documentation and found no answers.
Go fucking write the fucking specification then!
If the developers don't care enough to document their own protocols, I sure as fuck ain't going to do for them. Chances are its full of holes anyways, anyone who codes without a plan ends up with crap.
Re:No specs? (Score:5, Insightful)
Re: (Score:2)
The other thing I notice is missing besides the spec is industry co-operation. Without specs, the industry will simply do what's necessary to get the features they want.
No video support? Guess what? Yamaha will
Re: (Score:2)
That doesn't appear to document the protocol on the wire, just individual functions and their arguments.
UPNP AV (Score:4, Interesting)
There's already a competing open standard. [wikipedia.org]
It's what I use with my android devices (via BubbleUPNP [google.com]), XBMC and my Squeezebox.
My raspberrypi already does this ... better (Score:2)
For the Linux fans out there, I've written up some instructions on how to turn your Raspberry Pi into a MagicPlay device.
... My RaspberryPI has AirPlay support ... audio AND video ...
Great that its a BSD licensed alternative, but being that non of my devices will ever support this protocol, but they all support AirPlay, this is going to have a hard time gaining traction until it does what AirPlay does. Until then its just another silly protocol to do what we already can do, and do it better than this.
Not an AirPlay competitor... (Score:3)
Oh good! An AirPlay competitor! I wonder what video codec they used... Lemme just look through the code and...
Oh. It seems it doesn't support video at all. Not really an AirPlay competitor then...
Re: (Score:1)
Re: (Score:2)
Umm, video? I use it to stream Youtube vids from my iPad and iPhone to my XBMC boxes so I can see it on a bigger screen. Video is pretty important! I wish someone would do the desktop part for Linux now too just to complete things...
Re: (Score:2)
AirPlay is a marketing name for 3 different protocols: AirTunes (RTSP-based music streaming protocol), AirPlay (video files served up over HTTP) and AirPlay Mirroring.
Guess which use case is the most popular.
So it would be the open source AirTunes, not an open source AirPlay. Title is still wrong.
What a bunch of jerks... (Score:1)
For a streaming protocol... (Score:2)
the site is remarkably content-free. In particular, is this just a nice implementation of SAP/RTP, and if not, why? Even AirPlay is just RTP with an obnoxious (and broken) encryption on the payload.
so... (Score:1)
If they worked with airplay, I might consider them - for those who haven't used it before, it just simply ROCKS to be able to stream audio or video on one device (e.g., AppleTV,
Sonos (Score:2)
It's basically Sonos... from 8 years ago, except open source and without the hardware. Apple Airplay is great for video, but the Airplay Extreme audio players are a kludgy joke compared to Sonos. You want something that just works today get a Sonos. Yeah, Sonos is not cheap, but I feel that the price premium was paid in full and then some with all the updates and feature enhancements. I'm using hardware that's 5 years old now and it's still rock solid with all the features and services a new unit would
The article is misleading.. (Score:2)
"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.
Not true. AirPlay (as well as AirPrint) is an open standard. I've a couple of Android applications which transmit to my AppleTV without a problem. It's really the unwillingness of the hardware developers and/or Google to make use of that standard, being the only reason they can't make use of AirPlay.
Re: (Score:3)
No, sorry it's not open. It uses encryption and the only reason why some of the features work on Linux or elsewhere is because the crypto key was found in a firmware update. That is why when some IOS updates have come out Shairport etc. has gotten broken on Linux, Apple changed the keys. Once the new keys are figured out support resumes.
http://en.wikipedia.org/wiki/AirPlay [wikipedia.org]
Re: (Score:2)
No, sorry it's not open. It uses encryption and the only reason why some of the features work on Linux or elsewhere is because the crypto key was found in a firmware update. That is why when some IOS updates have come out Shairport etc. has gotten broken on Linux, Apple changed the keys. Once the new keys are figured out support resumes.
http://en.wikipedia.org/wiki/AirPlay [wikipedia.org]
From that same article you quoted.
"Originally only implemented in Apple's software and devices, Apple has licensed the audio-streaming portion of the AirPlay protocol stack as a third-party software component technology to manufacturer partners for them to use in their products in order to be compatible with Apple's iDevices."
There is aboslutely nothing stopping anyone from licensing software to enable this capability. A third party developer could license this for software. Hardware developers can lice
Re: The article is misleading.. (Score:2)
Is there something about the term "open standard" that you don't understand? Licensing technology does NOT make it open. Publishing, openly, how something works and the data is formatted to interoperate would be making it "open"....
Not quite Airplay? (Score:2)
Like most people, I'm mostly interested in the capability to stream audio to all kinds of devices. And people have already pointed out some key differences with DLNA that explain why there is reason to be happy with something like MagicPlay.
But Airplay offers streaming of audio, as well as video, photo's and screen mirroring. I haven't looked into the source yet, but going by the description, it looks like MagicPlay doesn't offer any of that and sofar nobody is planning to add it. Has anyone looked at the s
Re:What about UPnP? (Score:4, Informative)
Bingo! urn:upnp-org:serviceId:AVTransport & urn:upnp-org:serviceId:ContentDirectory already provide this... and have been implemented in quite a few devices & OSes.
Re:What about UPnP? (Score:4, Insightful)
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.
Re: (Score:2)
The rest of it!
Re: (Score:2)
DLNA interoperability can be surprisingly poor and using DLNA means using bandwidth-inefficient MPEG2 video and crummy stereo audio, which is kind of a let down if you have decent source files to work with.
Re: (Score:2)
Odd, I've never had much trouble streaming 5.1 DD and DTS over DLNA. Or h.264.
Re: (Score:2)
Re: (Score:2)
I'll agree that I haven't found much of a use case, for myself, for wifi speakers.
But my bluetooth speaker gets enough use that I bought a higher amp charger for it so it would have less downtime. I love that thing.