(2021-11-03, 18:50)PatK Wrote: This thread is all over the place with users posting different issues, which need their own individual post with proper debug log to be suitably addressed. Bringing demands, drama and accusations to the thread helps zilch. There has been a developer in this thread and from what I see, is encountering argumentative nonsense with vast reasoning.
(2021-10-21, 17:54)SakuraKira Wrote: last working was 17.3 and many plugins won’t work anymore
Wonders of wonders... the move from python 2 to python 3 over 3 years caught everyone off guard smack. The ancient plugins may no longer be supported, suggest there is no shame in running 17.3
(2021-10-22, 21:24)SakuraKira Wrote: but sometimes it takes 30-40 files until it shows.
Random at the 30 to 40 file level, smacks of network or hardware, if the issue shows up on 4 units of the same user, it's likely a configuration, network, or o/s issue. Suggest Portable vanilla installation on one device with default everything, local source. Prove it's functionality, should there still be an issue, present a debug log from the occurrence with the symptoms, the debug log will be small.
Since I am the one initially starting this thread, I will once again answer even though the most is answered already.
I never accused the developer. But I think what I wrote was not read. And the attitude seems to be „Kodi is fine, it is you dumb user“ did not really help with finding the problem.
He also seemed a bit annoyed and also quick to judge and thin skinned. If anything he goes aggro quickly on people posting. Maybe he reads to many of the „not working“ posts which is not really good if you are a developer.
What I post is not meant to aggravate or to deny that Kodi 19 is great. It just is a problem which I am trying to solve.
As also mentioned a couple of times.
I ruled out the network-stack since it also occurs on local files.
It occurs on my newly made portable installation as well. And after a fresh windows install on a fresh Kodi with local files. With Kodi 19.3. But it takes a lot of loading files to get there. That is the problem with sporadically.
On 4 different machines and sporadically which means
Debug Log is pretty annoying to get. And the
Debug Log is huge since sometimes it occurs after trying 50-60files which all adds to the log respectively.
It seems to occur more often after a lot of new files have been added. Sometimes randomly many times on the same file. Sometimes weeks without problems.
After being accused of „not wanting to try out“ (while I already ruled out the most things since I already tried and described it previously), or beeing a layer 8 problem (even though vanilla install with fresh windows is foolproof in my eyes) and not posting debug logs correctly („even though I did but pastebin does not hold it for half a year) I lost interest to try and solve the problem lately. I have not much time at my hands so restarting the PC is ok for me now.
I think the problem does not really occur while starting a file but with closing and freeing up the AE sink, which happens every time you close the file or the audio changes. Which then cannot be used anymore and the old handle from Kodi is still open what also prevents it from closing.
It may occur more likely when the file takes some time though adding steps before starting like hdr switching or refreshrate-Change.
You can see this in the log btw. The line I also pointed out. Also adding up if you have AVR or soundbar in the middle or it just was coincidence.
It happened once to me while watching over my surface … this was on 19.1. so I am really sure this is not only a NUC Problem. While reading around and searching for AEInit:failed I came across people having a similar issue and no fix to be found.
I don’t use Linux on these machines because I also use other windows programs.
If I get time on my hand (having a house in building and an annoying job making this a bit of a problem for me) I will try the Linux version out.