Google Discontinues Chromecast Audio (techcrunch.com)
Google has discontinued the Chromecast Audio dongle that allowed you to stream music via Wi-Fi to any dumb speaker with a 3.5mm headphone jack. If you're saddened by the news and would like to pick one up before they're completely gone, Google is now selling its remaining inventory for $15 instead of $35. TechCrunch reports: "Our product portfolio continues to evolve, and now we have a variety of products for users to enjoy audio," Google told us in a statement. "We have therefore stopped manufacturing our Chromecast Audio products. We will continue to offer assistance for Chromecast Audio devices, so users can continue to enjoy their music, podcasts and more."
Google is clearly more interested in getting people to buy its Google Home products and Assistant- or Cast-enabled speakers from its partners. It's also worth noting that all Google Home devices can connect to Bluetooth enabled speakers, though plenty of people surely have a nice speaker setup at home that doesn't have built-in Bluetooth support. "Bluetooth adapters suck," Google told us at the time, though at this point, it seems a Bluetooth adapter may just be the way to go.
Google is clearly more interested in getting people to buy its Google Home products and Assistant- or Cast-enabled speakers from its partners. It's also worth noting that all Google Home devices can connect to Bluetooth enabled speakers, though plenty of people surely have a nice speaker setup at home that doesn't have built-in Bluetooth support. "Bluetooth adapters suck," Google told us at the time, though at this point, it seems a Bluetooth adapter may just be the way to go.
Bummer, I could use another one. Nothing like listening to OK-ish digital music through four 7591a tubes. Friendly tube distortion mixed with digital artifacts. Sort of like crossing proton pack streams, might be "bad", or it might banish Zuul.
You know that a product has left Google beta and works perfectly, when Google decides to kill it outright
Take the cheese to sickbay, the doctor should see it as soon as possible - B'Elanna Torres, "Learning Curve"
I've never seen a speaker with a 3.5mm headphone jack.
Somehow 1 time out of 3 when I use bluetooth, it fails to connect giving me various excuses. Besides, AFAIK bluetooth is not lossless. Sure, shitty Chromecast puck is not gonna give you audiophile level quality, but at least there's not transcoding loss happening.
Sadly the only problem with the chromecast audio was the standard price. $35 was just too high. I got mine on a holiday sale last year for $15 with a discounted google home speaker. It let me upgrade me old yamaha 6.1 to allow easy streaming. I would have snapped up 4 more if the price was $15-$20 all the time. For $35 it was just too expensive for what it did. Honestly however if they add a 3.5 mm jack to the google home puck speaker I would get go that route.
Coffee: The lifeblood of intelligence in civilization.
I mean, it's not like Google has a long history of capriciously canceling products or anything of that sort
.
If after Google's long and dishonorable history of fucking over users you'd trust Google enough to use anything from Google, your ability to make intelligent decisions must be called into question in the most severe manner possible.
If you disagree, you're not only stupid, you're the worst kind of stupid, which is defined by a refusal to accept important new information because it might threaten your worldview.
A bluetooth dongle that seemlessly streams directly from the internet with no (extra) loss of quality and stays playing even when I leave with my phone?
Just admit it. A bluetooth dongle is nothing at all like the chromecast.
As for privacy- most people already use online music services so someone already knows what they listen to and when. You have to be especially paranoid to only play your own ripped, local, music because of privacy concerns.
I love my Chromecast audio. I use it with my 30 year old Sony receiver driving my 50 year old EPI speakers, serving up music from my Raspberry Pi running a minidlna server. Works great.
Does anyone know what it would take to rig a Google "Streaming Media Player" (i.e. the Video version with the HDMI output) to drive an old-school audio receiver?
Search for HDMI Audio Extractor. They are not especially expensive but it's another thing that you need to plug in.
I'm guessing that you don't have any friends?
https://youtu.be/Tjp5OmoDYQM?t...
https://www.amazon.com/YunList...
YunListen adapter with a 3.5mm jack -- supports DLNA as well as direct music streaming from a NAS.
Would it be easier to run a DLNA renderer on the Pi (or another Pi), add a DAC (HAT or USB), and plug it straight into the receiver?
My question is hypothetical since my current Chromecast audio is still fine, but for the record my Raspberry pi "server" lives
in the basement, while the receiver in upstairs in the living room.
Muh Headphone Jack!
I’m a Boomer, and I second this.I’m nostalgic about some vanished aspects of my youth, like few speech on college campuses, but tangled cords are not one of them.
EDIT: ...free speech on college campuses.
Though you're totally right about getting spied upon, it wasn't a walled garden. Chromecast was open enough that you could really use your way, instead of their way. Your own UI, your own controller, your own music storage. It doesn't lock you into anything, other than having to have some Android device around somewhere, for the initial installation. And after that, you don't even need Android if you don't want it. So it's more like a weird Google brick column in your garden, than like being trapped inside walls like you get with the videogame-console-like situations (Sony, Apple, etc).
As copyright owner of this comment, I authorize everyone to defeat any technological measure which limits access to it.
Second RPi running the renderer for about the same price as a Chromecast?
How's life in the hypocrite lane?