I'll explain my Chromecast experience simply: We are either using Chromecast in my house, or DirecTV.
When we want to watch Netflix, HBOGO, or something on Plex, we fire up a phone or tablet, open the app, and Cast it to the TV. The Chromecast automatically switches the input and begins playing what we asked it to.
@Loki540 - You might be referring to the still in development Chrome extension. We don't use that much but I hear it has to be on a very solid wireless connection. Chromecast-ready apps do not have that problem.
@yetfeo - It only costs 30 dollars, and any app can choose to be a 'Chromecast' app by adding in their API. Our iPads and Android devices all can use the Chromecast and the variety of things we can do with it is superior.
Just curious - what do you usually use Chromecast for? I got it specifically to stream Youtube on my TV, and found that there was usually a > 1 second lag between the image on the TV and the sound on the TV. This has given me a pretty negative view of Chromecast - basically that it's just good for streaming visual-only things like slideshows etc. Have you found this not to be the case?
I think you're missing the Chromecast button on the YouTube page. You shouldn't have to mirror the tab to fling YouTube to the TV.
Mostly I use it for Netflix, Google Play Movies & TV, and Plex.
Also if you have an Android or iPhone the native application on either device will have the Chromecast icon to fling the video. It's the same icon in Chrome (and maybe other browsers? I'm not sure) to fling from your computer.
Definitely not. Since Chromecast is sending audio and video over the same connection (HDMI), this is likely a problem with your TV or the like. Do you have a complicated Home Theater setup?
I disagree. As someone who owns a Chromecast, I think you're doing a _huge_ disservice to the AppleTV. The Chromecast isn't a standalone device. Period. Full stop. It's basically a mildly improved AirPlay device that still lacks many features (even in the way of AirPlay). Off the top of my head:
1. The streaming isn't system wide. Developers need to incorporate the streaming ability into their apps whereas Apple has it builtin to the device.
2. My parents are unable to understand the concept of "flinging" content; they want it to be a DVR-like device. The AppleTV allows them to rent, purchase, or view previously obtained iTunes content.
3. Music sounds terrible through it. It lacks an optical audio out port so it just uses the TVs speakers which are obviously not great.
4. This is probably a personal issue, but Chrome tab streaming constantly drops out after a short period of time. I've yet to get it working fully.
5. AppleTV can support games being flung to the TV while using the iDevice as a controller. This isn't a selling point, but I'd like my N5 to do the same.
6. My TV (while being a 40" 1080p flat screen) is lacking a USB port so I do have to plug it in.
7. Am I missing where I can stream my Android device's OS on the screen? I know iOS allows you to stream the entire device's OS so you can give presentations and the like.
There are many, many things the Chromecast can't do. It's saving grace is its price point which lessens peoples' expectations but I wouldn't start saying the AppleTV should aspire to be it.
I look at that as a feature. I already have applications I'm comfortable with for browsing and selecting media. I just want a new rectangle to play that media on.
The fact that anyone on my Wifi can access it with their phone, instantly, with nothing to install is a magical experience.
> 3. Music sounds terrible through it. It lacks an optical audio out port so it just uses the TVs speakers which are obviously not great.
HDMI Audio Return addresses that. If your TV and receiver support that (I think most do?), then audio will flow from the Chromecast into your TV and back up the TV's HDMI cable into the receiver.
My Chromecast plays audio through the speakers hooked up to my receiver just fine.
> Am I missing where I can stream my Android device's OS on the screen?
Maybe Chrome for Android supports that? I don't think there's OS level support for Chromecast.
> There are many, many things the Chromecast can't do.
Sure, a boat can't do many of the things an airplane can, and vice versa. They're different devices with very different user experiences.
> 3. Music sounds terrible through it. It lacks an optical audio out port so it just uses the TVs speakers which are obviously not great.
I have my TV's optical audio out running to my receiver. That way all my HDMI devices (laptops, Raspberry Pi, Chromecast) are hooked directly to my TV and the audio is automatically sent to my stereo system.
> 4. This is probably a personal issue, but Chrome tab streaming constantly drops out after a short period of time. I've yet to get it working fully
I've never experienced this problem.
For point 6, I prefer to plug in the Chromecast to a real 5V DC power source because the USB port on my TV is only powered when the TV is on, and I like that Chromecast can turn on the TV and switch the input itself.
One other point I'd add is that I hate using my phone (or tablet) as a remote for my TV.
I have an Apple TV, and being able to stream content via Air Play for my local TV network, YouTube, and VLC Streamer was nice at first. And then over the months I slowly stopped bothering with my phone and kept grabbing the Apple TV remote.
Interacting with a TV through a phone or tablet interface, no matter how simple, is just not as nice as looking directly at the screen and interacting.
I watch less shows now because of it — because there are more options only available on my phone. I just can't be bothered to use them.
Well it has different viewing options ("more open" for whatever that's worth). Based on Google's own promotions for Chromecast you gain Google Play and Pandora, and lose iTunes. There's a bunch of other tradeoffs I'm sure (I assume, for example, there's a PBS app for Chromecast just as there is for AppleTV. AppleTV supports Amazon video via AirPlay -- which is good but not great; but Amazon video simply won't play on Chromecast.)
Chromecast is more intelligently architected than AppleTV (you hand off to Chromecast rather than remote-controlling it) but I suspect AppleTV will address this shortly. OTOH AppleTV works with any remote, and you can use any iOS device as a remote, and AirPlay is wonderful.
It still needs power though so it needs to be plugged into something - whether USB or wall socket. What are the open viewing options? It seems to only provide youtube and google movies in countries that don't have netflix. Does it support streaming a local video from a phone or PC?
HDMI (v1.4) alone is capable of providing power to the Chromecast, pin 18 is specced for +5V/50ma.
Not every TV/monitor supports this since there aren't that many devices out in the field that utilize HDMI power, but if your TV does provide power over the HDMI port then the Chromecast can get everything it needs just from the HDMI port.
Using your Chromecast this way puts you at a disadvantage with many TVs. My TV only provides HDMI power when the input is selected (this may be per the spec) but that eliminates Chromecast's 'switch the input automatically' feature.
In the (European) country that I live in, you can actually buy an Apple TV. Whereas Chromecast simply does not exist.
One can argue all day about how awesome Chromecast is, but if you can't buy it, well, it isn't really competitive. And this has happened with a lot of other Google products which where announced with great fanfare in the past.
Off-topic, I tried to buy a 1-dollar song the other day. This may come as a surprise, but not only Google, but also Amazon were not willing to take my money. Of course iTunes happily accommodated me, as it has always been doing for many years.
To some extent. Google has to whitelist the apps that use the API. Right now that means you have access to Google's media offerings (including Youtube and G+) of course, but also Netflix and Hulu. Not Amazon yet or (obviously) iTunes.
It will play your local music content, but only recently whitelisted a few apps capable of playing your own video files (even then the codecs and containers supported by Chromecast are a short list, so be prepared to do a bunch of transcoding).
It's not open for sure. But it's not bad either; at $35 I'm willing to forgive the lack of hackability (I have a linux box on the same TV for that, this thing is just a convenience).
And the UI is basically perfect: pull the phone out of your pocket, play the video using exactly the same apps you're used to, and just click the chromecast button to send it to the TV. No more hunting for remotes; on my TV it will even turn it on and switch to the right input source automatically.
At this point, mainly cost and size (just plug it into the back of the tv and it is out of the way). Potentially, apps, but that is a sore point at the moment, as there are not many to speak of.
It's cheap. I bought one for my bedroom tv which I only use when falling asleep. I already have a Roku for the living room. Until the SDK comes out their features cannot be compared.
In mine and my wife's parents cases, Netflix. They didn't even know such a service existed before though, or they might've had a different solution in place already.
My sisters, Netflix and for my younger sister mainly YouTube and Google Music (which she rarely used before she got the Chromecast, as she has an iPhone and the app just came out for iOS).
Agreed. We think this approach is brilliant and suggests Google sees the TV as merely another screen. Chromecast combines the web dev model with the processing power of PCs (and mobile devices), making it a more flexible and powerful way to reshape the TV as another computing endpoint. Most importantly, Google innovation no longer is constrained by TV manufacturers and their divergent interests. Here's a Google game console: screen (TV) + processing (PC) + controllers (mobile device).
Google's long game still looks good in this area, IMO.