AppleTV 6.0 requires Fairplay-DRM Airplay Sources
weblog.rogueamoeba.com
weblog.rogueamoeba.com
Of course, Windows users are pretty screwed.
Both of these things you can do with the built in AirPlay support in 10.8+
Typical use case for me using Airfoil: Send Spotify output to an AppleTV, and a couple Airport Express devices, while all other apps send their output to my Mac's speakers.
F you Apple. Nobody has cracked the open streaming audio nut, trivial as it may be. And the rest are left with junk, proprietary crap like this.
Consider that AppleTV 6.0 now allows "AirPlay via iCloud", which means you can stream tracks you own on someone else's AppleTV where you haven't registered your iTunes account. Such a change might be one of the reasons for FairPlay encryption.
This might be a temporary issue where they open it up if enough people complain.
Well, RogueAmoeba wares was always a bunch of semi-legal stuff, utilizing kernel hacks, private APIs and such.
Maybe it should be looked at on a per-app basis. or company. Apple should have relationships with these very talented software shops. They should of course not support anything that would cause harm. In my wildest dreams, right?
Ummmmm, I'm going to call BS on that. If What RA was doing was illegal Apple would have shut it down ASAP - especially if it was with regard to using some undocumented features of the core OS that Apple wanted to protect. We're talking about streaming audio here - locally on your network (yes, there is the possibility of routing this across networks but if you're going through that much trouble you can implement a homegrown system much more reliably).
I find it interesting people go to bat for Apple when Apple screws over devs that makes a great product - and obviously are fans of Apple, and no, nothing RA was selling was illegal, that's just unfounded FUD. I've asked RA repeatedly to just build an interoperable product that has it's own streaming components that runs this way on Linux. At the time they said they had no plans - I really hope Apple pushes these guys over the edge to build products that can bridge the OS gap. Apple won't ever do anything along those lines.
Or using File/Add to library (Cmd-O) in iTunes.
Still recovering from this one, b/c I didn't know that it would do that...
Whether or not Apple does something in the future is a separate question, but accusing them of something they haven't done (despite several opportunities) appears more than a little biased.
Update: I am 100% incorrect about the developer certificate being free. You must be a member of the $99/yr Mac dev program to get one. So score one for "raising the walled garden" and I will gladly eat this humble pie.
IMO they are being complete shitbirds about app signing and I am actually surprised to hear Mavericks is not more restrictive. I fully expect them to lock it down at some point. (I've resolved to use only FOSS in the future and not buy Apple.)
Also I want really fine-grained permissions that I can disable to make system calls return fake information a la Cyanogen Mod.
then does that mean all the CA's in my system keychain can sign apps and have them run without the "risky click" dialog?
That's what the "computers" tab is for.
And honestly, if Google had any intention of having generally open access to it, they would have started with DLNA support, which would have allowed many phones to push to it out of the box. Instead expect it to stay heavily locked down and to only provide good support for getting users on to Chrome and Google Play.
http://static.fsf.org/nosvn/stickers/DBD-Sticker_002-jmt.svg
Apple does not help with Airfoil. They would prefer it to simply go away. Interoperability is not their thing here.
I worked on Airfoil at RA for years, including a couple of major updates and many workarounds for problems like these (although generally less severe). Apple never returned our metaphorical calls.
Ten seconds of running WireShark and watching iTunes talk to an AppleTV running v6 will give you something like that, where iTunes and the AppleTV do much talking about 'fp-setup' and FPLY and handshake together.
Apple's AirPlay (AirTunes) devices have actually been doing these FPLY verifications for years now, but they were optional and talking to the devices with the older non-FPLY protocol worked. It's just as of Apple TV 6.0 that they appear to be dropping the old connection exchange and requiring the FPLY one to talk to the device.
I'm not quite sure what you think we have to gain by claiming we think FairPlay is required now, when it really wasn't? This weblog post was to inform our customers about an issue with our software and ATV 6. We'd all dearly love a solution.
Also, iTunes content hasn't had DRM in years now, idiotic or otherwise.