Hi Masaru (or is Nomiya your first name?), I strip lots of stuff below to make it more readable.
On Wed, 08 May 2024, 11:04:39 +0200, Masaru Nomiya wrote: > [...] > MH> let me ask one question first: did kodi-21 from Packman work for you at > MH> all? If so, when did the problem start? > > Good question. > > Thepackman kodi worked with --audio-backend=pulseaudio as well as my > own build of kodi. Based on your "fix for pipewire" below, is it right that it does work now? > [...] > I've found the cause. > > I found a problem with the pipedwire configuration, fixed it, and > everything works fine. Great! Do you mind sharing the "problem with the pipewire configuration"? Perhaps the fix should go into the official pipewire packages... > [...] > Why do you want users to add --audio-backend=pulseaudio? Because it does not work on Leap otherwise... > [...] > MH> 1. /usr/bin/pulseaudio is installed > MH> 2. /usr/bin/pipewire is installed > MH> 3. /usr/bin/pipewire-pulse is NOT installed > > MH> If all three items are true, we will not get any sound unless we > MH> explicitly force kodi to use "--audio-backend=pulseaudio". If one item > MH> is not true, we don't force anything. > > As I wrote in a previous email, you are right, in the case of the > pilseaido system, --audio-backend=pulseaudio must be added. Yep, that's what my patch added. > But Tumbleweed, as you know, is not a pulseaudio system, but a > pipewire system, and --audio-backend=pulseaudio is to make the kodi > sound via pipewire-pulse. Does it make sense? > I think it's rather unnecessary. On Tumbleweed my patch does not change anything. So you're right in that the change was only relevant for Leap. The more I think about it, I agree with you that we should disable all PW stuff on Leap, but leave PA and PW enabled for Tumbleweed. > [..] > MN> > It still works, but installing pulseaudio instead of > MN> > pipewire-pulseaudio is not in line with the basic idea of pipewire > MN> > development, is it? > > MH> I'm not a pipewire developer, so I don't know. I just try to figure out, > MH> what needs to be done to make kodi work on both Tumbleweed and Leap. > > As I mentioned in a previous email, in Leap, the pulseaudio system is > the default and the transition to the pipewire system is > optional. > But, in Tumbleweed, the pipewire system is the default state. > The idea that the same kodi can be used in both Leap and Tumbleweed is > quite understandable. However, the fact that it asks you to start with > --audio-backend=pul;seaudio is not.... Kodi does *not* ask the user to add that parameter! Instead it finds out if the parameter must be added to produce sound at all, without any user interaction - the user still can override if wanted/necessary due to the user specific environment and setup. > In other words, kodi is not the only one that provides source for both > pulseaudio and pipewire, but as far as I know, there are audacious, > deadbeef, and mpd. > > And, their build conditions for these are the same as for kodi, and > pulseaudio is compatible with both pipewire and kodi. > > That is, it is up to the builders to decide whether to support > pulseaudio or pipewire. I found that audacious, deadbeef, and mpd all > support puseaudio on Leap, and pipewire on Tumbleweed. > I think kodi should do the same, shouldn't you? See above, I'll push my change to Kodi to disable pipewire for Leap. > BTW, I have question. > > The packman kodi can't display videos; > > 1. codec is h264 > > 2. codec is rv40 Do you have examples for these? h264 can be played here without issues. > My kodi plays fine, but are these specifications? Which ffmpeg packages are you using? > Best Regards. Cheers. l8er manfred
signature.asc
Description: PGP signature
_______________________________________________ Packman mailing list [email protected] https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
