2018-07-08, 23:42
(2018-07-08, 22:50)Alanon Wrote: @barev There's something going on with your file structure, that's why there are so many errors. Something in the way you have everything set up is clearly not to the add-ons' liking. For starters, you seem to run everything in portable mode, and I have no idea if all Kodi add-ons are able to work like that. Perhaps there's some particular procedure that would make things function properly.Thanks for the prompt reply! You're right I am running in portable mode, actually I've always used kodi like that for years and never had an issue ... actually if I switch the skin I do not get any errors.
The concrete error in the log seems to indicate you don't have an extrafanart filepath set up, which complicates things, given your portable use. Perhaps you had configured your library with a centralised artwork folder, and ExtendedInfo expects a path in the same tree, or something of the sort? As far as the memory leak warnings and other warnings that ExtendedInfo produces, they are just a consequence of the add-on itself.
Basically, if the errors are seriously impeding your usage, I would advise you to revise the way you have things set up, or see if there are any specific library artwork tweaks you can apply to lessen the number of errors, although by the sound of it, it appears to be a more serious issue. Regarding the warnings in the logs, we're all pretty much stuck with them until the add-on is updated.
The thing is the error is there for absolutely every addon I have installed, the extendedinfo was just an example. I have installed ArtWork Beef and it works, downloads all extended artwork and it is visible. I got this from their documentation:
https://rmrector.github.io/script.artwor...laceextra/
As far as I understand one way for extended art to work is to have a sub-folder in each library folder but then there is the option described in the ArtWork Beef docs. I do not know where is this option to set the extrafanart behaviour?
If you really think this is because of portable mode I can do a test clean install and provide a log but I get the same error ...