On Thu, 23 May 2024 17:57:51 +0000
dep via tde-users <users(a)trinitydesktop.org> wrote:
As I said, no sound. The occasional crackle or
alarming pop. Video is fine. EPG is fine. Started it in a terminal and after the expected
bitching about not liking my desktop, this:
[code]
mpeg2_v4l2m2m @ 0x7fff5804e100] Could not find a valid device
[mpeg2_v4l2m2m @ 0x7fff5804e100] can't configure decoder
[00007fff58013710] avcodec decoder error: cannot start codec (mpeg2_v4l2m2m)
[00005556238c9770] main audio output error: too low audio sample frequency (0)
[00007fff58053150] main decoder error: failed to create audio output
[mpeg2_v4l2m2m @ 0x7fff5804e100] Could not find a valid device
[mpeg2_v4l2m2m @ 0x7fff5804e100] can't configure decoder
[00007fff58013710] avcodec decoder error: cannot start codec (mpeg2_v4l2m2m)
[00007fff40006870] gles2 gl: Initialized libplacebo v4.208.0 (API v208)
[mpeg2video @ 0x7fff5804e100] get_buffer() failed
[mpeg2video @ 0x7fff5804e100] get_buffer() failed (-12 (nil))
[/code]
The thing that stands out to me here is the "v4l" bit showing up in one of
the codec names. That last character is an L, not a 1, so it's presumably
referring to Video4Linux, which is a set of kernel drivers for video
hardware. The sequence seems to suggest that v4l isn't quite working
right and can't get the audio feed.
kaffeine doesn't link v4l itself, but picks it up through xine-lib. xine-lib
may be linking it directly or picking it up through ffmpeg, depending on
how your distro has it set up. The presence of "avcodec" in the trace
suggests ffmpeg's involvement.
So I'd start at the kernel level, verify that the correct drivers are available
and being attached to the correct devices, then move upward through
ffmpeg and xine-lib. (If VLC, which uses libmpeg2 for mpeg2 decoding,
happens to work, that would practically be a smoking gun pointing at
ffmpeg or xine.)
E. Liddell