Kodi Community Forum

Hi guys

I have this issue:




This is my setup:
Raspberry Pi 4 B with 5v 3.5a power supply
LibreElec 10.0.1
Ethernet connection
rclone accessing to a Google Drive

Now I have some upgrades:
-Instead of the microSD, I have SSD through a Sata USB 3.0 adapter with UASP support.
-Fan 120m 12v (powered externally) Raspberry Pi is currently at 39º / 43º approx

Note: All the upgrades were in order fix this issue.
First I thought that the glitches were related to a bad microSD, but no.
Later I thought that the glitches were due to the temp was at 73º, but no.

I usually have this issue each 3 or 4 minutes, it's very annyoing.

What I found:
-Issue happens with Ethernet or Wifi, so it's not related to the Ethernet cable
-Issue is not happening if the movie is stored in the SSD. But I don't want to download each movie from Google Drive to the SSD.
-Issue has been happening with different versions of Kodi and LibreElec.
-Issue is not related to the micro HDMI cable because as you can see in the second screenshot, when I pause the video, the issue is only over the movie, not the entire screen.
-If I rewind a little the issue is not showed, it means that the "chunk" was redownloaded, I think.


My theories:
-This can be related to Google Drive API, but I'm not using the stream from there, I'm "downloading" chunks of the file with rclone.
-The other theory can be related with the chunks of rclone, but issue is happening with rclone but also with Google Drive addon. I dont think that the addon use the same size of chunks.

Do you have any idea? I have more samples if you are required.
Thanks in advance.

Something that I forget to mention is that I'm using LG OLED 65BX and Kodi has a 3840 x 2160 resolution.
Issue happens with 4k, 1080p and 720p movies. Differents codecs also
I have a 300MB DL speed without packet loss (checked)

Issue not happens playing the movie from my PC through SMB, so It has to be related to rclone or Google Drive...

To receive meaningful assistance you will need to provide a full debug log.

The instructions are here... debug log (wiki)

If you are using the Basic Method, then ensure the following is applied...
1.Enable debugging in Settings>System Settings>Logging,
2.Restart Kodi
3.Replicate the problem.
4.Upload the log to Kodi Paste Site manually or use the Kodi Logfile Uploader. (wiki) With either method post the link to the log back here.

If you are using the Advanced Method ensure you have correctly created and applied the advancedsettings.xml file (wiki)

In both instances, you should see the word DEBUG throughout the log.

Note: Full logs only. No partial or redacted logs
Do NOT post your logs directly into the forum. Use the Kodi Paste Site. Post the link to your pasted log in the forum

(2022-01-13, 04:55)EloyFarina Wrote: [ -> ]-Issue is not happening if the movie is stored in the SSD.

So we have the GDrive connection to blame?

Logs
https://paste.kodi.tv/loxuribugo.kodi


At 2022-01-13 03:31:12.080 T:809 I saw a movie with x265 enconde without any issues for 21:36 mins

2022-01-13 03:55:13.696 T:809 to the end.  I saw a documentary with h264 encode with issues multiples times
But when I saw that documentary from SMB or directly from the SDD I had not issues. (those are not in the logs)

I think that this can be a clue:

2022-01-13 04:13:24.556 T:1822 DEBUG <general>: ffmpeg[0xead25bc0X]: [image2] Custom AVIOContext makes no sense and will be ignored with AVFMT_NOFILE format. 2022-01-13 04:13:24.557 T:1820 DEBUG <general>: ffmpeg[0xecb24270X]: [image2] Custom AVIOContext makes no sense and will be ignored with AVFMT_NOFILE format. 2022-01-13 04:13:24.563 T:1819 DEBUG <general>: ffmpeg[0xf2ba2980X]: [image2] Custom AVIOContext makes no sense and will be ignored with AVFMT_NOFILE format. 2022-01-13 04:13:24.565 T:1821 DEBUG <general>: ffmpeg[0xd33689c0X]: [image2] Custom AVIOContext makes no sense and will be ignored with AVFMT_NOFILE format. 2022-01-13 04:13:24.566 T:1822 DEBUG <general>: ffmpeg[0xead25bc0X]: [image2] Custom AVIOContext makes no sense and will be ignored with AVFMT_NOFILE format. 2022-01-13 04:13:24.572 T:1820 DEBUG <general>: ffmpeg[0xecb24270X]: [image2] Custom AVIOContext makes no sense and will be ignored with AVFMT_NOFILE format. 2022-01-13 04:13:24.580 T:1821 DEBUG <general>: ffmpeg[0xd33689c0X]: [image2] Custom AVIOContext makes no sense and will be ignored with AVFMT_NOFILE format. 2022-01-13 04:13:24.583 T:1819 DEBUG <general>: ffmpeg[0xf2ba2980X]: [image2] Custom AVIOContext makes no sense and will be ignored with AVFMT_NOFILE format. 2022-01-13 04:13:24.590 T:1821 DEBUG <general>: ffmpeg[0xd33689c0X]: [image2] Custom AVIOContext makes no sense and will be ignored with AVFMT_NOFILE format. 2022-01-13 04:13:24.591 T:1820 DEBUG <general>: ffmpeg[0xecb24270X]: [image2] Custom AVIOContext makes no sense and will be ignored with AVFMT_NOFILE format.

mmm maybe the connection to GDrive with the x264 codecs
Not sure.

(2022-01-13, 16:18)EloyFarina Wrote: [ -> ]Logs

Debugging was enabled too late. Restart Kodi/LibreELEC was enabling debugging.
If you were fumbling with bluetooth settings/things, please don't for a moment.

(2022-01-13, 16:25)EloyFarina Wrote: [ -> ]I think that this can be a clue:

You already provided a log link, please don't splatter log stuff into the forum.

Hi Klojum, thanks for reply
So, are those logs usefuls or not?
I have turned off bluetooth, so that should not be an issue.
Apologies for pasting partial logs. I wanted to remark that every time that I experienced the issue, those lines appears in the logs.
But why? I mean, that is the same movie that I player from the SSD or my PC through SMB without issues.

I found the root cause!!!
It is the Raspoberry Pi 4, disabling hardware acceleration with DRM PRIME fix the issue.
But of course, this is not recommended for playing 4k videos.