Disclaimer: This thread was migrated from our previous version of the Google Nest Community. You can continue to receive updates on your thread issue here or simply ask, browse or more in the new Google Nest Community.
Original Poster: Ryan Trepanier
Hello. I just purchased a new chromecast with google tv. So far, it works very well, however I'm having an issue with audio. The audio works well, but every 5 minutes or so, the audio cuts out for about a second, then returns. It's very disruptive. I had a similar problem in the past with Google Movies. I have been unable to purchase and stream movies. The audio issue is happening across apps. It's not just one particular. I have a soundbar connected to my TV connected through digital audio in. The chromecast is plugged into an HDMI on my TV. I did not have any of these issues with my previous chromecast device. Any help anyone could provide would be greatly appreciated.
this problem has been going on for months and months with no resolution. seems to be related to PCM audio and, for me anyway, optical out from my TCL tv. no issues using the tv's built-in roku, only with the chromecast with google tv. have tried turning on/off CEC, different sound settings, etc. and problem will not go away. makes the CCwGTV unusable. previous thread had dozens of people with same problem. not an issue with the network as, again, roku works flawlessly.
I'm sorry about the delayed response, thank you for being patient! The team that is current looking into the issue wanted me to confirm that this issue only occurs when using a soundbar, not the default speakers of the TV, would you, or anyone, be able to test that?
Again, I thank you for being patient with this issue, and if you had any questions or concerns for me, please ask!
does not happen with built-in speakers. for me the setup is: TCL television with GGwGTV plugged into HDMI input. optical output for sound going into a receiver. sound drops out about every 30-90 seconds. someone on the other thread felt it was related to PCM audio but i have not tested enough to determine this.
Would you be able to observe what happens when the surround sound is disabled under Google TV's Display & Sound settings? Then the team also recommends using HDMI-arc connection from TV to receiver, and then enable HDMI pass-through for all devices instead of using optical cable. Either that, or you can also try plugging in the Chromecast with Google TV to the HDMI input of the receiver to test if the same issue would occur.
I hope that sense, if you had any questions, please let me know!
no difference as i have already tried turning surround on & off.
my receiver only has optical in, not HDMI, so some of your suggestions are not possible (and don't address the core bug so many of us are experiencing).
No problem, just trying to get as much information as possible for our engineering team, I really do thank you for being patient with this.
If you are willing to, would you re-create the bug on the Chromecast, then submit feedback to us with the System logs box checked, so we can see the details of the device? For the description, you can just put CCT3 5.1 surround sound issue, that way you don't have to worry about making a long response.
Thank you for help on this issue,
done. audio had dropped out about 2 minutes before i submitted feedback.
not sure if this is really a 5.1 surround issue as, again, i'm using optical out of my tv (which is just stereo, not 5.1).
my tv also has a roku built-in and, when i use that with the optical out, there are no dropouts. it only happens when watching with the ccwgtv.
Thank you so much for your help on this. The engineering wanted this particular issue to be submitted under that 5.1 surround sound issue for ease of finding that in the feedback reports. They will go ahead and take a look into this issue and we will re-open this thread once we have any updates.
If you had any more questions or concerns, please let me know! If not, I'll go ahead and lock up this thread in 24 hours.
Of course! We'll be locking it for now since the correct steps for someone who is experiencing this issue is to submit feedback with system logs enabled. At this point in time, it does not require any further discussion as we would just be repeating the same steps over again.
We'll provide updates on this issue as soon as we hear back from that team.