+- Kodi Community Forum (https://forum.kodi.tv)
+-- Forum: Support (https://forum.kodi.tv/forumdisplay.php?fid=33)
+--- Forum: General Support (https://forum.kodi.tv/forumdisplay.php?fid=111)
+---- Forum: OS independent / Other (https://forum.kodi.tv/forumdisplay.php?fid=228)
+---- Thread: [split] Kodi v21 "Omega" Stable Release - Issues Discussions (/showthread.php?tid=376989)
RE: [split] Kodi v21 "Omega" Stable Release - Issues Discussions - vonson - 2024-04-14
Hello everyone,
I have a major issue since the v21 update, that is most of my movies won't playback any more (device is a fire stick 4k max). The movie starts, then after 5-10 seconds just stops, or if I try to skip ahead/back it just stops. It happens on movies that have played before as well as on new ones. It happens when starting them via library as well as when starting them from their folder.
From my experimenting I thought it would only affect files with 5.1 audio, not such with 2.0 audio. That is not the case, it just also happend with a 2.0 file.
I had a quick look into the log:
Read - Error( -1, 32, Broken pipe )
underflow: Error reading file - assuming eof
Process - eof reading from demuxer
This never happened before I updated to v21.
I even checked with my older fire stick which still has 20.0 installed, and the movies in question do play there without any problem. (Via folders, obviously the library won't work because the remote mariadb is already migrated/updated).
Is this a known issue? Has anyone else experienced this? Is there anything I can do to fix this?
EDIT:
(initially I thought it would only affect files with 5.1 audio, not 2.0. This is not the case. Paragraph above updated.)
RE: [split] Kodi v21 "Omega" Stable Release - Issues Discussions - teriyaki - 2024-04-16
Using Linux here and after updating to Kodi 21, we've experienced several segfaults when navigating the main menu via remote control. I didn't keep the logfiles due to size but one of the backtraces is here if anyone wants to look: https://paste.kodi.tv/doruqevaro.kodi
I've even compiled a fresh clone of git master this morning and the segfault already happened. The devs have been good about fixing stuff like this in the past fairly quickly. Hopefully that will hold true with this issue as well so I won't have to revert back to an older snapshot (kodi-r64669.git+da56f6222e) that didn't have this problem.
RE: [split] Kodi v21 "Omega" Stable Release - Issues Discussions - Frankus - 2024-04-25
I had the same problem and i fixed mine very easily by making sure the DATE and TIME was correct, since then I've have no problems very stable.
RE: [split] Kodi v21 "Omega" Stable Release - Issues Discussions - Neo1973 - 2024-04-26
(2024-04-16, 05:34)teriyaki Wrote: Using Linux here and after updating to Kodi 21, we've experienced several segfaults when navigating the main menu via remote control. I didn't keep the logfiles due to size but one of the backtraces is here if anyone wants to look: https://paste.kodi.tv/doruqevaro.kodiI've heard a few times from people having problems with Python 3.12. Looking at the stack trace, it might be this bug: https://github.com/python/cpython/issues/116510
RE: [split] Kodi v21 "Omega" Stable Release - Issues Discussions - Common Man - 2024-04-26
(2024-04-14, 17:16)vonson Wrote: Hello everyone,
I have a major issue since the v21 update, that is most of my movies won't playback any more (device is a fire stick 4k max). The movie starts, then after 5-10 seconds just stops, or if I try to skip ahead/back it just stops. It happens on movies that have played before as well as on new ones. It happens when starting them via library as well as when starting them from their folder.
From my experimenting I thought it would only affect files with 5.1 audio, not such with 2.0 audio. That is not the case, it just also happend with a 2.0 file.
I had a quick look into the log:
Read - Error( -1, 32, Broken pipe )
underflow: Error reading file - assuming eof
Process - eof reading from demuxer
This never happened before I updated to v21.
I even checked with my older fire stick which still has 20.0 installed, and the movies in question do play there without any problem. (Via folders, obviously the library won't work because the remote mariadb is already migrated/updated).
Is this a known issue? Has anyone else experienced this? Is there anything I can do to fix this?
EDIT:
(initially I thought it would only affect files with 5.1 audio, not 2.0. This is not the case. Paragraph above updated.)
Have the exact same problem when it updated to Omega on Google Chromecast 4k today. Files that played yesterday quit within a few seconds. Have no idea how to get logs off of Chromecast device.
But this is not for all files though. So far only one set of files so it may have to do with particular encoding common to those files rather than a file read issue.
Edited: Problem with all files. In some it just freezes. Using SMB share. Could be a SMB version problem.
Edited with more debugging:
Problem is with SRT subtitle files in the same folder and same name as video.
The subtitles are disabled but Kodi does seem to read the file. If I remove the SRT file the video plays just fine. So, the problem appears to be with reading the SRT file in conjunction with the video file at least in my case. This is a regression bug in Omega.
Have eliminated any network or access related issues using other devices.
RE: [split] Kodi v21 "Omega" Stable Release - Issues Discussions - kofii12345 - 2024-04-26
@Common Man you are right.
I have the same problem with movie stopping and tested anything (video codecs, video settings, smb settings, audio settings) but subtitles and if the movie doesn't have subtitles in folder it works. If it has (or you download in player new one to folder) the movie crash. Looking forward to fix. (I use Nvidia Shield Pro and read SMB file from Asus AC86U)
RE: [split] Kodi v21 "Omega" Stable Release - Issues Discussions - Common Man - 2024-04-27
Found another problem on the Google Chromecast. Different from the SRT issue discovered above.
When Kodi app is in use and Chromecast is shut off, the next time it is turned on, it comes back up with the skin home sceen (not splash screen). This is normal as the device is in hibernation and app is woken up if it hasn't been killed by Android.
BUT in Omega, when the above happens, the skin home screen appears but it is stuck on a Working... notification in the right bottom corner. Navigation doesn't work. A back key will dismiss the notification and app appears to be running but there is no audio. Videos freeze soon after if played.
Looks like the audio device initialization fails on waking up. This is a regression bug in Omega.
A work around is to explicitly exit the app and start it again (with the splash screen coming up). It works normally then.
RE: [split] Kodi v21 "Omega" Stable Release - Issues Discussions - Neo1973 - 2024-04-27
@Common Man This has already been reported in https://github.com/xbmc/xbmc/issues/24950 and a fix will be provided with 21.1. It's already in the Omega nightlies if don't want to wait for that.
RE: [split] Kodi v21 "Omega" Stable Release - Issues Discussions - chengtjaws - 2024-04-28
To fix the srt playback crash issue, go to settings -> services -> SMB client and change chunk size to 64 kb.
Default value was changed from 64 to 128 in v21 update, see https://github.com/xbmc/xbmc/issues/24961
Hope it helps, worked for me at least
RE: [split] Kodi v21 "Omega" Stable Release - Issues Discussions - Colabacardi - 2024-04-28
As i wrote before, i found a strange bug.
When I install Dutch language the category sets disappeared.
Switching back to English makes it visible again.
This happens in standard skin of course.
Could you please look into it, as i would like to use Kodi in Dutch.
Thanks.
RE: [split] Kodi v21 "Omega" Stable Release - Issues Discussions - Common Man - 2024-04-28
(2024-04-28, 01:21)chengtjaws Wrote: To fix the srt playback crash issue, go to settings -> services -> SMB client and change chunk size to 64 kb.
Default value was changed from 64 to 128 in v21 update, see https://github.com/xbmc/xbmc/issues/24961
Hope it helps, worked for me at least
Nice. This worked for me as well but the root cause bug still needs to be fixed. The above is a workaround. But may narrow down the search for the bug.
I found that this problem occurs only when Kodi tries to load the SRT file at video play start (because it has the same file name). But if the SRT file has a different file name and you manually select it via browse for subtitle after starting play, it works fine with either chunk size. So the128kb chunk size is not the root cause.
There may be a timing/timeout issue when it tries to fetch SRT file automatically at startup while also reading the video file which is not triggered when chunk size is 64kb but is when 128kb.
Hopefully that helps to find the bug.
RE: [split] Kodi v21 "Omega" Stable Release - Issues Discussions - Hitcher - 2024-04-28
(2024-04-28, 03:19)Colabacardi Wrote: As i wrote before, i found a strange bug.I installed Dutch language and Sets are still there:
When I install Dutch language the category sets disappeared.
Switching back to English makes it visible again.
This happens in standard skin of course.
Could you please look into it, as i would like to use Kodi in Dutch.
Thanks.
RE: [split] Kodi v21 "Omega" Stable Release - Issues Discussions - Colabacardi - 2024-04-28
Thanks for your reply, but that is instellen.
I mean sets.(Moviesets)
Thanks
RE: [split] Kodi v21 "Omega" Stable Release - Issues Discussions - Hitcher - 2024-04-28
That is Movie Sets.
RE: [split] Kodi v21 "Omega" Stable Release - Issues Discussions - Colabacardi - 2024-04-28
Ahh….now I understand.
This is so funny, t the translation of sets in Dutch is also sets.
Instellen means settings.
Same goes for fanart, in Dutch it’s also fanart and not lieverkunst.
So I’ll stick to English for now .
If I can be of any help in translation let me now.
Thanks for now.