02-24-2024 08:12 AM
Hi all,
I'm currently replacing my smart speaker system from Teufel with native Google products. One interface is a blueray receiver (Teufel Impaq 8000) with several wired speakers. Before it was connecte to a Teufel Raumfeld Connector with Chromecast Build-In, but in general Raumfeld connectivity has been broken for actually years now, and neither of the two companies is making a move to fix that. Different issue.
The issue at hand is, that I wanted to use a Chromecast Gen3 that I have to cast audio to that receiver, via HDMI. Nice perk of HDMI is that in theory it can start said receiver thanks to CEC. Generally that works, and music plays. However the music is muted, in parts, and sometimes there is a relative loud popping sound. Its every few ten seconds or so, relatively irregular I'd say. Through trial an error I found out, that if the TV is running, picking up the video signal which apparently is emitted fro Chromecast anyway, even if I'm casting music from Youtube Music (artist, title & album art), the audio runs stably, with issues. As soon as I turn it off, it starts again.
I found this repsonse to a similar issue on reddit, which may be a hint on what is happening:
"The problem you are running into is that the Chromecast will not power up completely until it successfully negotiates HDCP encryption for the video signal between itself and the display. You will either need to leave it connected to a TV (That must be on, or that negotiates HDCP when it is in standby) through the audio extractor, or you would need a device that simulates a display to defeat the HDCP check to use it as you are describing."
Does anyone of you run a similar setup and knows how to avoid the matter? Chromecast Audio being discontinued would make sense to me, if the "normal" Chromecasts could fulfil it's purpose and then even have perks like CEC, but apparently they are not designed for that use case?
Any help much appreciated!
02-27-2024 04:16 PM
Hi patdj182,
Thanks for posting here in the Google Nest Community. First and foremost, the Chromecast device is designed to work on a TV. HDMI communication, which sends both video and audio, is utilized instead of splitting audio and video out. This is the reason why others connect it to a receiver instead of connecting it to a TV directly. The receiver splits the audio and video, which means it’s not the Chromecast’s task anymore since it’s the receiver's job now as it took both audio and video feeds from the Chromecast device. Your Chromecast 3rd Gen is working as intended. It doesn’t matter if the app that was cast is for audio only; it would operate as long as it met the requirement.
I hope this sheds some light on the situation. Let us know if you still have questions.
Thanks,
Kimy