kodi-rpi (f)kms video issues

[unformatted]

I'm using latest kodi-rpi 19.0-9 on RPi4 4GB with armv7l and have some questions.

My hardware setup includes an HDMI audio extractor on which I can't get audio with kms driver. Problem is explained here by HiassofT: https://www.raspberrypi.org/forums/viewtopic.php?f=29&t=288234&hilit=kms+hdmi+sound&sid=de66b935c9cd67d5bcfc7b408b1b94a4&start=350#p1786593 I just couldn't get the edid stuff to work so I'm stuck with fkms for the moment.

However I've been testing some clips, movies and live TV with both kms and fkms, see attached.

I noticed that the jellyfish h264 does not start without any gpu_mem, both kms and fkms. As soon as I add gpu_mem it works. I use 320 while that was recommended with fkms for kodi 18 but I wonder if there is a recommended setting for use with kms driver.

[graysky]

My memory of lots of threads around this issue is not to use fkms. Here is a longer thread discussing it, too lazy to review myself for relevance: viewtopic.php?f=65&t=15165

Others may exists on kodi forums, rpi forums like you linked, or github issues.

[unformatted]

@graysky that thread is audio, my question was on video.

[graysky]

$this->bbcode_second_pass_quote('unformatted', 'I')'m using latest kodi-rpi 19.0-9 on RPi4 4GB with armv7l and have some questions.

...

but I wonder if there is a recommended setting for use with kms driver.

[unformatted]

Sorry for that, guess I kind of drifted away after days of testing.

If I have my config.txt as follows:
$this->bbcode_second_pass_code('', '
dtparam=audio=on
dtoverlay=vc4-kms-v3d,cma-512
dtoverlay=rpivid-v4l2
disable_overscan=1
disable_fw_kms_setup=1
initramfs initramfs-linux.img followkernel
')
I noticed that the jellyfish h264 does not start. The other jellyfishes play nice. Same issue when I change kms to fkms (just to test).
Only when I add gpu_mem=320 (perhaps other values will also do but haven't tested). I'm just wondering why I should need to add gpu_mem for this video. Other movies (h264) play fine without.

(I just included your 4 lines directly in config.txt, with include line the result is the same).

[graysky]

If you rebooted after modifying /boot/config.txt there should not be a need for the gpu_mem= line. Are you sure the h264 test clip is good? What does your kodi.log in debug mode show when you try playing that file? Can you play other h264 clips?

[unformatted]

I just downloaded the clip again to be sure:

https://test-videos.co.uk/vids/jellyfish/mp4/h264/1080/Jellyfish_1080_10s_30MB.mp4

First I play the h265 clip (from the same site!) and then the h264, here's the last part of the log:

https://pastebin.com/79wP0twZ

The log shows the 265 playing first, then the 264. The 264 looks like it's going to start (playing info in kodi top right corner) but nothing happens. There's an error in the log:

$this->bbcode_second_pass_code('', 'ERROR <general>: ffmpeg[0x5e58dc8X]: [h264_v4l2m2m] === poll unexpected TIMEOUT: events=0x43, cap buffers=20')

Other h264 plays fine, I've tested about a dozen of movies and I've seen no problems so far. Also live TV HD channels are h264 and play fine. It's only this clip. It's not a very big deal to me because others play fine but I'm juist curious why this is and why it will play as soon as I add gpu_mem.

[graysky]

Where did you get Jellyfish_1080_10s_30MB_h264.mp4 from your log? The test clips provided by https://www.jell.yfish.us/ are all all in a mkv container.

[unformatted]

$this->bbcode_second_pass_quote('', '
')I just downloaded the clip again to be sure:

https://test-videos.co.uk/vids/jellyfis ... s_30MB.mp4

[unformatted]

Just downloaded https://www.jell.yfish.us/media/jellyfi ... d-h264.mkv and that played ok. Thanks for pointing that out.

That raises the question what's wrong with the mp4. Can you play that?