News for hackers. Stuff that matters.
Re:Chromecast now open to developers with the Google Cast SDK by UnoriginalGuy on Monday February 03, 2014 @01:32PM (#7172537)
I love my Chromecast and use it extensively. This is what Miracast should have been, something that "just worked" and seamlessly interconnected devices.

But instead Miracast is yet another classic example of "death of committee" where tons of big media and hardware companies wanted to get their features and DRM in, and as a direct result we now have dozens of completely incompatible Miracast devices.

I think this table accurately sums of the Miracast issue: http://i.imgur.com/I2QmeZe.jpeg

And that is my experience too. Samsung works only with other Samsung "allshare" devices, Sony works only with other Sony "Xperia" devices, and so on.

Ironically my Samsung TV has a YouTube app which can almost act like a Chromecast built in, and that is the only reliable way to stream content to the thing. I've never been able to get Miracast on either the Samsung or Sony to work reliably (both 2013 models).

My only slight complaint right now about Chromecast is that I cannot stream from VLC but hopefully with the release of this SDK that might change in time.

PS - If Chromecast becomes popular this really will isolate Apple's iTunes video. Most other video providers/renters work with Chromecast (Hulu, Netflix, Play Store, et al), or with apps on your TV already. Apple is the only large digital content provider which wants to force us to buy their proprietary device ("Apple TV") to watch their proprietary content. It really does decrease the value for Apple's content. In fact I'm just not going to buy Apple's DRM-ed video anymore, as I have to plug in a HDMI cable to watch it on my TV.

Re:Chromecast now open to developers with the Google Cast SDK by eclipxe on Monday February 03, 2014 @04:07PM (#7173494)
As someone who works day-in and day-out with Miracast devices, you're a little bit off. The problem isn't really with features and DRM leading to incompatibility. The HDCP portion of Miracast is pretty straightforward and isn't often the problem. The problem (as seen with the charts) is manufacturers that are sorta-kinda-using Miracast but not really. For example the Samsung AllShare devices were never advertised as Miracast capable, but they happen to work (sometimes). Same with the HTC Media Link. Customers get these dongles or TVs and expect it to work with other Miracast devices, even though they aren't really Miracast. Give the standard 2014, 2015 and let's see where we are.

The Chromecast comparison is really a bad one - yes you can tabcast, but really it is designed around a "send this URL to play" experience which is much much easier to accomplish than real-time streaming. For the real-time streaming, you only have a single sink device to worry about and it only works on desktops (for now). Your surface area is much smaller, so of course interop is going to be better.

Re:Chromecast now open to developers with the Google Cast SDK by UnoriginalGuy on Monday February 03, 2014 @04:34PM (#7173653)
> Give the standard 2014, 2015 and let's see where we are.

People said exactly the same thing about Miracast in 2013 and 2012. We still aren't anywhere with it. It is more broken than it is working, it is a giant mess.

> The Chromecast comparison is really a bad one - yes you can tabcast

You can fullscreen cast.

> but really it is designed around a "send this URL to play" experience which is much much easier to accomplish than real-time streaming.

Except for the tab casting and full screen casting..?

> For the real-time streaming, you only have a single sink device to worry about and it only works on desktops (for now).

You're strangely contradicting yourself. First you acknowledge that tab casting is a thing,then you pretend that tab casting isn't something it does and use that as justification for Miracast's superiority? Very confusing.

Also "only have a single sink device" is total gibberish. Even assuming the word "sync" it is still nonsense, both Miracast and Chromecast only support a single device on either end (sender and receiver).

PS - Chromecast works with other devices. It isn't just desktops. People already made apps that could send a full Android "desktop" to the Chromecast back in the early days before Google killed it with an update. I'm sure it will return with the release of this SDK.

> Your surface area is much smaller, so of course interop is going to be better.

It is an identical surface area between the two.

Re:Chromecast now open to developers with the Google Cast SDK by eclipxe on Monday February 03, 2014 @07:24PM (#7174619)
>People said exactly the same thing about Miracast in 2013 and 2012. We still aren't anywhere with it. It is more broken than it is working, it is a giant mess.

I'm glad your time-machine is working and you've experienced the 2015 ecosystem.

>You're strangely contradicting yourself. First you acknowledge that tab casting is a thing,then you pretend that tab casting isn't something it does and use that as justification for Miracast's superiority? Very confusing.

I'm not pretending tab casting isn't a thing. What I mean by "sink" is a device that receives the stream. Chromecast can do this because it controls both ends, the software you install on Chrome and the Chromecast device (the sink). Your surface area for testing and coverage is much smaller, vs a standard that is in hundreds of devices. Even then the feature is still not on mobile devices officially and is experimental.

>PS - Chromecast works with other devices. It isn't just desktops. People already made apps that could send a full Android "desktop" to the Chromecast back in the early days before Google killed it with an update. I'm sure it will return with the release of this SDK.

Yes, I've used Koush's Allcast app and it is nice. I'm not saying it won't happen (Android to Chromecast) - it will. But still you aren't getting what I'm saying here - there is only one target device you have to build for (Chromecast) not hundreds of TVs, BluRay players, and dongles.

>It is an identical surface area between the two.

I mean test and interop surface area. It is surely not identical. Your test matrix for Chromecast is n. For Miracast it is n^2. That is the real problem. Not your straw man about "DRM"

Re:Chromecast now open to developers with the Google Cast SDK by saltysugar on Tuesday February 04, 2014 @03:38AM (#7176197)
> here is only one target device you have to build for (Chromecast) not hundreds of TVs, BluRay players, and dongles.

Just chiming in, Google actually has plan to work with TV makers to integrate Chromecast technology into future smart TVs, and hopefully other peripheral devices too.

Re:Chromecast now open to developers with the Google Cast SDK by lsaferite on Monday February 03, 2014 @06:05PM (#7174199)
> "only have a single sink device"

I'm sure the OP was referring to source (sender) and sink (receiver) devices. And more specifically that the only current sink device is the Chromecast dongle.

Re:Chromecast now open to developers with the Google Cast SDK by UnoriginalGuy on Monday February 03, 2014 @06:32PM (#7174354)
That isn't accurate. The YouTube app on several TVs (e.g. Samsung) can receive Chromecast streams.
Re:Chromecast now open to developers with the Google Cast SDK by eclipxe on Monday February 03, 2014 @07:27PM (#7174630)
That isn't a Chromecast stream. It is an open standard called DIAL (http://www.dial-multiscreen.org/)

Specifically, only Tab casting/full screen casting works to Chromecast. Go ahead and cast your tab/screen to your Samsung TV. I'll wait.

Re:Chromecast now open to developers with the Google Cast SDK by lsaferite on Tuesday February 04, 2014 @03:22PM (#7180021)
Just as a gee whiz, DIAL is also what is used to send video from the NetFlix phone app to the NetFlix PS3 app.
Re:Chromecast now open to developers with the Google Cast SDK by upbeat_addict on Monday February 03, 2014 @06:57PM (#7174488)
I've also noticed recently that I can cast to my PS3 from the Chromecast icon in the YouTube app, so long as the PS3 YouTube app is running. I see it alongside my chromecast as an option. Presumably, the PS3 Netflix app behaves the same way.
Re:Chromecast now open to developers with the Google Cast SDK by eclipxe on Monday February 03, 2014 @07:28PM (#7174635)
Correct, thanks.
Re:Chromecast now open to developers with the Google Cast SDK by Kudos on Monday February 03, 2014 @06:06PM (#7174206)
> You can fullscreen cast.

Since when? Source?

Re:Chromecast now open to developers with the Google Cast SDK by UnoriginalGuy on Monday February 03, 2014 @06:31PM (#7174341)
Basically since the Chromecast was released.

The Chromecast came out on July 24, 2013, and several dozen articles note the feature before the end of July (26-28th). Just click the little down arrow on the Chromecast button (part of the Chromecast extension) then "Cast entire screen (experimental)."

July 26th, 2013: http://www.droid-life.com/2013/07/26/tip-chromecast-can-cast...

July 26th, 2013: http://www.androidauthority.com/chromecast-share-entire-desk...

July 27th, 2013: http://forum.xda-developers.com/showthread.php?t=2380302

July 26th, 2013: http://www.reddit.com/r/Android/comments/1j3sd1/chromecast_c...

Re:Chromecast now open to developers with the Google Cast SDK by Kudos on Monday February 03, 2014 @07:05PM (#7174524)
Oh my god, I can't believe I missed that...
Re:Chromecast now open to developers with the Google Cast SDK by officialjunk on Tuesday February 04, 2014 @03:07AM (#7176117)
Does this mean I can stream any app and my desktop or just a full screen chrome window?
Re:Chromecast now open to developers with the Google Cast SDK by pawelkomarnicki on Tuesday February 04, 2014 @07:10AM (#7176901)
Unfortunately (at least for me) it seems like it doesn't work via LAN, but somehow uses Internet connection to stream to somewhere and then back, kinda sucks and slow
Re:Chromecast now open to developers with the Google Cast SDK by dmdavis on Tuesday February 04, 2014 @10:07AM (#7177824)
Full screen streaming works beautifully for me, it's how my wife and I watch Amazon Prime movies. It's just like watching TV. I've read that the computer needs to encode the video it's streaming to the chromecast, so if your computer is slow, the streaming will be slow. That may be why you were getting poor results.
Re:Chromecast now open to developers with the Google Cast SDK by coda_ on Tuesday February 04, 2014 @10:57AM (#7178204)
You can stream any app and your desktop, yes.
Re:Chromecast now open to developers with the Google Cast SDK by isomorphic on Monday February 03, 2014 @02:17PM (#7172802)
Out of curiosity, what have you been using your Chromecast for?

I have drunk the Apple Kool-Aid: I have iOS devices, AppleTVs, and a home server running iTunes. Admittedly, the iTunes server is serving video and music that is ripped from legitimately-acquired spinning-discs, so perhaps I haven't tasted the iTunes Store Kool-Aid.

I purchased a Chromecast right at launch. As far as I could tell, the only things it did well was Netflix and stream YouTube. However, for my purposes, the AppleTV was better at both, so I literally put the Chromecast in a drawer.

When someone announced a jailbreak for it, I took it out of the drawer, rooted it, fiddled with it some more, then put it back in the drawer when I realized I was just wasting my time.

I'm not trolling, here; I really want to know how you use it. Is it that is works better with Android devices? Is it providing a better, open, AirPlay alternative? I just don't understand how it is in any way more useful than existing STBs--if not the AppleTV then, e.g., a Roku.

Re:Chromecast now open to developers with the Google Cast SDK by Touche on Monday February 03, 2014 @02:26PM (#7172877)
Yes, the fact that Apple TV doesn't work with non-Apple devices makes it a non-starter among those who don't exclusively buy Apple products in perpetuity.

So the question is Chromecast vs. other cross-platform TV solutions, like Roku. Roku does have it's own device-streaming but it only works with media on your device. I own both and use both, but lean towards the Roku more often as using the phone/tablet as a remote isn't significantly better than just using a remote, and I don't have to worry about what happens when the phone dies, or if I have it on a charger having to get up and walk to it when I need to pause the program.

Re:Chromecast now open to developers with the Google Cast SDK by IgorPartola on Monday February 03, 2014 @03:08PM (#7173118)
I have three Roku-powered rooms in my house. I read about Chromecast's capabilities but I cannot find how it would serve me better than Roku. My needs are:

* Stream Netflix/Hulu/Amazon/HBO Go to the TV.

* Stream videos off my NAS, such as DVD rips, home movies, etc. (For this I use Plex.)

* Occasionally, stream movies and pictures I took with my phone to the TV.

* Very occasionally, stream live events, such as the New Years ball drop, or the World Cup.

* Have an interface that is easy enough to use by non-technical people.

Chromecast, at least on paper, seems to do these things markedly worse. I appreciate it's simplicity and I'd probably get one to play around with if I did not have the Roku players already, but so far, it seems like the shabbier streamer. A Roku 2 or a refurb Roku 3 is about twice the price of Chromecast, yet seems to deliver much more value and much less headache. So my question is the same as above: why use Chromecast at all?

Re:Chromecast now open to developers with the Google Cast SDK by 67726e on Monday February 03, 2014 @03:17PM (#7173182)
I've got three Roku boxes in my house as well and I have to agree with all of your points. I got a Chromecast as a gift at Christmas and played with it but I really just don't see it as being better than the Roku with the exception of two fronts:

1. Price. It's just cheaper. About 40% the price of the latest Roku.

2. Development. Maybe this is a personal one for me. I keep wanting to work on a Roku Channel (app) but I really don't want to take the time to figure out their proprietary language.

Re:Chromecast now open to developers with the Google Cast SDK by robflynn on Monday February 03, 2014 @06:10PM (#7174221)
For what it's worth, BrightScript is pretty much just Visual Basic. It did take me a bit to get used to their various 'screens' and events.
Re:Chromecast now open to developers with the Google Cast SDK by virtue3 on Monday February 03, 2014 @06:32PM (#7174355)
also a brightscript/roku dev here. There's a nice code color plugin for sublime you can use and it's a bearable platform to develop on. Definitely use the console to just send the debug build up to the device and start debugging. It's really not that bad. Probably took me about a day to get used to it.

Honestly, as long as you stick within their control schemes you're fine. Trying to break out of the roku app controls leads to a total nightmare so be weary of that trap ;)

Re:Chromecast now open to developers with the Google Cast SDK by kbenson on Tuesday February 04, 2014 @12:42AM (#7175723)
I don't know how it is on the newer versions, but BrightScript was always very, very slow. Much slower than you would expect. Most of the time it never matters, since you are calling out to compiled object code that exports APIs for complex tasks, but when it matters, it matters. For example, implementing CRC32 (no built-in shift operators!), or minmax for game AI (for Reversi of all things, it's not like there's that many possible moves) always required heavy optimization to achieve performance that was near acceptable.

It always boggled my mind why they didn't just take a JS implementation and port it, but I guess it's hard to justify throwing away IP which already exists because of a prior product.

The engineers at Roku and the community were always great though.

Re:Chromecast now open to developers with the Google Cast SDK by virtue3 on Friday February 14, 2014 @09:10PM (#7242336)
There's a certain point of "good engineer's" career where they want to make their own language/vm. I'm 99% sure this is what happened here. It's always a train wreck.

They really should have used lua. It would have been very simple to put in and it's robust enough and efficient for small memory devices.

While I appreciate the power/flexibility/efficiency of js it is no where near as efficient as lua. Lua keeps things as ints until they aren't needed etc. Very much build for embedded systems almost. I'm probably biased in that I've worked on a lua VM for mobile handsets for a few years.

Re:Chromecast now open to developers with the Google Cast SDK by jggonz on Monday February 03, 2014 @03:23PM (#7173213)
I own a Roku, and find it works great when you're laying down on your bed and want to watch a movie on Amazon/Netflix. However, for entertaining, the easy access to Google Play Music and the ability to cast Chrome tabs was the reason that I chose Chromecasts everywhere, and stuck with the Roku just where I want to watch Amazon movies.
Re:Chromecast now open to developers with the Google Cast SDK by IgorPartola on Monday February 03, 2014 @03:26PM (#7173233)
I haven't tried it before but it seems the Roku app on iOS lets you stream music to the Roku player. In addition to that, many new home surround sound systems come with Bluetooth streaming capability, though then of course you have to keep the phone close enough to the stereo to not break the connection.
Re:Chromecast now open to developers with the Google Cast SDK by Touche on Monday February 03, 2014 @03:27PM (#7173239)
The difference I see is that remote-based streamers are better when you know what you want to watch. Push-from-device based streamers are better when you are just browsing and come across something interesting.
Re:Chromecast now open to developers with the Google Cast SDK by higherpurpose on Monday February 03, 2014 @04:47PM (#7173738)
I don't think it's for someone who already has 3 Rokus...
Re:Chromecast now open to developers with the Google Cast SDK by giovannibajo1 on Monday February 03, 2014 @04:25PM (#7173600)
> Yes, the fact that Apple TV doesn't work with non-Apple devices makes it a non-starter among those who don't exclusively buy Apple products in perpetuity.

That's factually false. I daily use an Apple TV with my Synology NAS, for instance. There are AirPlay streamers for Android and for Windows. The protocol has been fully reversed (besides the DRM bits).

Now, I'm not saying that this was the design of the protocol. Obviously Apple doesn't care less about 3rd-party compatibility. I'm just saying that it's false that Apple TV nowadays is limited to the Apple ecosystem.

Re:Chromecast now open to developers with the Google Cast SDK by Touche on Monday February 03, 2014 @04:28PM (#7173616)
Great, but none of the apps that people care about like Netflix, Hulu, HBO Go, Plex, etc. are using a reversed-engineered Airplay on Android.
Re:Chromecast now open to developers with the Google Cast SDK by stock_toaster on Monday February 03, 2014 @07:54PM (#7174731)
However, the first 3 you mentioned are already native "apps" on appletv.
Re:Chromecast now open to developers with the Google Cast SDK by blinkingled on Monday February 03, 2014 @03:34PM (#7173270)
One yet unrealized advantage of ChromeCast over AppleTV is that it has an open API available which developers can use to extend it to do more creative things. And the client support isn't limited to Apple only device - web, Android, iOS, desktop everything is supported as a client.

Besides it's only $35 and it works well.

Re:Chromecast now open to developers with the Google Cast SDK by jggonz on Monday February 03, 2014 @03:18PM (#7173185)
This is what I do with my Chromcasts:

1. Stream Netflix movies for myself and my child. My son can control Netflix easily with my Nexus 4 smart phone once I get the Chomcast connected.

2. Stream music from Google Play music. I pay $7.99 per month and can use my phone in my living room chromecast, my bedroom chromecast and my bluetooth enabled radios in the cars. Everywhere I go, my music can come with me.

3. I use it to cast Chrome tabs from my Macbook whenever I want to share pictures with families or show something interesting I've been working on to friends.

4. Whenever Netflix doesn't have a movie, I can sometimes find something on Google Play Movie.

I also own a Roku mainly because I find Amazon's movie selection to be vastly superior to what Netflix has to offer. I can usually find anything I want to watch on Amazon vs Netflix and Google Play Movies.

One feature I need/want from the Chromecast is the ability to view my phone's screen just like Miracast. I'm assuming they're still working on improving the reliability.

In order to properly stream content to the Chromecast, I had to upgrade my router to something that supported HD video streaming.

Re:Chromecast now open to developers with the Google Cast SDK by curveship on Monday February 03, 2014 @03:14PM (#7173158)
Netflix, HBO GO and Google Play Music. That's almost all I watch/listen to anyway, the two exceptions being Amazon Prime video and Spotify music, neither of which are supported yet on the Chromecast.

I bought when it still came with 3 months of Netflix credits, making the effective cost around $10. It's well worth that to me just to be able to control the music while I'm sitting at the dinner table. For video, it's not as clear a gain. It's nicer to browser Netflix and HBO on my phone than on the (clunky) "Smart TV" apps of my TV, but I rarely watch video alone, and browsing on the TV means everyone can discuss the options, while browsing on my phone means only I am seeing them.

Re:Chromecast now open to developers with the Google Cast SDK by wahsd on Monday February 03, 2014 @03:19PM (#7173191)
I played with Chromecast for about a couple weeks and just yesterday remembered I had totally forgotten about it. It's a typical Google product, released just after leaving Alpha state, marginally decent, of limited and disjointed utility, and generally poorly executed. Judging based on Google's history with, literally every single thing they have done, we are approaching peak internal support and attention with declining marginal focus and development. I expect Chromecast to languish and atrophy within this year.

...

"Hey, anyone want to watch a movie together? ... Ok, you guys just sit there in silent and awkward anticipation while you look at me flipping through various apps on my personal device." Google —— Please, someone explain what this "social" thing means

Re:Chromecast now open to developers with the Google Cast SDK by cdash on Monday February 03, 2014 @10:48PM (#7175379)
"Hey, anyone want to watch a movie together?"

Everyone pulls out their phones to flip through Netflix to make suggestions. You all agree on a movie and then someone hits play. Done.

What are you even talking about "social".

Re:Chromecast now open to developers with the Google Cast SDK by wahsd on Thursday February 06, 2014 @11:42AM (#7191234)
I mean social, as in pre-Facebook social, you know, >1 person interacting and engaging with each other, their environment, and sharing an experience in the real world, e.g., looking at the same screen, seeing the same thing, implicitly sharing their mutual interests through queues like "click on the details for {movie title}, I would like to see what it's about". I know it's confusing that I didn't mention pushing each movement and thought to Twitter and Facebook and Tumblr, but there used to be a time when social meant a singular level interaction between humans within physical proximity to each other.

Your rebuttal does nothing to improve my original point. You and all those around you are digging in their phones doing things unseen by everyone else, and also maybe even excluding those who do not have a device, or even just haven't downloaded that specific app.

I have a perfect solution to bridge that gap. But that's for another time.

Re:Chromecast now open to developers with the Google Cast SDK by dclara on Monday February 03, 2014 @05:01PM (#7173817)
Funny scenario, but I can imagine. This is also my concern along with the rest of the things. Can we anticipate that we have so many apps installed on our phone and keep looking for the one we need to control every time? Especially, we'll buy every "thing" with an Android or ChromeOS or iOS on it for a price more than $100?
Re:Chromecast now open to developers with the Google Cast SDK by jsloat on Monday February 03, 2014 @09:15PM (#7175058)
> Can we anticipate that we have so many apps installed on our phone and keep looking for the one we need to control every time?

Total tangent, but I've come to depend on the Android app Conjure[1], which acts kind of like Mac's Spotlight search for apps. You can type in a full app name, or show all apps that contain the letters you type in in that order, even if you skip letters (e.g. searching for "cre" would bring up ChRomE").

[1] https://play.google.com/store/apps/details?id=com.iojess.con...

Re:Chromecast now open to developers with the Google Cast SDK by skelsey on Monday February 03, 2014 @02:25PM (#7172868)
Your friends with Android phones can't cast to Airplay, but they can cast to Chromecast.
Re:Chromecast now open to developers with the Google Cast SDK by isomorphic on Monday February 03, 2014 @02:52PM (#7173004)
By "cast," you mean "tell the Chromecast to fetch/display content", rather than "show streaming video of my device's screen"?

This is part of what I'm asking: I don't get the usage model. I prefer using the STB directly with a remote (and no other client device), or pushing the client device's screen to the STB. If you're saying that you use "tabcasting" (which I guess is remotely-directed Chromecast web surfing), then fine. It's not something I'd ever use, but I understand that the equivalent doesn't exist on other STBs.

Please don't get me wrong: I would prefer if there were an open AirPlay equivalent that Android and iOS devices supported at the OS level. But I don't think that's what you're talking about.

Re:Chromecast now open to developers with the Google Cast SDK by ajross on Monday February 03, 2014 @03:42PM (#7173322)
> I prefer using the STB directly with a remote

The idea is that your phone (or tablet or laptop or whatever) becomes your remote. If you want to watch something on Netflix you pull the phone out of your pocket, launch your Netflix app, and then hit the Chromecast button to send the output to the TV. It's not a separate UI, just a separate destination for the video content you've already selected. For me, the simple fact of never having to hunt for a remote is enough to justify the $35.

On a technical level: what the chromecast is doing is simply streaming content from local devices on the Wifi LAN. It has no UI of its own and won't fetch content by itself. The codec suite is limited when compared to Android: it supports H.264 baseline, VP8, MP3 and AAC. And I believe the container must be either MP4 or WebM.

Re:Chromecast now open to developers with the Google Cast SDK by bane on Monday February 03, 2014 @03:36PM (#7173284)
No, you can also stream to the chromecast. e.g. Google's "cast tab". I use it to watch stuff off my plex server or hulu (don't have a hulu plus account).
Re:Chromecast now open to developers with the Google Cast SDK by untog on Monday February 03, 2014 @02:43PM (#7172952)
Cast what though, beyond YouTube and Netflix?
Re:Chromecast now open to developers with the Google Cast SDK by spankalee on Monday February 03, 2014 @02:51PM (#7172999)
Play Music & Movies, Pandora, Hulu, Chrome tabs, HBO Go, Plex...

See http://chromecast.com/apps for the current list.

I really only use Google Play, Netflix, YouTube and tab casting though.

Re:Chromecast now open to developers with the Google Cast SDK by untog on Monday February 03, 2014 @03:12PM (#7173146)
I know what's available- I have one myself, I just don't ever use it. I don't have a Hulu Plus subscription, nor do I buy music/video through the Play Store. Chrome tab performance is weak at best.

I guess I'm just hoping for a lot more than what I have right now.

Re:Chromecast now open to developers with the Google Cast SDK by spankalee on Monday February 03, 2014 @06:21PM (#7174285)
That's the reason to be excited about the SDK release, but honestly, regardless of the number of apps even available, I just don't use that many services that I want to stream to my TV. The current crop does pretty well. I would like to see the ability to throw a Flash object to the screen so I can play any embedded video, and I hope to see interesting games and ambient apps, but that's about the extent I can think of.
Re:Chromecast now open to developers with the Google Cast SDK by jggonz on Monday February 03, 2014 @03:26PM (#7173230)
Chrome tab performance may be weak due to a slow router. I bought a newer Asus and it helped quite a lot. I can play youtube videos within a Chrome tab and it works perfectly well, even with the router several bedrooms away.
Re:Chromecast now open to developers with the Google Cast SDK by sethhochberg on Monday February 03, 2014 @02:54PM (#7173023)
With the opening of the SDK, presumably anything - even so far in the comments on this HN posting there are already few individuals who are happy their local media streaming servers can be published, and it wouldn't be too hard to imagine that VLC plugins or something similar are too far behind.
Re:Chromecast now open to developers with the Google Cast SDK by bitskits on Monday February 03, 2014 @02:52PM (#7173011)
HBO Go and Plex are two apps I am using very frequently with my Chromecast... That gets me both external and locally stored content without a dedicated HTPC to play the media.
Re:Chromecast now open to developers with the Google Cast SDK by menriquez on Monday February 03, 2014 @04:18PM (#7173558)
Plex has been a pleasant surprise to me...im wondering how the release of this api is going to improve the usability of it
Re:Chromecast now open to developers with the Google Cast SDK by aggronn on Monday February 03, 2014 @03:04PM (#7173091)
If you stream sports, chromecast is a godsend if you don't want to hook up your computer to the TV.
Re:Chromecast now open to developers with the Google Cast SDK by hershel on Monday February 03, 2014 @04:16PM (#7173546)
Are there places to stream sports with reasonable amount of content without being tied to a cable company ?

And does it increase cord cutting ?

Re:Chromecast now open to developers with the Google Cast SDK by aggronn on Monday February 03, 2014 @04:27PM (#7173613)
legally and in high quality? not really. I wouldn't throw a superbowl party without tv access, but if you want to watch your favorite team when you otherwise can't, its definitely possible.
Re:Chromecast now open to developers with the Google Cast SDK by Touche on Monday February 03, 2014 @04:31PM (#7173636)
search.twitter.com

Team Name stream

Re:Chromecast now open to developers with the Google Cast SDK by fernandotakai on Monday February 03, 2014 @02:56PM (#7173042)
i use plex and netflix extensively and i use more youtube than i thought.
Re:Chromecast now open to developers with the Google Cast SDK by jsight on Monday February 03, 2014 @02:27PM (#7172881)
My usage falls into three categories:

- Netflix (a lot) - Tab Casting (occasionally) - Youtube (very seldom)

I suspect that AppleTV would work better for everything except for the tab casting for me. Even with the current limitations, I don't know of another settop box that does that as effectively as the Chromecast.

Having said that, I have still been mostly disappointed with the device so far, as tab-casting has been basically the only free solution to local streaming so far. I am optimistic that this will change soon if the SDK is really open, though.

Re:Chromecast now open to developers with the Google Cast SDK by jsloat on Monday February 03, 2014 @09:19PM (#7175073)
Screen mirroring on Apple TV works well, assuming, of course, that you're on a Mac and the OS lines up.
Re:Chromecast now open to developers with the Google Cast SDK by saltysugar on Tuesday February 04, 2014 @03:41AM (#7176208)
That's a very expensive assumption for most people
Re:Chromecast now open to developers with the Google Cast SDK by jsloat on Friday February 07, 2014 @11:11AM (#7196912)
Poll's a little old, but most HN readers use OSX: https://news.ycombinator.com/item?id=3786674
Re:Chromecast now open to developers with the Google Cast SDK by kllrnohj on Monday February 03, 2014 @04:51PM (#7173758)
Chromecast has the really nice advantage of the fact that when friends or family visit they can cast THEIR content to your TV without needing to sign in to your STB.
Re:Chromecast now open to developers with the Google Cast SDK by __david__ on Monday February 03, 2014 @06:13PM (#7174236)
How is that an advantage over the Apple ecosystem? When I visit my parents I can stream random stuff to their Apple TV or their Airport Expresses without doing anything besides getting on the WiFi network.
Re:Chromecast now open to developers with the Google Cast SDK by mdwrigh2 on Tuesday February 04, 2014 @01:04AM (#7175786)
Friends or family don't need to have bought into the Apple ecosystem.
Re:Chromecast now open to developers with the Google Cast SDK by __david__ on Wednesday February 05, 2014 @02:03AM (#7182338)
Ok, but they need to have bought into the Google ecosystem. I can't stream from my favorite music app to a Chromecast...

That's not really an advantage.

Re:Chromecast now open to developers with the Google Cast SDK by kllrnohj on Wednesday February 05, 2014 @05:23PM (#7187262)
Uh, no, that's not true at all. Chromecast works with Netflix, Pandora, etc... None of which are part of the "Google ecosystem". And you can cast from just about every device.
Re:Chromecast now open to developers with the Google Cast SDK by bane on Monday February 03, 2014 @03:39PM (#7173301)
Casting youtube to my TV, slides for presentations, casting tabs from my browser to watch various streaming video services.

It's not fancy, but it's unbelievably cheap and just works.

The model of using your phone as your impromptu remote is awesome. I can't wait to see what apps support it in the future.

Re:Chromecast now open to developers with the Google Cast SDK by thefreeman on Monday February 03, 2014 @03:09PM (#7173130)
After the previous update I use mine to cast media from my PC to TV through Real Player Cloud. The app is crap though and files need to be n mp4 format. I am glad they finally opened p the SDK so I can make something more tailored for my needs.
Re:Chromecast now open to developers with the Google Cast SDK by mmanfrin on Monday February 03, 2014 @01:56PM (#7172685)

    Apple is the only large digital content provider which wants to force us to buy their proprietary device ("Apple TV") to watch their proprietary content. It really does decrease the value for Apple's content. In fact I'm just not going to buy Apple's DRM-ed video anymore, as I have to plug in a HDMI cable to watch it on my TV.
People said that about iTunes, no?
Re:Chromecast now open to developers with the Google Cast SDK by untog on Monday February 03, 2014 @01:58PM (#7172700)
I'd argue that the long term future of iTunes isn't fantastic. Individual music companies (Spotify, Rdio) are providing better experiences than Apple can.
Re:Chromecast now open to developers with the Google Cast SDK by __david__ on Monday February 03, 2014 @06:23PM (#7174298)
Really? I don't like spotify compared to iTunes. I can't imagine locking myself into a service for the rest of my life in order to hear music. Once I buy it from iTunes, it's mine to use as I please, it's not locked up in some stupid custom DRM-laden app (which is fairly ironic).
Re:Chromecast now open to developers with the Google Cast SDK by untog on Monday February 03, 2014 @10:28PM (#7175326)
I can't imagine locking myself into a service for the rest of my life in order to hear music.

But Spotify doesn't lock you into anything.

Re:Chromecast now open to developers with the Google Cast SDK by __david__ on Tuesday February 04, 2014 @06:18PM (#7180906)
If I don't pay the monthly fee then I can't listen to albums on my phone. That's pretty much the definition of lock-in.
Re:Chromecast now open to developers with the Google Cast SDK by saltysugar on Tuesday February 04, 2014 @03:43AM (#7176220)
iTunes videos are DRM-ed
Re:Chromecast now open to developers with the Google Cast SDK by __david__ on Tuesday February 04, 2014 @06:17PM (#7180902)
Yes, we're discussing music not video.
Re:Chromecast now open to developers with the Google Cast SDK by lnanek2 on Tuesday February 04, 2014 @11:42AM (#7178509)
I've had the entirely opposite experience here. Miracast just works for me. I have the Netgear receiver and I've used it with several different phones - Samsung, HTC, and LG. In fact, I know your chart is wrong because my LG Nexus 4 works fine with it.

Meanwhile Chromecast is a joke. It doesn't work at work because our employee network requires a username and password and our guest network requires a click through agreement. It doesn't work at the hotels I stay at because again, they have a click through agreement. It works about half the time on personal WiFI APs where the person wasn't security conscience enough to turn on client isolation. The thing is nearly useless for me.

Miracast uses WiFi Direct so works trouble free and lag free. Chromecast is some bizarre crappy second computer that has to connect to the network, but has very little capability to actually connect in the real world.

Re:Chromecast now open to developers with the Google Cast SDK by xur17 on Monday February 03, 2014 @01:36PM (#7172552)
I also use mine extensively. The interface for Netflix alone makes it worth it, even if you already have another device that works with netflix. I'm really excited to see what new apps, etc come out, now that my biggest complaint has been solved (no public api).
Re:Chromecast now open to developers with the Google Cast SDK by sciurus on Monday February 03, 2014 @04:47PM (#7173741)
So you're saying that the chromecast (created by google) works well with android (created by google) and chrome (created by google)? And you love this, because it's so much better than Miracast where Samsung only works with Samsung, Sony only works with Sony, etc?

I agree it's a shame that a standard like Miracast has incompatible implementations. However, creating another protocol just makes that situation even worse.

Re:Chromecast now open to developers with the Google Cast SDK by Johnie on Monday February 03, 2014 @04:51PM (#7173757)
Netflix on iOS works well with the Chromecast.
Re:Chromecast now open to developers with the Google Cast SDK by avtar on Monday February 03, 2014 @06:30PM (#7174338)
I wish I could be in this club. Instead Netflix/Chromecast will complain, more often than not, about not being able to stream content. The only workaround seems to be to perform a factory reset and even that is temporary.

https://groups.google.com/forum/#!msg/chromebook-central/oYV...

http://www.ibtimes.com/chromecast-update-refreshes-google-do...

Re:Chromecast now open to developers with the Google Cast SDK by oaktowner on Monday February 03, 2014 @05:18PM (#7173919)
Johnle - Indeed. It works better with Chromecast than Netflix on Android in my experience!
Re:Chromecast now open to developers with the Google Cast SDK by ChuckMcM on Tuesday February 04, 2014 @12:05AM (#7175621)
I'm trying to figure out why my Chromecast's video sucks so badly. On my 1080p HDMI TV the pictures it uses look great but if I try to cast something to it, it looks like badly scaled crap. I selected "hyper high res" mode or what ever they called it which helped but many it still looks pretty crappy.
Re:Chromecast now open to developers with the Google Cast SDK by talonstriker on Monday February 03, 2014 @06:46PM (#7174420)
It's a lot easier for things to "just work" when one company controls the entire stack.

That being said, as others have pointed out, ChromeCast and Miracast solve different problems. One is something more of a Wireless DLNA solution while the other is real-time streaming.