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."

177 comments

  1. its not news yet by viperidaenz · · Score: 3, Insightful

    If there isn't wide spread hardware adoption, its a useless 'standard'

    1. Re:its not news yet by buchner.johannes · · Score: 4, 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.

      --
      NB: The message above might reflect my opinion right now, but not necessarily tomorrow or next year.
    2. Re:its not news yet by viperidaenz · · Score: 4, 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.

    3. Re:its not news yet by Anonymous Coward · · Score: 0

      If there isn't wide spread hardware adoption, its a useless 'standard'

      And unless it's a 'standard', it won't get adopted .

      Catch-22.

    4. Re:its not news yet by buchner.johannes · · Score: 1

      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.

      --
      NB: The message above might reflect my opinion right now, but not necessarily tomorrow or next year.
    5. Re:its not news yet by TigerTime · · 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.

    6. Re:its not news yet by Anonymous Coward · · 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?

    7. Re:its not news yet by bonehead · · Score: 1

      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.

    8. Re:its not news yet by smash · · Score: 0

      Except that it's not even an alternative yet, as it doesn't do video...

      --
      I run: Windows, OS X, Linux, FreeBSD. Just because you have a hammer, doesn't mean everything is a nail.
    9. Re:its not news yet by MindPhlux · · 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.

    10. Re:its not news yet by grouchomarxist · · Score: 1

      This is slashdot. It is supposed to be a site about up and coming technologies, not just about established technologies.

    11. Re:its not news yet by bonehead · · Score: 1

      Right. I think I said something like:

      and "will have a subset of the functionality of the existing, successful product".

    12. Re:its not news yet by bill_mcgonigle · · Score: 0

      than a handful of irrelevant people who made a pretty website and metioned the Raspberry Pi

      Hey, when I read this I thought, "oh, look, something useful to do with those buggy-as-shit RPi's I got conned into buying," and then I went and read their site:

      Optional: USB sound card for better quality (the integrated sound card on the Raspberry Pi has an annoying crackle bug)

      <cartman>Goddammit!</cartman>

      --
      My God, it's Full of Source!
      OUTSIDE_IP=$(dig +short my.ip @outsideip.net)
    13. Re:its not news yet by viperidaenz · · Score: 1

      Why would you use AirPlay then, if you can just connect a macbook to everything and use plain old itunes?

    14. Re:its not news yet by viperidaenz · · Score: 2

      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.

    15. Re:its not news yet by viperidaenz · · Score: 0

      But they won't, because this isn't a standard.

    16. Re:its not news yet by viperidaenz · · Score: 0

      This is slashdot.

      So that explains why the editors don't know the difference between a standard and someone's pet project.

    17. Re:its not news yet by similar_name · · Score: 1

      Turn in your geek card. This is /. It's News for Nerds (it's still in the title tag). BSD and streaming music over wifi is what this site is all about. Above all else, Slashdot is never ahead of the news.

    18. Re:its not news yet by moderatorrater · · Score: 1

      Slashdot.org is not a newsfeed for Pintrest and Best Buy shoppers

      That might have been true a few years ago...

    19. Re:its not news yet by zieroh · · Score: 4, 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.

      --
      People who say "sheeple" have about as much sophistication as an AOL user, and in fact are probably actually AOL users.
    20. Re:its not news yet by Anonymous Coward · · Score: 0

      The problem is that requires foreseeing future problems and needs.

    21. Re: its not news yet by alex.ecorrespondence · · Score: 1

      You do see the words "open standard" in the article, right? Now please go and check the references, come back and say sorry for being a jerk. A decent person would do so. Even if it was saying just "standard" it would still be OK. No, really. "Standard" has little to do with market coverage or the extent of adoption. It is merely a documented, accessible and hopefully rational way of doing or approaching something. Adhering to it is a choice. Perhaps you were thinking about "defacto standard"? Sometimes big businesses make a marketing cocktail of licensing/patent/branding/intimidation and call that mess euphemistically "a standard". Is that what you were thinking of? What were you thinking? Perhaps my idiomatic english skills leave a lot to be desired... Or did I just feed a troll?

    22. Re:its not news yet by ThatsNotPudding · · Score: 1

      If there isn't wide spread hardware adoption, its a useless 'standard'.

      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.

    23. Re:its not news yet by Anonymous Coward · · Score: 0

      This is slashdot. It is supposed to be a site about pissing on others while dodging the piss of others!

      There, fixed that for ya.

    24. Re: its not news yet by Anonymous Coward · · Score: 0

      A person who not unlike Google likes to call a standard whatever he likes logs in using Google+. How funny!

    25. Re:its not news yet by Anonymous Coward · · Score: 0

      a group did decide on it just not one you mention.

      A hearty "You Mad Bro?" definitely warranted here.

      You are the reason we can't have nice things.

    26. Re:its not news yet by Medievalist · · Score: 1

      If there isn't wide spread hardware adoption, its a useless 'standard'

      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.

    27. Re:its not news yet by Anonymous Coward · · Score: 0

      4K TV? I guess that's covered under the HDMI supported resolutions.

      There is no agreed-upon standard for displaying 4K content in consumer electronics (DCI handles pro equipment), although the HDMI specification theoretically supports two different resolutions at 24-30Hz. I am not looking forward to my clients buying all these amazing [sic] 1st-gen 4K TVs that won't be compatible with any of the source devices coming out in the next couple years.

    28. Re:its not news yet by Anonymous Coward · · Score: 0

      Obligatory xkcd...

    29. Re: its not news yet by viperidaenz · · Score: 1

      I checked the references, this is Qualcomm trying to get in to the wireless streaming market.

    30. Re:its not news yet by crutchy · · Score: 0

      yet

      i guess you think we should all go back to using IE6 too

    31. Re:its not news yet by crutchy · · Score: 0

      where on the internet does it say HTML5 browser?

      nowhere? thought so. not really a standard then is it

    32. Re:its not news yet by Anonymous Coward · · Score: 0

      OK, let's write up the business plan. Pick an existing, successful, and widely implemented technology. Come up with an alternative.

      linus torvalds and his dodgy homebrew alternative to unix in 1991

      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"

      fast forward 22 years...

    33. Re:its not news yet by Anonymous Coward · · Score: 0

      Since when was IE6 a standard? At no point during its lifetime was it ever close to providing standard compliance.

    34. Re:its not news yet by Squeeonline · · Score: 1

      If there isn't wide spread hardware adoption, its a useless 'standard'

      Oblig. XKCD

    35. Re:its not news yet by Anonymous Coward · · Score: 0

      This has got to be one of the dumbest posts I've read in 15+ years on this site.

      Although not half as brain-dead as the idiots who modded this up.

  2. What about UPnP? by Anonymous Coward · · Score: 0

    I'm confused as to why UPnP/DLNA isn't up to this task?

    1. Re:What about UPnP? by DaHat · · Score: 3, 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.

    2. Re:What about UPnP? by Anonymous Coward · · 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.

    3. Re:What about UPnP? by Anonymous Coward · · Score: 0

      What is bad about it?

    4. Re:What about UPnP? by NatasRevol · · Score: 1

      The rest of it!

      --
      There are two types of people in the world: Those who crave closure
    5. Re:What about UPnP? by Anonymous Coward · · Score: 0

      That's not a streaming protocol (it serves up files over HTTP). It also does not support synchronized streaming to multiple speakers.

  3. Just because it's there doesn't mean it'll be used by tumnasgt · · 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.

  4. Incompatible with AirPlay? by MrEricSir · · Score: 4, 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?

    --
    There's no -1 for "I don't get it."
    1. Re:Incompatible with AirPlay? by jawtheshark · · Score: 2

      Obligatory XKCD.

      --
      Ahhh...the great dumpster continuum. Many a free computer will be found there. -- sowth (748135)
    2. Re:Incompatible with AirPlay? by Anonymous Coward · · Score: 0

      Right. Because once you have one of something there is never a need for an alternative

    3. Re:Incompatible with AirPlay? by Qwavel · · 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.

    4. Re:Incompatible with AirPlay? by bonehead · · Score: 3, 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.

    5. Re:Incompatible with AirPlay? by Anonymous Coward · · 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 even require clients to advertise, let alone to allow remote control.

    6. Re:Incompatible with AirPlay? by exomondo · · Score: 1

      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.

    7. Re:Incompatible with AirPlay? by Anonymous Coward · · Score: 0

      Um, because AirPlay is proprietary.

      A fact irrelevant to all but a niche group of nerds. Come back to us when you have broad manufacturer support not some attribute that next to no one cares about.

    8. Re:Incompatible with AirPlay? by Anonymous Coward · · Score: 0

      HDMI is proprietary too, but I'd have a hard time arguing that a competing open standard would improve the current landscape.

    9. Re:Incompatible with AirPlay? by MrEricSir · · Score: 1

      Um, because AirPlay is proprietary.

      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?

      --
      There's no -1 for "I don't get it."
    10. Re:Incompatible with AirPlay? by bonehead · · Score: 1

      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.

    11. Re:Incompatible with AirPlay? by aXis100 · · Score: 2

      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.

    12. Re:Incompatible with AirPlay? by bonehead · · Score: 1

      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.

    13. Re:Incompatible with AirPlay? by Anonymous Coward · · Score: 0

      Except DLNA, unlike AirPlay and Sonos, do not support synchronized audio streaming. In fact, it's not a streaming protocol at all. With DLNA the original source files are served up over HTTP which means you're screwed when the DLNA device you bought doesn't support the codec needed to play a particular file.

    14. Re:Incompatible with AirPlay? by smash · · Score: 0

      So is MP3, h.264, Active Directory and GIF. None of those are going away any time soon. You can either accept that and deal with it, or invent a new incompatible and functionally incomplete (no video) standard that nobody uses and thus, nobody will use.

      --
      I run: Windows, OS X, Linux, FreeBSD. Just because you have a hammer, doesn't mean everything is a nail.
    15. Re:Incompatible with AirPlay? by bonehead · · Score: 1

      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.

    16. Re:Incompatible with AirPlay? by Anonymous Coward · · Score: 0

      This is how far Slashdot has fallen. Open standards aren't important, some douchbag's iPhone is.

    17. Re:Incompatible with AirPlay? by almostinsane · · Score: 0

      Nothing to do with Slashhdot. Its a reflection of how society has grown.

    18. Re:Incompatible with AirPlay? by Anonymous Coward · · Score: 0

      Like what? I've tried PS3 Media Server & XBMC to send audio & video from XP to PS3 over 802.11g - a pretty pedestrian setup - and consistently have problems, both in terms delays in browsing file lists and in playback.

      Being able to play audio from the device that holds it and leave the rest to the speakers / receivers is a much more (to my mind) sensible division of labor than the contortions involved in DLNA.

    19. Re:Incompatible with AirPlay? by Anonymous Coward · · Score: 0

      AirPlay is live streaming audio though; that is pretty much all it does it is simplicity at its finest. I can airplay voice chat or game audio from my macbook to my wifi base station.
      The AirPlay devices in my house simply show up as audio devices on my computer.

    20. Re:Incompatible with AirPlay? by Dynedain · · Score: 1

      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!

      --
      I'm out of my mind right now, but feel free to leave a message.....
    21. Re:Incompatible with AirPlay? by cyber-vandal · · Score: 1
    22. Re:Incompatible with AirPlay? by vanzylst · · Score: 1

      I use the following which works reasonably well: - ArkMC iPhone app as Remote - minidlna Server - Samsung F8000 Smart TV Player The big benefit over the the Samsung's built-in DLNA player is that you can actually change the stream playback position, using a slider, rather than a very slow and tedious swiping of the Samsung remote to get to where you want. Problems with this setup is that the Remote is very basic, cannot for example sort items differently than just alphabetically, uses too much screen space to display the entries, etc., etc.

    23. Re:Incompatible with AirPlay? by Anonymous Coward · · Score: 0

      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.

      I just had a play with this with an android tablet and my Serviio DLNA server. I purchased a couple of apps to test and 2player (https://play.google.com/store/apps/details?id=com.twoplay.twoplayer2&hl=en) was the only Android DLNA renderer with DLNA control point that I could find that worked properly. I'll probably get an android stick to hook up to the amp, to save having to turn on the TV just to select/play music.

    24. Re:Incompatible with AirPlay? by Anonymous Coward · · Score: 0

      using minidlna with a upnp/dlna streaming out audio driver in phonon you can recreate an airplay-type setup with your OSS tools. right now. i've been running it for awhile. there are android apps which let you stream from one DLNA source to another. what does not exist yet, is audio redirection on the android. output goes to speaker, headphones, or bluetooth. you cannot redirect the audio to a DLNA source

    25. Re:Incompatible with AirPlay? by Medievalist · · Score: 1

      Grown? I don't think that word means what you think it means.

      I've had streaming, synchronized, multi-room wireless music playback in my home for quite a few years now. And until I read this forum, I was barely aware that "AirPlay" existed!

  5. Xbmc still wins by Anonymous Coward · · Score: 0

    Xbmc and phone based remote apps do the job. wifi speakers are overkill.

    1. Re:Xbmc still wins by bonehead · · Score: 1

      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.

  6. Lots of protocols for music over the network by loufoque · · Score: 1

    There are lots of protocols to play music over the network. This summary suggests there was none but AirPlay.

    1. Re:Lots of protocols for music over the network by Anonymous Coward · · 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 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.

    2. Re:Lots of protocols for music over the network by bonehead · · Score: 1

      Mod this up +100, AC or not.

    3. Re:Lots of protocols for music over the network by Anonymous Coward · · Score: 0

      Besides AirPlay and Sonos (both proprietary), which protocols support synchronized audio streaming over WiFi?

    4. Re:Lots of protocols for music over the network by MightyYar · · Score: 1

      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 practical implementations.

      --
      W..w..W - Willy Waterloo washes Warren Wiggins who is washing Waldo Woo.
    5. Re:Lots of protocols for music over the network by smash · · Score: 0

      Agreed. Beta software with zero hardware support partially solves solved problem (no video)!

      I like open standards as much as anyone, but the ship already sailed (9 years ago), and there are already open source implementations and quality hardware to support a working (and it works well, at that) protocol.

      Spend development resources on something that ISN'T solved.

      This is a bit of a problem with open source in general from what I've seen in the past 18 years. No, we don't want a brand new replacement for some half baked media player in our new desktop that does almost the same stuff, with a different UI and different bugs.

      As with starting a new thread when forum posting - use the fucking search engine. If a problem is ALREADY SOLVED (even partially, or in progress), then contribute to the existing project and make it better, rather than starting over and reinventing the wheel for the 50th time.

      --
      I run: Windows, OS X, Linux, FreeBSD. Just because you have a hammer, doesn't mean everything is a nail.
    6. Re: Lots of protocols for music over the network by loufoque · · Score: 1

      What does synchronous mean in this context?

    7. Re: Lots of protocols for music over the network by Anonymous Coward · · Score: 0

      That when playing on several different devices, there is no delay difference.

      Regular streaming to multiple devices can result in a several second difference, so when you stand between two different players, one is noticably behind the other, kinda like an echo.

    8. Re: Lots of protocols for music over the network by MightyYar · · Score: 1

      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.

      --
      W..w..W - Willy Waterloo washes Warren Wiggins who is washing Waldo Woo.
    9. Re: Lots of protocols for music over the network by loufoque · · Score: 1

      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.

  7. Good thing! by Anonymous Coward · · Score: 0

    Android users have been left out in the cold.

    Hey, this sounds like a good thing!

  8. Incompatible with Upnp by tuppe666 · · Score: 1

    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 works* with their proprietary garbage. Personally I hope this...and Airplay die a death.

    1. Re:Incompatible with Upnp by smash · · Score: 2, 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.

      --
      I run: Windows, OS X, Linux, FreeBSD. Just because you have a hammer, doesn't mean everything is a nail.
    2. Re:Incompatible with Upnp by Anonymous Coward · · Score: 0

      Actually AirPlay does so much less than UPnP or DLNA, that is why it works so much better.
      It is simply and remote audio and video device.

      You simply send an audio stream to an airplay device and it will play it back as audio.

      In OS X the AirPlay devices simply show up as an audio device (I don't have a video airplay device), which you can use to direct audio from any application to.

      However UPnP, DLNA requires media servers, controlling devices to play back media.

      If you want to route your application's audio with UPnP, DLNA to a remote audio device, you will need a media server that shows up as an audio device on your computer, which then makes a stream for it, then advertises that stream, then you need to use remote control to tell the remote audio device to play back this stream. If that doesn't seem a bit round about to you, then you are not a very good engineer.

  9. Wish idiots would understand how to quote by tuppe666 · · Score: 2

    Obligatory XKCD.

    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.

    1. Re:Wish idiots would understand how to quote by Anonymous Coward · · Score: 0

      You might want to go back and read the GGP.

  10. Already dead on arrival. by DMJC · · Score: 5, 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 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.

    1. Re:Already dead on arrival. by Anonymous Coward · · Score: 0, Informative

      You do realise that most media centres run XBMC, which would have no problem supporting this standard.

    2. Re:Already dead on arrival. by Anonymous Coward · · Score: 0

      Haha you waste your money on crap that sounds woody or purple.

    3. Re:Already dead on arrival. by bonehead · · Score: 1

      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.)

    4. Re:Already dead on arrival. by BitZtream · · Score: 1

      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?

      --
      Persistent Volume manager for Kubernetes - https://github.com/dwimsey/openshift-pvmanager
    5. Re:Already dead on arrival. by Anonymous Coward · · Score: 0

      "Linux already supports Airplay" is a nonsensical statement. What is this Linux product you speak of? Just because geeks can hack together a working AirPlay solution in their basement doesn't mean it's of any relevance to the mass market (where a company could get sued for using Apple's proprietary protocol without authorization). Can you point to an Android phone from Samsung or HTC that supports AirPlay? Can you point to to a WiFi speaker from Bose that works with an Android phone?

    6. Re:Already dead on arrival. by BLKMGK · · Score: 1

      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).

      --
      Build it, Drive it, Improve it! Hybridz.org
    7. Re:Already dead on arrival. by BLKMGK · · Score: 1

      http://www.knowyourmobile.com/android-apps/18049/best-airplay-apps-android

      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.

      --
      Build it, Drive it, Improve it! Hybridz.org
    8. Re:Already dead on arrival. by almostinsane · · Score: 0

      Less niche is Windows Media Center and even that is a dying group.

    9. Re:Already dead on arrival. by waspleg · · Score: 1

      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.

    10. Re:Already dead on arrival. by Anonymous Coward · · Score: 0

      You could feel good about using an open "standard". I'm sure it supports ogg, as well.

  11. DLNA Called by Anonymous Coward · · Score: 0

    And wants their features back.

    My uncle has a PS3 and his laptop hooked up together no problem. My 5 year old laptop also has no problem streaming to any DLNA compatible device.

    1. Re:DLNA Called by slaker · · Score: 1

      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.

      --
      -- I wanna decide who lives and who dies - Crow T. Robot, MST3K
    2. Re:DLNA Called by bonehead · · Score: 1

      Odd, I've never had much trouble streaming 5.1 DD and DTS over DLNA. Or h.264.

    3. Re:DLNA Called by smash · · Score: 0

      DLNA does not support the same feature set as airplay.

      --
      I run: Windows, OS X, Linux, FreeBSD. Just because you have a hammer, doesn't mean everything is a nail.
    4. Re:DLNA Called by GrahamCox · · Score: 1

      And it's crap. 8.3 format filenames in 2013? Get out of here.

    5. Re:DLNA Called by Anonymous Coward · · Score: 0

      MPEG2 is just the minimum mandated support. The client can (and, in almost all cases, does) support other codecs.

  12. accessory manufacturers are desperate by tuppe666 · · Score: 0

    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 times. Recently I am seeing those same shelves occupied with Apple products filled with those with *open*(yes I am playing hard and loose with the word-Pretend your reading this on Ars) standards like Bluetiooth, USB...and even old 2.5mm Headset Jack.

    The days of the iPod are over...any Apple proprietary anything (protocol stack/suite; connector...seriously anything) is a strategic disadvantage on their part.

    1. Re:accessory manufacturers are desperate by Anonymous Coward · · Score: 0

      +1: Funny. I knew there would be a humorous post in this thread.

    2. Re:accessory manufacturers are desperate by 93+Escort+Wagon · · Score: 4, 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.

      --
      #DeleteChrome
    3. Re:accessory manufacturers are desperate by NatasRevol · · Score: 0

      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!

      --
      There are two types of people in the world: Those who crave closure
    4. Re:accessory manufacturers are desperate by Anonymous Coward · · Score: 0

      Didn't you hear? iPods have no wifi and less space than a Nomad, lame. Also Microsoft are dying, Apple are dying, Google do no evil and it's the Year of the Linux Desktop!

    5. Re:accessory manufacturers are desperate by Zontar+The+Mindless · · Score: 1

      Not until Netcraft confirms it.

      --
      Il n'y a pas de Planet B.
  13. Miracast by Anonymous Coward · · Score: 0

    Seems like Miracast will be much more likely to be the alternative: http://en.wikipedia.org/wiki/Miracast

    1. Re:Miracast by Anonymous Coward · · Score: 1

      Seems like Miracast will be much more likely to be the alternative: http://en.wikipedia.org/wiki/Miracast

      Nope. Shitty name.

  14. okay.jpg by Anonymous Coward · · Score: 0

    Got my hopes up, thinking it'd let me mirror into desktops/laptops. There's software out there that does it, but that idea is almost as stupid as the "suggestions" that tell mac users to shell out $60+ when they ask about a Volume Mixer equivalent.

  15. Open-ness is the point. by Anonymous Coward · · 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.

    1. Re:Open-ness is the point. by bonehead · · Score: 1

      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.

    2. Re:Open-ness is the point. by Anonymous Coward · · Score: 0

      Oh, to be young, naive, and ideological again....

      I assure you that I am semi-old and quite jaded.

      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.

      No, that is why the world works so poorly. That and the resignation to quietly accept whatever you are given by The Market.

  16. No specs? by Jah-Wren+Ryel · · Score: 3, 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.

    --
    When information is power, privacy is freedom.
    1. Re:No specs? by Anonymous Coward · · Score: 0

      You sound like a marketing scumbag. Or are you the guy that delivers specs to the developers because developers can't talk to users?

      You're pointless and unnecessary.

    2. Re:No specs? by Anonymous Coward · · Score: 0

      You are obviously interested in documentation of this project. Go fucking write the fucking specification then! It's an open source project which means interested people contribute. Another option is that you can stick with your proprietary white and glossy expensive black boxes.

    3. Re:No specs? by Jah-Wren+Ryel · · Score: 3, 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.

      --
      When information is power, privacy is freedom.
    4. Re:No specs? by smash · · Score: 4, Insightful

      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.
    5. Re:No specs? by PanAmaX · · Score: 1

      get the code.. run doxygen on it.. it will generate you out some documentaion

    6. Re:No specs? by Jah-Wren+Ryel · · Score: 1

      That doesn't appear to document the protocol on the wire, just individual functions and their arguments.

      --
      When information is power, privacy is freedom.
    7. Re:No specs? by PanAmaX · · Score: 1

      Sorry, I should have read the subject line of your post rather than just the content

      I responded to the doc folder being empty, which in no way answers your point about the "Specification" being completely MIA.

      you sir, make a valid point :D

    8. Re:No specs? by tlhIngan · · Score: 1

      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.

      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 introduce it! As will Pioneer, Onkyo, Marantz, etc. Oh, did I mention they were all incompatible with each other because they all went and did their own thing?

      Without a clear roadmap of when support will be added and clear industry contacts, "take the code and use it" doesn't get very far because each company wants to add their own "special sauce" to the mix.

      And yes, this work is boring and un-sexy and is akin to documentation, UX design and other skills that are often way undervalued amongst FLOSS programmers (I didn't say software engineers on purpose). Valuing code over everything else does not get acceptance.

      So to even get started, someone needs to be an industry liason and seek input - what do THEY want out of it? And when can they expect an implementation. And nothing wishy-washy - product cycles are short, lead times long and deadlines far closer than you think (e.g., if you want to make Holiday 2013, you must be ready with hardware and software now).

      Given it came out now, the earliest product will be ready is Holiday 2014. Maybe summer 2014 if everyone gets their act together and figures out how to talk to industry and how to handle their demands.

      And don't forget qualification testing. Some no-name Chinese brand may add it as a feature point if it compiles nicely into the code (if it doesn't, they'll chop stuff out until it does). But without a way to enforce quality standards and a test suite, these crap implementations may simply result in everyone going "Oh, it supports MagicCrap" because everyone sees stuttering, choppy playback as the result, or it not working at all because some vital bit is missing. (What, you expect testing?)

      Just because it's BSD doesn't mean it's accepted. It just means the license is acceptable. Industry knows what their customers (consumers to high end A/V professionals) want, and if there's demand, they'll provide it. And to do that they need to know how they can ask for improvements, help, assistance, qualification tests, etc.

  17. UPNP AV by AceJohnny · · Score: 3, Interesting

    There's already a competing open standard.

    It's what I use with my android devices (via BubbleUPNP), XBMC and my Squeezebox.

    --
    Misleading titles? Inflammatory blurbs? Keep in mind that Slashdot is a tabloid.
    1. Re:UPNP AV by Anonymous Coward · · Score: 0

      UPnP doesn't support synchronized streaming to multiple speakers (a major selling point for AirPlay and Sonos). In fact, it's not a streaming protocol at all. With UPnP the original source files are served up over HTTP which means you're screwed when the DLNA device you bought doesn't support the codec needed to play a particular file.

  18. SMB alternative by tepples · · Score: 1

    True, FTP and NFS are open alternatives to Server Message Block to an extent. But what's the open alternative to Super Mario Bros. and Super Monkey Ball?

    1. Re:SMB alternative by bonehead · · Score: 3, Funny

      TuxRacer, of course!

    2. Re:SMB alternative by bonehead · · Score: 1

      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.

  19. Poor Analogy by tuppe666 · · Score: 4, 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.

    1. Re:Poor Analogy by bonehead · · Score: 0

      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?

    2. Re:Poor Analogy by Anonymous Coward · · Score: 0

      No, not really. Both are standards with tons of 3rd party implementations.

    3. Re:Poor Analogy by smash · · Score: 0

      Developed by apple. Supported by a big list 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 require for the functionality.

      --
      I run: Windows, OS X, Linux, FreeBSD. Just because you have a hammer, doesn't mean everything is a nail.
    4. Re:Poor Analogy by thesupraman · · Score: 1

      Great, can you please point me to an airplay implementation for my android phone and tablet?

    5. Re:Poor Analogy by Anonymous Coward · · Score: 0

      Because apparently, as someone pointed out, you can't get it to work on Android since we all know that everyone use Android right? Right?.... pardon me a minute my blackberry is buzzing...

    6. Re:Poor Analogy by BLKMGK · · Score: 2

      http://www.knowyourmobile.com/android-apps/18049/best-airplay-apps-android

      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 :-)

      --
      Build it, Drive it, Improve it! Hybridz.org
    7. Re:Poor Analogy by TranquilVoid · · Score: 4, 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.

    8. Re:Poor Analogy by zieroh · · Score: 1

      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.

      --
      People who say "sheeple" have about as much sophistication as an AOL user, and in fact are probably actually AOL users.
    9. Re:Poor Analogy by jwdb · · Score: 1

      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 require for the functionality.

      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.

    10. Re:Poor Analogy by Attila+Dimedici · · Score: 1

      Who told you that you should give up Airplay? All of the comments I have seen defending either this story or the new standard have used the argument that Airplay is proprietary to explain why some people think an alternative is necessary. So far none of them have been claiming that YOU should go out and switch to this new standard right now.

      --
      The truth is that all men having power ought to be mistrusted. James Madison
  20. How is this new? I have Subsonic. by Anonymous Coward · · Score: 0

    What does this do that Subsonic doesn't? I can run Subsonic server on pretty much any platform and then stream to many different devices over 3g or Wi-Fi. Works great on any smartphone or laptop I've ever used, either through the web browser, or through a custom app.

    I can't imagine that implementing on speakers or on an RP would be very hard.

    What does this do that's different? Sounds like re-building the wheel and trying to generate hype to me.

    1. Re:How is this new? I have Subsonic. by Anonymous Coward · · Score: 0

      Wait - nevermind... MagicPlay/AirPlay implement the exact opposite of what's actually useful. I'll stick with Subsonic.

  21. Specifications vs Code by tuppe666 · · Score: 1

    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.

    1. Re:Specifications vs Code by Jah-Wren+Ryel · · Score: 1

      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.

      --
      When information is power, privacy is freedom.
    2. Re:Specifications vs Code by Anonymous Coward · · Score: 0

      Code is full of bugs and idiosyncrasies - it is in no way a reasonable basis for a standard.

      It may or may not be, depending on the code.

      The existence of a formal specification is not necessarily the basis for a standard either.

      The Constitution is a specification, and various laws throughout the US are code that is (effectively) based on this specification.

      All are full of bugs and idiosyncrasies.

    3. Re:Specifications vs Code by Anonymous Coward · · Score: 0

      You must be tripping. Laws are not software, not even close.

    4. Re:Specifications vs Code by brantondaveperson · · Score: 1

      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 is a good idea, in which case I agree with you.

    5. Re:Specifications vs Code by smash · · Score: 0

      A specification shows intent. Code shows whatever random joe coder interpreted as how he thinks the spec should work. No spec means that the design hasn't been formalised and thus, there is no testing possible to validate that it is correct and complies with the standard. It is a fact of life that coders write bugs.

      Relying on an initial version of a bit of code to hold up as your "spec" is only going to end in tears eventually.

      --
      I run: Windows, OS X, Linux, FreeBSD. Just because you have a hammer, doesn't mean everything is a nail.
    6. Re:Specifications vs Code by tlhIngan · · Score: 1

      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.

      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 a 7.1 stream? Or will I create an incompatible protocol because it was designed for 2.0 channel encoded L-R, and I tried to send it 7.1 as L-R-C-LS-RS-LP-RP-LFE ? Or if someone else had the same idea and decided it was best as L-R-LS-RS-LP-RP-C-LFE ?

      And what if there's a security flaw? Is that a spec item, or an implementation bug? Do I have to write my implementation with the same bug?

      One thing documentation does is it shows how you intended to do things. With code, you're not sure what was done for implementation and what was done per the spec.

      Is the "1.0" sent in the header a magic number? A version? Should I send "1.1" if I want to upgrade it to send an upgraded stream? Unless it supports everything out of the bat, people will want to expand it. Without documentation, you'll have like what happened to DLNA - you end up with a dozen slightly incompatible implementations. This was resolved in a later revision (UPnP/DLNA 3.0) that harmonized everything once and for all.

  22. My raspberrypi already does this ... better by BitZtream · · Score: 1

    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.

    --
    Persistent Volume manager for Kubernetes - https://github.com/dwimsey/openshift-pvmanager
  23. Not an AirPlay competitor... by maccodemonkey · · Score: 2

    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...

    1. Re:Not an AirPlay competitor... by Anonymous Coward · · Score: 1

      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.

    2. Re:Not an AirPlay competitor... by BLKMGK · · Score: 1

      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...

      --
      Build it, Drive it, Improve it! Hybridz.org
    3. Re:Not an AirPlay competitor... by Anonymous Coward · · Score: 0

      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...

      not better than airplay, just a weak copy... at least we know which audio codec they use : ALAC.... what's the point here ? i don't get the approach ? why using ALAC for an open source solution while FLAC is known to be better and open source by nature (ALAC is now open source, but still weak vs FLAC)...
      To me MagicPlay is a joke, not a revolution.

    4. Re:Not an AirPlay competitor... by maccodemonkey · · Score: 1

      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.

  24. What a bunch of jerks... by bitMonster · · Score: 0

    What a bunch of jerks you guys are. This is by DVDJon. Show some respect. To all the people that are going on about UPnP and DLNA, I don't think those do synchronized playback.

  25. For a streaming protocol... by chrylis · · Score: 1

    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.

  26. Logitech Media Server by Anonymous Coward · · Score: 0

    What does MagicPlay offer that Logitech Media Server doesn't?

    LMS is free software (GPL), can stream via LAN or WAN, can synchronize streams between multiple clients (e.g. to sync playback in multiple rooms), has a variety of clients (both hardware and software) available for playback and server control, is supported out-of-the-box by various Logitech products, is cross-platform (it's written in Perl), has numerous plug-ins available...

    Can anyone point out what advantages (if any) MagicPlay has over Logitech Media Server?

  27. Shairport. For RPi and XBMC already do this by Anonymous Coward · · Score: 0

    They implement the Airplay protocol nicely, so what's the deal?

  28. so... by smash · · Score: 0

    .... not compatible with Airplay = non-starter. Like it or not, there is an absolutely huge Airplay userbase already, and you're quite unlikely to get those users to give up their devices. Personally, I'm not about to go integrating another protocol at home simply to cater to a few open source devices that I don't even own yet.

    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, then pick up the iPad or iPhone, walk to another room and continue watching (say, while I go grab a drink), then flick back to the TV when I return - totally seamlessly and without losing my place, etc.

    Given there are already open source implementations of Airplay out there, I'm not sure what the usage case for this is? It doesn't even look to do video?

    --
    I run: Windows, OS X, Linux, FreeBSD. Just because you have a hammer, doesn't mean everything is a nail.
  29. Sonos by Kagato · · Score: 1

    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 have.

    I will give kudos to Logitech Squeezebox. They don't make them anymore and they weren't as fancy as Sonos, but they were a solid product they killed before it's time.

  30. consider streamripper by Anonymous Coward · · Score: 0

    This is something I've wondered about. You can use streamripper to convert an Internet audio stream to MP3, and/or re-stream it to multiple users on your local network. If that could be generalized, anyone could take music from *any* source (files, gstreamer/clementine/amarok, microphone, whatever) and create his own Internet radio station. If many thousands of these stations were popping up and disappearing all the time, the RIAA would have to give up! (Yes, I know about icecast. Try configuring it sometime.)
    Next step: do the same for Video streams. Everyone could have their own YouTube! Goodbye MPAA! BTW, isn't this the argument for symmetrical bandwidth?

  31. Duplicate efforts by Anonymous Coward · · Score: 0

    So what about Pulseaudio? Doesn't it have the same streaming capabilities?
    Or Bluetooth's A2DP?

  32. The article is misleading.. by Shadowmist · · Score: 1

    "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.

    1. Re:The article is misleading.. by BLKMGK · · 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

      --
      Build it, Drive it, Improve it! Hybridz.org
    2. Re:The article is misleading.. by Shadowmist · · Score: 1

      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

      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 license this to enable it on their devices.

    3. Re: The article is misleading.. by BLKMGK · · Score: 1

      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"....

      --
      Build it, Drive it, Improve it! Hybridz.org
  33. Won't Work by DrStrangluv · · Score: 1

    Even if they get this technically perfect, it can never work, because it will never be supported by Apple.

    I can already use AirPlay mirror to transmit not only my iPad/iPhone or Mac screen, but through additional software I can also mirror my Windows or Linux Desktop and even an Android tablet or phone. Oh, and the receiver doesn't have to be an AppleTV. A Mac or PC can receive streams as well. You can even hack a Pi or XBMC to receive AirPlay, too. The only major missing device categories today are Windows RT and Blackberry 10... and if they know what's good for 'em, they'll open up API's to make this possible. Apple's AirPlay is already the lingua franca of wireless A/V, even more so than technologies like WiDi.

    AirPlay today is already *everything* MagicPlay wants to be, with the exception that MagicPlay has virtually no chance of ever working on an iPad.

    The only way this changes is if Apple decides to go legal on the third party tools making this possible... tools which currently have their blessing... a move which would make no sense, as the core technology is too easy to duplicate (as proven by this very story). Moreover, the move would make some new enemies in tech circles and especially in education (historically an Apple stronghold), because at that point there will be no hope for places like conference centers/auditoriums/classrooms to easily have a single generic point of contact for wireless display.

    I will grant that if Apple does go for the legal option, MagicPlay could be well-positioned as a single alternative supported by all the competitors: Android, Windows (regular and extra-crispy metro), linux, etc

  34. Not quite Airplay? by Grismar · · Score: 1

    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 source and are they able to refute this?

    Calling MagicPlay "open source AirPlay" seems a bit of a stretch then. That's like calling AbiWord "open source Office". Of course the marketing department won't like it, but MagicPlay seems more like "open source RAOP" (Remote Audio Output Protocol, see the Unofficial AirPlay Protocol Specification ) with the added stuff required to nicely hook up sinks to sources.

  35. Unchallenged? by Anonymous Coward · · Score: 0

    So I must have been hallucinating streaming all my music via PulseAudio damn you, Lennart!

  36. vlc by Anonymous Coward · · Score: 0

    i had a grafic card with a yellow analog video-in connector and a white-red analog sound cable that went to the line-in on soundblaster. i would just configure vlc to capture from grafic card and line-in and then multicast to 235.255.255.255 and then (via wifi b standard) listen on other computers with vlc to the muticast stream. twas all very synchroneus. thank you for the satellit dish!

  37. bullsit by Anonymous Coward · · Score: 0

    I was streaming music via wifi long before crapple came up with a proprietary way to do it.

  38. so, if i pull up to the light by Anonymous Coward · · Score: 0

    beside a rapmobile, i could turn the volume down? or at least switch it to ambient music?

  39. DLNA? by Anonymous Coward · · Score: 0

    I use it fir android, linux, smart tv streaming.

  40. Re:Just because it's there doesn't mean it'll be u by Anonymous Coward · · Score: 0

    same was no doubt said re android vs ios a few years ago

    don't you morons ever get tired of being wrong all the time?