• 1
  • 2
  • 3
  • 4(current)
  • 5
  • 6
  • 8
v18 HDMI Audio Pass-Through Momentary Cutout
#46
I think I finally got rid of the cutouts, 4 days ago I've upgraded my system from 18.04 to 19.10 and since then I had no more cutouts.
Seems like it was really a problem with the alsa version in 18.04.

@mossman1120 maybe worth a shot upgrading?
Kodi 21.0α | Ubuntu 22.04.3 | Kernel 6.4.x | intel i5-12600K | Gigabyte Z690 Gaming X DDR4 | Corsair 2x8192MB (DDR4-3200) | HDPlex H5v2 | HDPlex 400W HiFi DC-ATX | Pioneer VSX-934 | LG 65B7D
Reply
#47
(2019-11-04, 08:53)3dfx Wrote: I think I finally got rid of the cutouts, 4 days ago I've upgraded my system from 18.04 to 19.10 and since then I had no more cutouts.
Seems like it was really a problem with the alsa version in 18.04.

@mossman1120 maybe worth a shot upgrading?

Oh the is great news. Do you mind sharing what kernel you are running? Can you generate and share your alas debugging information generated using the following steps:

php:

Excerpt from https://help.ubuntu.com/community/SoundT...gProcedure (Step 3)

Tip: If you have a wheel mouse or 3-button mouse, you do not need to type the commands into the Terminal. Instead, copy the commands from this web page
and paste them into the terminal. To do this, move your mouse cursor over the start of the command written on the Web page. Then press the left mouse
button and drag the mouse till the end of the command to highlight the whole command; then release the mouse button. Then press the middle mouse button
or mouse wheel anywhere inside the Terminal. The command should now be printed in the Terminal without errors. Now press <Enter> to execute the command.

wget -O alsa-info.sh http://www.alsa-project.org/alsa-info.sh && chmod +x ./alsa-info.sh && ./alsa-info.sh

Here is the version information from my system:

php:

!!Kernel Information
!!------------------

Kernel release:    5.0.0-31-generic
Operating System:  GNU/Linux
Architecture:      x86_64
Processor:         x86_64
SMP Enabled:       Yes


!!ALSA Version
!!------------

Driver version:     k5.0.0-31-generic
Library version:    1.1.3
Utilities version:  1.1.3


!!Loaded ALSA modules
!!-------------------

snd_hda_intel


!!Soundcards recognised by ALSA
!!-----------------------------

0 [PCH            ]: HDA-Intel - HDA Intel PCH
                      HDA Intel PCH at 0x2ffff20000 irq 141


!!PCI Soundcards installed in the system
!!--------------------------------------

00:1f.3 Audio device: Intel Corporation 200 Series PCH HD Audio


!!Advanced information - PCI Vendor/Device/Subsystem ID's
!!-------------------------------------------------------

00:1f.3 0403: 8086:a2f0
Subsystem: 1849:1222


!!Modprobe options (Sound related)
!!--------------------------------

snd_pcsp: index=-2
snd_usb_audio: index=-2
snd_atiixp_modem: index=-2
snd_intel8x0m: index=-2
snd_via82xx_modem: index=-2
snd_atiixp_modem: index=-2
snd_intel8x0m: index=-2
snd_via82xx_modem: index=-2
snd_usb_audio: index=-2
snd_usb_caiaq: index=-2
snd_usb_ua101: index=-2
snd_usb_us122l: index=-2
snd_usb_usx2y: index=-2
snd_cmipci: mpu_port=0x330 fm_port=0x388
snd_pcsp: index=-2
snd_usb_audio: index=-2


!!Loaded sound module options
!!---------------------------

!!Module: snd_hda_intel
align_buffer_size : -1
bdl_pos_adj : -1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1
beep_mode : N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N
enable : Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y
enable_msi : -1
id : (null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(n
ull),(null)
index : -1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1
jackpoll_ms : 0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
model : (null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null)
,(null),(null)
patch : (null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null)
,(null),(null)
pm_blacklist : Y
position_fix : -1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1
power_save : 1
power_save_controller : Y
probe_mask : -1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1
probe_only : 0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
single_cmd : -1
snoop : -1

I am wondering if there are some nightly or back port repos that I can add and use to get the fixes from 19.10. I would like to see if it is possible.
Kodi 19.0 | Ubuntu 20.04.2 | Kernel 5.4.0-67-generic | Intel i7-8700K | ASRock Z370 Gaming-ITX/ac | Ballistix Sport LT 2x16384MB (DDR4-2666) | Samsung 970 PRO 1TB |LG WH16NS60 | Cooler Master Elite 130 | Yamaha RX-A780Samsung Q70R
Reply
#48
(2019-11-04, 20:21)mossman1120 Wrote: I am wondering if there are some nightly or back port repos that I can add and use to get the fixes from 19.10. I would like to see if it is possible. 

I'm not sure, if there is a backport repo, I didn't find it Confused
But I also tested 2 days with 19.04 as the upgrade-path looks like this 18.04 => 19.04 => 19.10.
Luckily I had no issues upgrading, but you never know, I made a CloneZilla image of my system-drive first Big Grin Rofl

Here's my log: Alsa-Info
Kodi 21.0α | Ubuntu 22.04.3 | Kernel 6.4.x | intel i5-12600K | Gigabyte Z690 Gaming X DDR4 | Corsair 2x8192MB (DDR4-3200) | HDPlex H5v2 | HDPlex 400W HiFi DC-ATX | Pioneer VSX-934 | LG 65B7D
Reply
#49
(2019-11-05, 07:51)3dfx Wrote:
(2019-11-04, 20:21)mossman1120 Wrote: I am wondering if there are some nightly or back port repos that I can add and use to get the fixes from 19.10. I would like to see if it is possible. 

I'm not sure, if there is a backport repo, I didn't find it Confused
But I also tested 2 days with 19.04 as the upgrade-path looks like this 18.04 => 19.04 => 19.10.
Luckily I had no issues upgrading, but you never know, I made a CloneZilla image of my system-drive first Big Grin Rofl

Here's my log: Alsa-Info 

So a quick scan of your ALSA information shows you are using driver version 5.4.0 (same as your kernel) along with library and utility version 1.1.9. So I think I am going to try to upgrade the kernel to 5.4 and see what that does to the output. I am hoping the driver and utility version are tied to the kernel. If not I think I saw a link to a ALAS nightly repo I just have to figure out where I saw that...go figure I didn't bookmark it  https://launchpad.net/~ubuntu-audio-dev/...alsa-daily . This seems to have a build for 18.04 / 19.04 from 7/8/2019.
Kodi 19.0 | Ubuntu 20.04.2 | Kernel 5.4.0-67-generic | Intel i7-8700K | ASRock Z370 Gaming-ITX/ac | Ballistix Sport LT 2x16384MB (DDR4-2666) | Samsung 970 PRO 1TB |LG WH16NS60 | Cooler Master Elite 130 | Yamaha RX-A780Samsung Q70R
Reply
#50
I had the 5.4-rc kernel installed before upgrading, the is the alsa-driver is in the kernel but it didn't had any effect on 18.04.
Also I had tried these modprobe options (without effect):
Code:
snd_hda_intel: power_save=0 power_save_controller=N

What I concluded was: there are issues in the lib and/or utility in 1.1.3 (what's installed on 18.04).
If you find a package of 1.1.9 (19.10) or 1.1.8 (19.04), try that. Had no issues with both versions.

But as I already upgraded to 19.04 I thought, why not go up to 19.10 Smile

I upgraded on 10/30 (for european users 30.10.) and today is the 7th day after upgrading and still got no cutouts Love
Kodi 21.0α | Ubuntu 22.04.3 | Kernel 6.4.x | intel i5-12600K | Gigabyte Z690 Gaming X DDR4 | Corsair 2x8192MB (DDR4-3200) | HDPlex H5v2 | HDPlex 400W HiFi DC-ATX | Pioneer VSX-934 | LG 65B7D
Reply
#51
(2019-11-05, 08:57)3dfx Wrote: I had the 5.4-rc kernel installed before upgrading, the is the alsa-driver is in the kernel but it didn't had any effect on 18.04.
Also I had tried these modprobe options (without effect):
Code:
snd_hda_intel: power_save=0 power_save_controller=N

What I concluded was: there are issues in the lib and/or utility in 1.1.3 (what's installed on 18.04).
If you find a package of 1.1.9 (19.10) or 1.1.8 (19.04), try that. Had no issues with both versions.

But as I already upgraded to 19.04 I thought, why not go up to 19.10 Smile

I upgraded on 10/30 (for european users 30.10.) and today is the 7th day after upgrading and still got no cutouts Love
I suppose I could search for the package in the 19.10 repo and see if it just installs.
Kodi 19.0 | Ubuntu 20.04.2 | Kernel 5.4.0-67-generic | Intel i7-8700K | ASRock Z370 Gaming-ITX/ac | Ballistix Sport LT 2x16384MB (DDR4-2666) | Samsung 970 PRO 1TB |LG WH16NS60 | Cooler Master Elite 130 | Yamaha RX-A780Samsung Q70R
Reply
#52
It could be possible if there are no reverse dependencies you don't get on 18.04
Kodi 21.0α | Ubuntu 22.04.3 | Kernel 6.4.x | intel i5-12600K | Gigabyte Z690 Gaming X DDR4 | Corsair 2x8192MB (DDR4-3200) | HDPlex H5v2 | HDPlex 400W HiFi DC-ATX | Pioneer VSX-934 | LG 65B7D
Reply
#53
I plugged my problem causing HDMI switch to the AMP and the first test shows no problems playing a video file with Atmos sound Shocked
I'm gonna keep it plugged in for a while and, I'm curious if the problems are gone even with the switch.
Kodi 21.0α | Ubuntu 22.04.3 | Kernel 6.4.x | intel i5-12600K | Gigabyte Z690 Gaming X DDR4 | Corsair 2x8192MB (DDR4-3200) | HDPlex H5v2 | HDPlex 400W HiFi DC-ATX | Pioneer VSX-934 | LG 65B7D
Reply
#54
(2019-11-05, 11:42)3dfx Wrote: I plugged my problem causing HDMI switch to the AMP and the first test shows no problems playing a video file with Atmos sound Shocked
I'm gonna keep it plugged in for a while and, I'm curious if the problems are gone even with the switch.

I was able to install most of the packages but one of the core ones requires a new version of ncurses so I don't think it will be possible. I am going to try upgrading the kernel and see if I have better luck with that.
Kodi 19.0 | Ubuntu 20.04.2 | Kernel 5.4.0-67-generic | Intel i7-8700K | ASRock Z370 Gaming-ITX/ac | Ballistix Sport LT 2x16384MB (DDR4-2666) | Samsung 970 PRO 1TB |LG WH16NS60 | Cooler Master Elite 130 | Yamaha RX-A780Samsung Q70R
Reply
#55
Ohh that's bad Undecided
I also got an update, the HDMI switch still causes problems but not so often, still annoying, so I unplugged it again and it runs smoothly without that piece of cr*p switch Big Grin
Kodi 21.0α | Ubuntu 22.04.3 | Kernel 6.4.x | intel i5-12600K | Gigabyte Z690 Gaming X DDR4 | Corsair 2x8192MB (DDR4-3200) | HDPlex H5v2 | HDPlex 400W HiFi DC-ATX | Pioneer VSX-934 | LG 65B7D
Reply
#56
(2019-11-13, 09:24)3dfx Wrote: Ohh that's bad Undecided
I also got an update, the HDMI switch still causes problems but not so often, still annoying, so I unplugged it again and it runs smoothly without that piece of cr*p switch Big Grin
So I updated just the kernel to 5.3.11-050311-generic which has a new version driver. I still have my switch connected, not the Kinivo one but the Koopman man one. So far thing seem to be a lot more stable. I don't want to jinx anything. I will report back in another couple of days to see how it continues to hold up. Which switch are you using again?
Kodi 19.0 | Ubuntu 20.04.2 | Kernel 5.4.0-67-generic | Intel i7-8700K | ASRock Z370 Gaming-ITX/ac | Ballistix Sport LT 2x16384MB (DDR4-2666) | Samsung 970 PRO 1TB |LG WH16NS60 | Cooler Master Elite 130 | Yamaha RX-A780Samsung Q70R
Reply
#57
I had this UGreen switch but since I realized that it's causing problems, it isn't connected anymore.
Kodi 21.0α | Ubuntu 22.04.3 | Kernel 6.4.x | intel i5-12600K | Gigabyte Z690 Gaming X DDR4 | Corsair 2x8192MB (DDR4-3200) | HDPlex H5v2 | HDPlex 400W HiFi DC-ATX | Pioneer VSX-934 | LG 65B7D
Reply
#58
(2019-11-17, 10:01)3dfx Wrote: I had this UGreen switch but since I realized that it's causing problems, it isn't connected anymore.

I had a few days in a row with no issues and then they started to come back intermittenly. What seems to make it better is turning on the TV and AMP. Then selecting the input for Kodi. Attempt playback. If there are issues stop playback and select another input wait a few seconds and then select the Kodi input. What I have noticed is the shorter the delay to start outputting audio at the start the less likely there will be issues.

How have things been going on your end? Things still solid after the dist upgrade?
Kodi 19.0 | Ubuntu 20.04.2 | Kernel 5.4.0-67-generic | Intel i7-8700K | ASRock Z370 Gaming-ITX/ac | Ballistix Sport LT 2x16384MB (DDR4-2666) | Samsung 970 PRO 1TB |LG WH16NS60 | Cooler Master Elite 130 | Yamaha RX-A780Samsung Q70R
Reply
#59
(2019-12-12, 20:06)mossman1120 Wrote: I had a few days in a row with no issues and then they started to come back intermittenly. What seems to make it better is turning on the TV and AMP. Then selecting the input for Kodi. Attempt playback. If there are issues stop playback and select another input wait a few seconds and then select the Kodi input. What I have noticed is the shorter the delay to start outputting audio at the start the less likely there will be issues.

How have things been going on your end? Things still solid after the dist upgrade? 

Not perfect, but after the dist-upgrade the cutouts are occuruing less often as before.

And switching between HDMI inputs gets rid of the cutouts, you didn't notice that back than ^^
(2019-09-15, 09:59)3dfx Wrote: I still have some cutouts from time to time, sometimes no problems for a whole day, sometimes after watching a Video and starting another one. But switching HDMI port and back again everything is fine and I see in the Kodi-log that ALSA is reinitialized and after that all is fine

Switch HDMI inputs and take a look at your kodi.log you will see, ALSA got reloaded and another look in dmesg shows EDID gets reloaded also.
That's why I came up with the idea to write this script forcing alsa to reload:

bash:

 #!/bin/bash
xbmcLog=/var/spool/myScripts/logs/xbmc.log

MSG="explicit reload"
echo $(date +%Y/%m/%d\ %H:%M:%S)' EDID: '$MSG >> $xbmcLog

export DISPLAY=:0
OUTPUT=$(xrandr -d $DISPLAY -q | sed '/ connected/!d;s/ .*//;q')
#echo "$IDSPLAY" "$OUTPUT"
if [ "$OUTPUT" == "" ]; then
OUTPUT="DP1"
fi
xrandr -d $DISPLAY --output $OUTPUT --auto --mode 3840x2160 --rate 60 --set "Broadcast RGB" "Full"
$(showKodiMsg 1500 "EDID" "reloaded")

FAIL=1
COUNT=0
while [ $COUNT -lt 3 ]; do
COUNT=$((COUNT+1))

if [ $FAIL -ne 0 ]; then
FAIL=$(alsa force-reload | grep -i failed | wc -l)
fi

if [ $FAIL -eq 0 ]; then
COUNT=5
else
sleep 1
fi
done

MSG="forcing reload"
RES=""
if [ $FAIL -ne 0 ]; then
RES="failed!!"
else
RES="success!"
fi
MSG="$MSG $RES"
echo $(date +%Y/%m/%d\ %H:%M:%S)' ALSA: '$MSG >> $xbmcLog
$(showKodiMsg 2000 "ALSA" "$MSG")

"showKodiMsg" is a script for displaying Notification messages in Kodi
Kodi 21.0α | Ubuntu 22.04.3 | Kernel 6.4.x | intel i5-12600K | Gigabyte Z690 Gaming X DDR4 | Corsair 2x8192MB (DDR4-3200) | HDPlex H5v2 | HDPlex 400W HiFi DC-ATX | Pioneer VSX-934 | LG 65B7D
Reply
#60
(2019-12-17, 08:33)3dfx Wrote:
(2019-12-12, 20:06)mossman1120 Wrote: I had a few days in a row with no issues and then they started to come back intermittenly. What seems to make it better is turning on the TV and AMP. Then selecting the input for Kodi. Attempt playback. If there are issues stop playback and select another input wait a few seconds and then select the Kodi input. What I have noticed is the shorter the delay to start outputting audio at the start the less likely there will be issues.

How have things been going on your end? Things still solid after the dist upgrade? 

Not perfect, but after the dist-upgrade the cutouts are occuruing less often as before.

And switching between HDMI inputs gets rid of the cutouts, you didn't notice that back than ^^
(2019-09-15, 09:59)3dfx Wrote: I still have some cutouts from time to time, sometimes no problems for a whole day, sometimes after watching a Video and starting another one. But switching HDMI port and back again everything is fine and I see in the Kodi-log that ALSA is reinitialized and after that all is fine

Switch HDMI inputs and take a look at your kodi.log you will see, ALSA got reloaded and another look in dmesg shows EDID gets reloaded also.
That's why I came up with the idea to write this script forcing alsa to reload:

bash:

 #!/bin/bash
xbmcLog=/var/spool/myScripts/logs/xbmc.log

MSG="explicit reload"
echo $(date +%Y/%m/%d\ %H:%M:%S)' EDID: '$MSG >> $xbmcLog

export DISPLAY=:0
OUTPUT=$(xrandr -d $DISPLAY -q | sed '/ connected/!d;s/ .*//;q')
#echo "$IDSPLAY" "$OUTPUT"
if [ "$OUTPUT" == "" ]; then
OUTPUT="DP1"
fi
xrandr -d $DISPLAY --output $OUTPUT --auto --mode 3840x2160 --rate 60 --set "Broadcast RGB" "Full"
$(showKodiMsg 1500 "EDID" "reloaded")

FAIL=1
COUNT=0
while [ $COUNT -lt 3 ]; do
COUNT=$((COUNT+1))

if [ $FAIL -ne 0 ]; then
FAIL=$(alsa force-reload | grep -i failed | wc -l)
fi

if [ $FAIL -eq 0 ]; then
COUNT=5
else
sleep 1
fi
done

MSG="forcing reload"
RES=""
if [ $FAIL -ne 0 ]; then
RES="failed!!"
else
RES="success!"
fi
MSG="$MSG $RES"
echo $(date +%Y/%m/%d\ %H:%M:%S)' ALSA: '$MSG >> $xbmcLog
$(showKodiMsg 2000 "ALSA" "$MSG")

"showKodiMsg" is a script for displaying Notification messages in Kodi   
Are you watching for something to trigger your script or is it something that is run post input change? It almost seems like ALSA is timing out and then can't grab hold of the device again.

I forgot did you hard code your EDID information in grub?

Do you see this in dmesg? https://bugs.freedesktop.org/show_bug.cgi?id=104952
Kodi 19.0 | Ubuntu 20.04.2 | Kernel 5.4.0-67-generic | Intel i7-8700K | ASRock Z370 Gaming-ITX/ac | Ballistix Sport LT 2x16384MB (DDR4-2666) | Samsung 970 PRO 1TB |LG WH16NS60 | Cooler Master Elite 130 | Yamaha RX-A780Samsung Q70R
Reply
  • 1
  • 2
  • 3
  • 4(current)
  • 5
  • 6
  • 8

Logout Mark Read Team Forum Stats Members Help
HDMI Audio Pass-Through Momentary Cutout0