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.
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.
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"
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.
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.
Specifically, only Tab casting/full screen casting works to Chromecast. Go ahead and cast your tab/screen to your Samsung TV. I'll wait.
Since when? Source?
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...
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.
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.
* 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?
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.
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 ;)
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.
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.
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.
Besides it's only $35 and it works well.
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.
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.
...
"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
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".
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.
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...
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.
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.
See http://chromecast.com/apps for the current list.
I really only use Google Play, Netflix, YouTube and tab casting though.
I guess I'm just hoping for a lot more than what I have right now.
And does it increase cord cutting ?
Team Name stream
- 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.
That's not really an advantage.
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.
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?But Spotify doesn't lock you into anything.
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.
I agree it's a shame that a standard like Miracast has incompatible implementations. However, creating another protocol just makes that situation even worse.
https://groups.google.com/forum/#!msg/chromebook-central/oYV...
http://www.ibtimes.com/chromecast-update-refreshes-google-do...
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.
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.