Hello, I write my mail on two PC's to check my correspondence to the Mailing list, one is a desktop PC and the other is a laptop, both with Tumbleweed as the platform.
The Tumbleweed on the laptop is in the state of the one provided by openSUSE and I have not modified it in any way. In the Message; Subject : Re: [packman] Kodi 21.0 Omega - Update against sound issues on Leap Message-ID : <[email protected]> Date & Time: Wed, 1 May 2024 12:16:16 +0200 [MH] == Manfred Hollstein <[email protected]> has written: [...] MH> As I wrote several times before, I cannot reproduce what you see! Both MH> variants work for me here and produce sound. May I suggest that you MH> create an issue upstream? Please include all details such as OS platform MH> and the version of pipewire including where you got them from. I can't understand what you are talking about. Do you understand what your proposal is? In the Message; Subject : [packman] Kodi 21.0 Omega - Update against sound issues on Leap Message-ID : <[email protected]> Date & Time: Mon, 29 Apr 2024 13:59:33 +0200 [MH] == Manfred Hollstein <[email protected]> has written: [...] MH> We have therefore extended the /usr/bin/kodi script to detect, if the MH> installation is kind of broken: MH> # Work around a possibly broken installation of pipewire on openSUSE Leap MH> # see 'https://bugzilla.opensuse.org/show_bug.cgi?id=1222636' MH> if [ -x ${prefix}/bin/pulseaudio ] && MH> [ -x ${prefix}/bin/pipewire ] && MH> [ ! -x ${prefix}/bin/pipewire-pulse ]; then MH> ENV_ARGS="--audio-backend=pulseaudio" MH> fi MH> This means that a default installation of Leap 15.5 or 15.6 will cause MH> kodi to add "--audio-backend=pulseaudio" by itself. Please note, you can MH> still override this by adding your own preference by adding one of the MH> following yourself: MH> --audio-backend=<backend> Select which audio backend to use. MH> Available audio backends are: alsa, pipewire, pulseaudio, alsa+pulseaudio [...] Your proposal means; kodi, which by default starts by activating the API to pipewire, should be replaced by activating the API to pulseaudio, since this will not play sound. Naturally, this switch is only for the API, and sound is played via pipewire. Furthermore, can't you understand that kodi built with the -DENABLE_PIPEWIRE=OFF switch does the same thing as kodi start up with the pulseaudio API enabled (ie., --audio-backend=pulseaudio)? I ask because this is a good time to ask; In the Message; Subject : Re: [packman] Kodi 21.0 Omega - Update against sound issues on Leap Message-ID : <[email protected]> Date & Time: Tue, 30 Apr 2024 09:21:50 +0200 [MH] == Manfred Hollstein <[email protected]> has written: [...] MH> This is the situation that a Leap installation with all updates MH> installed is in. It has /usr/bin/pulseaudio and /usr/bin/pipewire, but MH> no /usr/bin/pipewire-pulseaudio. [...] Is this really? It still works, but installing pulseaudio instead of pipewire-pulseaudio is not in line with the basic idea of pipewire development, is it? What about Tumbleweed, which updates like nothing leap has ever seen, and is still on pipewire-pulseaudio? More to the point, the maintainer(s?) of pipewire in both Leap and Tumbleweed should be the same person(s?). I can't believe he (or they) would change the specs for Leap and Tumbleweed, though, can you? Kind Regards. --- ┏━━┓彡 Masaru Nomiya mail-to: nomiya @ lake.dti.ne.jp ┃＼／彡 ┗━━┛ "To hire for skills, firms will need to implement robust and intentional changes in their hiring practices ― and change is hard." -- Employers don’t practice what they preach on skills-based hiring -- _______________________________________________ Packman mailing list [email protected] https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
