The obvious question: Why would you buy this if you already had an Apple TV (or were considering buying one)?
* Cross-platform support, not just iDevices
* For apps that integrate with the SDK (currently Youtube & Netflix, but I am sure more will be coming soon), the processing of the content can be transferred to the the Chromecast. Hence, once you "flick" your Netflix content to Chromecast, your phone is free and not processing content anymore unlike Airplay, which is a huge win for your phone's battery.
* All your phones/tablets/computers become your remote/controllers.
* The price (at $35, it's a relatively low-risk impulse buy)
* UPDATE: It automatically switches to the HDMI input channel when streamed, atleast on my LG TV. My 3rd gen Apple TV doesn't so I have to find the TV remote to switch HDMI inputs, which can sometimes be annoying.
For apps that integrate with the SDK (currently Youtube & Netflix, but I am sure more will be coming soon), the processing of the content can be transferred to the the Chromekey. Hence, once you "flick" your Netflix content to Chromekey, your phone is free and not processing content anymore unlike Airplay, which is a huge win for your phone's battery.
If that's the case, I wonder why Chromebooks (other than the Pixel) aren't compatible.
Close. It's hardware encode acceleration. The Ivy Bridge CPU in the Pixel has it, the earlier Chromebooks don't (I don't know if that's true universally; I didn't check).
It only requires CPU usage when it's streaming the contents of your screen. For Youtube/Netflix, all it does is tell the key the url of the stream and everything is done either on the key or the server.
I don't believe that's correct -- from what I can tell, when it's streaming webpages, it is actually only synchronizing two copies of Chrome -- one on the stick, one on your PC. It is not encoding/transmitting a video, as with AirPlay or Miracast.
From what do you discern that? Given that everything they showed about the the product was variations of it receiving and decoding a video stream, it would be quite a switch for it to also have a full platform running a web browser in synchronicity. It seems much more likely that it is a direct video send, making it enormously simpler to design.
> The receiver device runs a scaled-down Chrome browser with a receiver application that receives data over Internet Protocol and transmits it to the television via HDMI.
Very cool, though incredibly surprising (a browser is an intensive, complex thing, so will people have to constantly be patching their Chromestick?), especially given that once you add the cost of synchronizing all interactions, it seems so much easier to simply video grab the tab.
If anyone has this device, what is CPU usage on the source like when tab-casting?
I don't know, maybe because it needs a browser extension which older ones don't support at the moment. I would assume they'll support them later, but honestly, I don't know.
That sounds smart to me, but for Netflix at least, generally everyone would use the Netflix app on the Apple TV (which is solid) rather than airplay from their device. YouTube is another story, though, it's a disaster on the Apple TV and I'll almost always stream from my phone. Of course, if I'm streaming to my Apple TV I'm by definition at home with a charger nearby, so this isn't a key differentiator.
But that brings up what I think is the most interesting use case – portability: put it in your bag and forget it until you need to present/watch something for work/at a friends house.
With many TVs with built in youtube support and many other devices already connected to the TVs that have you tube, xbox, PCs, PS4, Wii, Roku, etc. Why would you buy it? Just so that I don't have to search what I am watching on my phone on my TV again? For the price this might still be worth enough to spend for that feature. But just trying to understand if there is anything else there is to it.
The scenario that Google presented was users doing stuff on their phones/tablets and then saying to themselves, "Hey, let's play this on the big TV screen." That's a different use case to Google TV/Xbox/PS4 etc.
They made a lot of the fact that, with Chromecast, your phone/tablet works as a TV remote.
Also, people who are already familiar with their phones/tablets don't have to learn a new UI etc.
And it doesn't have to deliver a lot of value to justify $35....
> generally everyone would use the Netflix app on the Apple TV (which is solid) rather than airplay from their device
Only people that have Apple TVs. Apple has sold a lot of them, but it's a fairly niche device that costs 3x what this one does. They also work differently so that you're not streaming from your device to the Chromecast dongle, but that you're essentially just telling it what to play (you can then use your device as normal). This is pretty neat, I for one would use it just so I would not have to deal with the terrible Apple TV remote control anymore. Typing in anything is a frustrating experience, I'd rather type from my phone or computer and then have it play where I'd like (my TV).
Yes, but the comment I was responding to was specifically about the Chromecast vs Apple TV - while we use ours a lot, it certainly has a far from perfect interface. I certainly wouldn't recommend it to anyone who wasn't on the Apple ecosystem already, and would be using the Remote app on their phone/iPad to type search queries rather than up up down down left right left righting for minutes at a time.
HDMI has a feature called CEC which can control inputs, volume, channels, basically everything a normal remote can, but over the existing cable and connection. https://en.wikipedia.org/wiki/HDMI#CEC
My Toshiba TV and my Onkyo receiver both support it. It's not a cost/licensing issue since it's built into HDMI and Pulse-Eight makes a USB CEC HDMI passthrough adapter and provides a libCEC library: http://www.pulse-eight.com/store/products/104-usb-hdmi-cec-a...
PS3 supports it. Although not when the youtube app is running for some reason. When I turn my TV on, the PS3 starts automatically and I can use the remote to navigate menus and Netflix.
It's worth noting that each consumer electronic manufacturer has its own name for CEC, rather than using the generic term. This, despite good compatibility between manufacturers' implementations.
From the Wikipedia page linked by the parent:
Trade names for CEC are Anynet+ (Samsung), Aquos Link (Sharp), BRAVIA Link and BRAVIA Sync (Sony), HDMI-CEC (Hitachi), E-link (AOC), Kuro Link (Pioneer), CE-Link and Regza Link (Toshiba), RIHD (Remote Interactive over HDMI) (Onkyo), RuncoLink (Runco International), SimpLink (LG), T-Link (ITT), HDAVI Control, EZ-Sync, VIERA Link (Panasonic), EasyLink (Philips), and NetCommand for HDMI (Mitsubishi).
Seems exactly like the evolution of the Nexus Q. It interfaces the exact same way with the Youtube/Play Movies apps, minus the need for a special app to set it up.
IIRC, the early beta version AirPlay displayed a mirror button for every <video> tag in MobileSafari. Apple got a lot of pushback from content providers, and had to make AirPlay an opt-in for content providers [1] (though with iOS 5 they later changed it to an opt-out feature).
Not sure how the content providers will respond this time.
If you use 3rd party plugins (I use ClickToPlugin in Safari) you can get that option back for HTML5 video. You can also use display mirroring or window mirroring for flash stuff (part of Mountain Lion for recent Macs, older Macs can use AirParrot).
I just added the "Google Cast" extension on both my mac and Linux Chrome installs and it appears to work on both(as far as I can determine them to work without actually having a chromecast yet, anyway.)
Haven't tried it, but with the Chromecast extension, it presumably should. The only potential problem I see is if there are any licensing issues with video codecs.
It wouldn't be killer. A very small subset of users would want it. Any time I've seen browsers on TV's trying to read the text from a couch has been difficult, interfacing with it's difficult, and like most people I'm sure I don't like browsing in full view of everyone. e.g. type in a password and everyone can see it. If this had a full browser I seriously doubt that could release it this cheap and I think anything over $50 and it wouldn't sell.
No reason it wouldn't work on a projector right? I was going to use a Raspberry Pi to do the same thing, but this is much simpler. Do you know when is it coming to Canada? I'd prefer not to go through the hassle of getting a reshipper to mail it to me.
They said other markets would be coming as soon as they can. Not sure what that means but for the Nexus 7 launch Canada is only a few weeks behind the US. With the Chromecast they probably have now idea how demand will be and once they know they can fulfil it will open up to Canada and others.
for the Nexus 7 launch Canada is only a few weeks behind the US
"Only"? In comparison, Apple ships to a large number of nations simultaneously. I got my iPad shipped (from China, which is also where those Nexus 7s are coming from) the same day that US buyers got theirs shipped.
Such is how international companies usually operate.
I like Google the company, but they are incredibly provincial and out of step when it comes to these things. If they lack manpower to do international releases, perhaps they should hire the appropriate people instead of constantly treating the rest of the world as an afterthought.
Apple has delayed shipping to other countries many times. e.g. I got the first iPad the day it became available in the UK (I pre-ordered). That was about 6 weeks after the US launch. As far as I recall it was actually two weeks later than they originally scheduled for the UK launch.
Demand for these products is very high and producing them in large quantities while trying to keep them a surprise is difficult. If Apple, a company that is a hardware business has trouble with this it's hardly surprising Google a web software and advertising company would have problems.
Google doesn't make or design the Nexus 7, but rather Asus does (or at least Asus is the brand behind it, though they likely offload actual manufacturing to Foxconn or similes). Nor does Google manufacture, warehouse, or ship these products (which one experiences when they try to do any sort of service requests on Nexus devices, to instead be direct to HTC or Samsung or Asus).
Google constantly and egregiously fails to see a world beyond the US as being important to their initiatives. It took a ridiculously long time for customers outside of the US to buy apps on the Android Market (it remains seriously limited), and was significantly worse for those who want to sell on the market. With each of these hardware releases, it's the US and then, maybe some day, the rest of the world. That's Google's prerogative, and they're based on the US, but every time they do that they incrementally offend the rest of the world.
Well that only adds androids devices to the list, Windows phones are out right now.
> "* For apps that integrate with the SDK (currently Youtube & Netflix, but I am sure more will be coming soon), the processing of the content can be transferred to the the Chromecast. Hence, once you "flick" your Netflix content to Chromecast, your phone is free and not processing content anymore unlike Airplay, which is a huge win for your phone's battery"
AppleTv does this by it owns, not need to stream Netflix from your devices.
> "* All your phones/tablets/computers become your remote/controllers."
Only if they are iDevices or android devices.
> "* The price (at $35, it's a relatively low-risk impulse buy)"
Only attractive I see, still if you already own an AppleTV, why should I buy this one too?
Chrome browser supports it. There's an SDK, so theoretically any device can support it.
I own both an AppleTV and a ChromeCast. For Netflix, I use both depending on whether my phone or the Apple TV remote was closer to me. For Youtube, no question, Chromecast is far better. Other content, I don't want to comment about since I am not sure what's released to the public yet.
I also strongly dislike that AppleTV has a fixed set of channels/apps and no SDK (though it's likely they will have one soon). I can't even remove the multiple channels that I never watch and don't care about.
Funny thing when people down-vote posts that criticize(?) Google and don't give a good reason why...
Exactly which part of what I said deserves to be downvoted? I don't care about the karma but it makes me wonder what are the things that are not acceptable in HN
It uses a mini/micro? USB (one of those small USB ports for power). My device came with an adapter that I could attach to my TV's USB port, so there are no dangling wires. If your TV doesn't have a USB port, you can just connect it to a normal power outlet (it's the same adapter as for many other Android devices)
How long does it take to boot? ie from power being applied through to it showing up as a target in other devices/apps.
(The reason for asking is whether you need to connect it to a full time powered port, or one that only comes on once the TV etc are on. If it takes 5 minutes before becoming visible that would be problematic but 5 seconds would be fine.)
* Cross-platform support, not just iDevices
* For apps that integrate with the SDK (currently Youtube & Netflix, but I am sure more will be coming soon), the processing of the content can be transferred to the the Chromecast. Hence, once you "flick" your Netflix content to Chromecast, your phone is free and not processing content anymore unlike Airplay, which is a huge win for your phone's battery.
* All your phones/tablets/computers become your remote/controllers.
* The price (at $35, it's a relatively low-risk impulse buy)
* UPDATE: It automatically switches to the HDMI input channel when streamed, atleast on my LG TV. My 3rd gen Apple TV doesn't so I have to find the TV remote to switch HDMI inputs, which can sometimes be annoying.