271–280 of 609 posts
> Today, we’re introducing Google TV Streamer, a more premium device built for the new era of entertainment and smart home needs.
> , bringing its best features to our next-generation 4K TV streaming device — but as a faster, more premium version.
This line in particular puts a bad test in my mouth, because my $2k LG G2 OLED has the worst support for casting I've ever experienced. In fact the software in general is so bad I was excited to pre-order the new Google TV Streamer this morning, so I don't have to deal with it again.
Chromecast used to be a great product. I had my gen 1 Chromecast for the last 10 years until recently when it got fried by this piece of crap TV I plugged it into. It was exactly what I want in a device: Do one thing and do it well. I decided to replace it with a new "Chromecast" device to find out that it bears next to no resemblance to the original. Today's Chromecasts are just wannabe Roku devices with actual cast…
The original Chromecast was really good at just letting you cast anything to a TV.
Earlier quoted context omitted.
Can't have nice things indeed. An alt: Apple AirPlay works super well even with Android tvs nowadays.
Isn't AirPlay only good for screen casting as opposed to casting videos directly? My conclusion was that it's not feasible to use AirPlay to cast a video at the full frame rate and sound synced.
Earlier quoted context omitted.
True, but at that point, what does the "Chrome" part of Chromecast mean? It made much more sense when the device was tied to a browser, and then (kinda) apps on a phone. Once they added a remote, I think the writing was on the wall for the name "Chromecast". Google TV is a better "brand", IMO.
but the new brand is actually "Google TV Streamer" (3 words) why didnt they just go for "Google TV" (2 words) they also could have played a bit "Google TOP" (because its a table top device) , "Google S" (S for Streamer) , i think the 3 word "Google TV Streamer" , is function over form gone wrong
Chromecast used to be a great product. I had my gen 1 Chromecast for the last 10 years until recently when it got fried by this piece of crap TV I plugged it into. It was exactly what I want in a device: Do one thing and do it well. I decided to replace it with a new "Chromecast" device to find out that it bears next to no resemblance to the original. Today's Chromecasts are just wannabe Roku devices with actual cast…
well, they no longer produce the "display-only" Chromecast in favor of their "Google TV" sticks with Remote etc. Not that much of a shock here, the market moved on from simple wireless display dongles. Unfortunately no sign of Google Cast protocol being opened for general purpose use. Would be great to be able to run your own custom Receiver-device without needing a Google certificate...
Fun fact: There was a guy who managed to extract the keys out of one of the earlier Chromecasts. He eventually stopped working on (or at least posting on XDA about) it because he was hired by Google. There isn’t really any decent open casting protocol with adoption. DLNA (UPnP) is pretty well implemented in proprietary devices (besides uncontrollable latency up to 10s on Samsung TVs), but there are neither decent fre…
[EDIT] I've just seen discussion on why it's not equivalent in response to this comment here https://news.ycombinator.com/item?id=41171297
Earlier quoted context omitted.
> most of all by being open Didn't Chromecasts work with DIAL which was an open protocol? https://www.dial-multiscreen.org/dial/protocol-specification
Google Cast was originally built on top of DIAL, but DIAL itself is mostly about device discovery IIRC. Nowadays it's all mDNS instead.
The DIAL spec documents spend three pages talking about discovery and sixteen pages talking about state tracking, launching, HDMI-CEC, etc.
It's a pretty basic protocol spec since it mostly relies on things like UPnP for discovery and HTTP REST so a lot of complications are already defined in other specs.
Chromecast used to be a great product. I had my gen 1 Chromecast for the last 10 years until recently when it got fried by this piece of crap TV I plugged it into. It was exactly what I want in a device: Do one thing and do it well. I decided to replace it with a new "Chromecast" device to find out that it bears next to no resemblance to the original. Today's Chromecasts are just wannabe Roku devices with actual cast…
My experience was the opposite: my gen1 Chromecast's unreliable streaming is what made me get a Raspberry pi 3 :) IIRC the problem likely was the lack of support for 5Ghz WiFi combined with crowded channels in my area.