venebil dawnna joaquim
Karmen Mcarthun
I have two Chromecast with Google TV's (4k) connected to Samsung sound bars (Q80R and Q900A). There is a frequent audio skipping issue that is encountered when watching content through multiple native apps such as HBO, Netflix, and Hulu. When watching content, the audio will randomly but out for about a second before resuming. This issue does not occur at regular intervals. Sometimes it happens several times in a minute, others it has 10 or 15 minutes in between. However, it happens very frequently and is frustrating.
The issue began to occur a couple of months ago on both devices. It seems as if an update triggered it. Both the Google TVs and soundbars have been fully updated. I have noticed that on one of the soundbars with a small display, whenever the audio skips and comes back the display flashes "Dolby Atmos" or whatever encoding is being used by the content. It's as if the audio connection has dropped and reestablished. Disabling surround sound on the Google TV did not resolve the issue. I've filed feedback with logs on the devices already. Anything else I can try to fix this?
Hey there gellson,
I apologize for the late response, thank you for being patient! Were you able to fix that audio skipping issue? If not, I'd be happy to help out, as I can imagine this issue is pretty frustrating. You mentioned that you have everything up-to-date already, that's good. It's interesting that "Dolby Atmos" appears when you experience those skips. Do you have Dolby Atmos enabled on the Chromecast as well as the TV settings? Disabling Dolby Atmos on the Chromecast didn't help, but are you able to disable it on the TV?
Atmos is supported on both sound bars that the chromecasts are plugged into, but I'm not able to disable it. We were able to play Atmos content on both devices previously with no issues, the skipping has only begun to occur relatively recently.
Just out of curiosity, how do you have the soundbars set up, via Bluetooth or HDMI? If via HDMI, the most effective setup I've seen users use is having the Chromecast plugged into the HDMI port on the soundbar and having the soundbar's HDMI Out plugged into the TV's HDMI-ARC. If you have them connected via Bluetooth, you can only connect one audio device at a time.
That is no good to hear. In this case, it may be best to reach out to Chromecast Support to do a little digging into this issue. If y'all don't mind, would you be able to fill out this form to have Chromecast Support reach out to you via email? Just let me know when you have done so; otherwise, I'll check up on you to see if you need more help.
Awesome, thank you for doing that! It may take them a few days before they reach out to you since there has been an influx of cases recently, so keep an eye out. In the meantime, let me know if you have any more questions.
I have had 3 technicians come and nobody can fix tis problem. whenever i use apps off my samsung smart tv like netflix yourutbe fubo prime dazn everything is good. but when i go back to cable there is no sound . nobody knows why. is it my smart tv . it weird i have to turn off the tv and turn it back on for my cable to have sound. its very frustrating and i wish i never switched to ignite. can anybody help me.
On the Rogers box, go to Rogers - Settings - Device Settings - Audio - HDMI Audio Output and try the various settings there. The best when using a TV is usually "Stereo", instead of "Auto Detect" because the latter requires a handshake between the box and the TV, whereas the former doesn't. There appears to be a handshake issue between the TV and the Rogers box. Make sure that the firmware on your TV is up to date, especially if it's a few years old.
Edit - If this doesn't fix it, and you don't like turning the TV off/on, perhaps change the input on the TV to a different one (like ANT or other) and then back to the HDMI input you're using for Rogers. Another thing you can try is plugging the Rogers box into a different HDMI input, assuming the TV has one - HDMI2 instead of HDMI1 for example. Sometimes one of the inputs is designed for a particular type of signal...
Any update on this have the same TV and have similar issues, I have sound but it is lower while watching Ignite TV and any of the apps on the box (Netflix, Youtube, etc), switch to apps on Samsung TV and the apps are normal volume. Have tried different boxes, different HDMI ports, adjusted all the audio settings on the TV and Ignite Box and nothing helps.
Unfortunately, different devices can have different volume outputs. I'm not sure if the TV has an adjustment in the TV's audio setting, but you say you've tried them all. Usually the TV audio may have something like "voice enhancement" or something similar that can increase the audio somewhat, but I'm not sure if you can do that specifically for a specific input. Check out your Input and HDMI input settings on the TV for anything regarding audio. I suggest you give those a try again. You may want to download the operating manual for the TV and do a search of the PDF using terms like "volume" "audio", "Input" etc.
Basically the audio (not matter what application) flickers and stutters. I have a video with the KDE desktop (because it has more information than the GNOME desktop in 19.10), that shows strange behavior in the audio settings, alsamixer and pavucontrol. I've tried a lot of solutions, but never occurred to me that I could get help if I showed directly the problem.
I didn't have any problems with older distributions, the only thing that happened was that in any sound settings, the sound icon or volume would flicker visually, but never affected practically. Now, every distro has flickery settings and the audio is choppy and stutters. And I've realized that if in those older (or stable) distributions I connected and HDMI monitor, the problem appears. I can't imagine what would happen if I tried a distribution with the problem and then connected and HDMI monitor. Maybe I would hear just crackling.
Apparently, it has something to do with something called S/PDIF, because it turns on and off while the audio cracks. Also, Pavucontrol frequently says "Establishing connection to pulseaudio" while this happens. With KDE, there is a constant message of changing devices, that says "Built-in-Audio" (has seen in the video).
Some time ago, I made a post on Ask Fedora about the problem, there is a lot of information there. Maybe it will also give useful information. However, I think you can ignore most of it and just see what happens in the video. Take in consideration that although in that post I say that some distributions don't have the problem, later I discovered that if I connected and HDMI monitor, the problem will appear. Here it is:
I cannot hear music and audio normally. On every application and site, would it be Rhythmbox, Audacious, YouTube, etc, the audio is choppy. What I mean by that is that the audio cuts itself every two or three seconds, and the sound icon on the bar of GNOME disappears for the moment in which the audio goes off. Is very infuriating. And the worst thing, it happens on almost any other Linux distro!
#2) Trying to investigate the problem, I installed a plugin in GNOME that let me choose the audio output, and it showed lots of entries labeled Dummy output. When I clicked on one of them, the shell crashed
To get rid of choppy / stuttering / skipping audio when listening to music, simplyfollow post #6 here. The top of that answer reckons the method described therein is obsolete but it worked perfectly on my Dell Precision M6700 with this audio:
I had uncommented just the lines starting with default-... prior to this edit, but I found that occasionally I'd get the odd stutter/skip. I haven't had any issue since adding high-priority and nice-level as noted in later posts in the thread linked above.
Despite all these changes, I was still occasionally getting stuttering audio after laptop has been running for an extended period. I'm now trying the low latency kernel as supplied by Ubuntu. The only issue I've had so far is that I cannot access my ZFS formatted USB drive - I installed the low latency kernel manually and not via the HWE method as discussed in the linked article. I might change to the HWE method to see if I can access ZFS and then I'll be fully content.
Okay - the stuttering has returned with a vengence - despite all the changes. Feels like the machine has perfected its AI on how to become a major PITA! I'm currently trying the changes below as suggested by this article [Solved] Mint 13 Mate 32 bit, Sound Skips from back in 2012 - just 6 days shy of 9 years today. Hopefully this turns out to be the ultimate fix and hence my last edit:
I finally bit the bullet and decided to ditch PulseAudio in favor of PipeWire in Nov 2021. However, although the problem seemed to be less severe, it was still there. But just 3 days ago, I stumbled upon this GitHub issue where the OP stated that commenting one line in the default /etc/pipewire.conf file and adding 4 new lines, his skipping, stuttering, and choppy audio issues simply faded away. I did the same and what do you know - I've been listening to loads of music for the last 3 days and it is truly resolved.
None of the above fixes worked for me (pulseaudio 11.1); what solved it for me was going into /etc/pulse/daemon.conf and turning off realtime-scheduling by adding in the line realtime-scheduling = no beneath the line reading ;realtime-scheduling = yes like so:
i had skipping problems in Debian and fedora.
(Mother Gigabyte B450 Gaming X and Behringer Um2)I was able to solve it by uninstalling all audio drivers and installing pipewire, pipewire-jack, pipewire-alsa, pipewire-pulse, etc. Now everything works perfect, I spent a lot of time trying to solve this and I finally got it. I hope it works for you!
Don't worry - it's quick and painless! Just click below, and once you're logged in we'll bring you right back here and post your question. We'll remember what you've already typed in so you won't have to do it again.
90f70e40cf