sound disappears on mx23.1 using kodi and vlc

[django013]

... easiest way to test that is to see if your audio disappears while using systemd.

OK, I started system using systemd - same behaviour with different timings

also presuming that the audio is supposed to come out the HDMI cable. when the sound drops away, is a different output selected in pavucontrol, and is the HDMI still available as a choice if so?

pavucontrol is unchanged after disapearing sound.

I have to admit, that I changed /etc/pulse/default.pa where I disabled module switch:

Code: Select all

#load-module module-switch-on-port-available

... and enabled this:

Code: Select all

load-module module-alsa-sink

With this changes, every alsa-sink appears as selectable in pavucontrol (some sinks have the addition "not available"), but this list remains unchanged on sound disappearing or reappearing

[Stevo]

Your hardware is supported by the stock Debian 6.1 kernel, so can you install and run kodi and vlc on that kernel to see if that makes any difference?

[swarfendor437]

How was KODI and VLC installed? I've discovered issues with apps on another KDE distro that uses snap and flatpak heavily. Using Synaptic Package Manager resolved my issue of AisleRiot Solitaire crashing on launch with the Snap version, no issues with the Apt install via Synaptic. I noticed in the terminal screenshot about failure to connect to Jackxxx, Perhaps you need to install Jack packages via Synaptic. I also prefer ALSA over Pulse Audio, so much so that on another distro I disabled it by creating a Pulseoff folder in /etc and dragging Pulse folder into it. Then installed all ALSA packages except for OSS and Jack (You only need Jack normally if you use multiple audio devices. Also installed Qasconfig, Qasctrl, and Qasmixer.

[django013]

Your hardware is supported by the stock Debian 6.1 kernel, so can you install and run kodi and vlc on that kernel to see if that makes any difference?

I bootet with kernel 6.1 and it made no difference. Sound disappeard faster than with other kernels and did not come back.

How was KODI and VLC installed?

I used MX package manager (debian packages)

I noticed in the terminal screenshot about failure to connect to Jackxxx ...

I noticed the same. Don't know, why kody tries to connect to jack.
From compiling kodi I know, that kody relies on pipewire, which is supposed to be a replacement for jack ...

I also prefer ALSA over Pulse Audio ...

I don't care for type of audio system. Whatever works would be fine for me.
I would prefer a system, that can be statically configured and setup, without udev, cable or edid checking, whatever.
Tell the system, what drivers should be loaded and then use that system.

On my mediacenter I don't like experiments or kidding - my hardware would not change, so the system has no need to enable dynamic changes.
My amp supports any audioformat I have, so passthrough should work for any streams.

If someone knows how to do a static setup, any hint will be appreciated a lot!

[j2mcgreg]

Your lack of a swap partition is cause for concern. There are a lot of folks touting the idea that with enough ram available you can forgo creating a swap partition or file, but the reality is that some applications still expect it to be there (even though it may never be used) and can give unpridictable results when swap space is not present. The good news is that you can add a swap file at any time and here’s how:

https://www.digitalocean.com/community/ ... -debian-11

[Stevo]

Another experiment would be to run the Live session of the ISO that MX was installed from, update VLC and maybe Kodi (don't think bookworm has done any upgrades of Kodi, though) and then see if the same problems occur in the live session.

[django013]

Are there no logging/debug options that could be turned on to get more meaningful output that could be used to narrow down the cause?

[Stevo]

Something that's pretty quick is to install our indicator-sound-switcher and see if you can redirect the sound to your preferred output if you have a choice in its options. You could also look in VLC's Tools/Preferences/Audio and see if switching that from Automatic to manually point to what you want might fix it. VLC's "Automatic" has been known to have issues before.