Jump to content

embyforkodi (next-gen) 11.X.X support


Recommended Posts

jonomite
Posted
21 minutes ago, quickmic said:

Sounds your EMby server is busy/overloaded and I can see the server was scanning when the stream stalled.

Increasing Kodi's video cache will also help.

Interesting. I'd be curious to know more about this - where in the log does it show that? I recently build a new (much, much upgraded) server so it is surprising to hear that it is overloaded. 

Also, I'm curious for your thoughts on which Kodi cache settings to modify.

https://kodi.wiki/view/Settings/Services/Caching

There are quite a few settings. Do you recommend changing all of them? 

 

quickmic
Posted (edited)
50 minutes ago, jonomite said:

I recently build a new (much, much upgraded) server so it is surprising to hear that it is overloaded.

 

Good server hardware helps but for large libraries etc. scans can still "overload" the server (actually the Emby application becomes unresponsive for http requests for a couple of seconds).

Even on my Dell server this can happen on long running (sqlite) database queries on the server.

If you think it's not a server issue, might be a network issue or Kodi bug. Impossible to say remotely, surly not a plugin issue.

-> Probably IPV6 issue? You could also try disable it.

Kodi cache helps if you buffer more data into the ram, or as I do using the complete disk.

Caching everything might wear out your disk! Read the Kodi docu.

btw, Cache settings are not respected for trans-coding streams (hls streams)

image.png.8c25d81351ab8e9b005ee0e56ab88460.png

 

Quote

Interesting. I'd be curious to know more about this - where in the log does it show that?

Cause Emby server is sending realtime updates via websocket to Kodi and I assume you didn't modify metadata manually?

EMBY.hooks.websocket: [ LibraryChanged ]

 

Kodi log reports:

2025-05-17 19:59:41.325 T:13085   error <general>: CCurlFile::CReadState::FillBuffer - (0x78d06520) Failed: Timeout was reached(28)
2025-05-17 19:59:41.325 T:13085 warning <general>: CCurlFile::CReadState::FillBuffer - (0x78d06520) Reconnect, (re)try 1

Kodi tries to pull data, and usually a "(re)try)" works but if it's too much this happens ->

CVideoPlayerAudio::Process - stream stalled

 

 

Edited by quickmic
quickmic
Posted
On 4/25/2025 at 2:09 PM, kalg said:

 Do you use embys live TV with their TV guide for epg ?? If so when you highlight a show in the TV guide you get art image of a show , with me now? What I'm saying is that isn't getting imported to Kodi IE no EPG images of the TV guide that emby has  . Are you not familiar with EPG guide images ??  First image is on emby server TV guide I'm highlighting Dracula then I clicked it to show you next screen see cover art. Now third screen is Kodi with your plugin and enabled live TV sync but  cover art not imported into IPTV simple client 

IMG20250425131521.jpg

IMG20250425131532.jpg

IMG20250425131617.jpg

I tried to add images to my epg file, but Emby does not support that.

 

I use M3U source with XMLTV epg on Emby server, which one do you use?

quickmic
Posted (edited)
1 hour ago, kalg said:

emby's own tv guide data

I"m not sure what you are talking about:

The only source I can add under "Guide Data Sources" is XmlTv as I have no other plugins installed.

btw. "Emby Guide Data" is for US, Canada and UK only. I'm not based there.

livetv1.png

Edited by quickmic
Posted

Oh thought it was for many countries because you have to select the country lots . Any how that's the guide I'm using, by default, just tried it with the xmltv using epg123 from green button forum and that does the same, so looks like it wont work thanks for the time you tried 

jonomite
Posted
10 hours ago, quickmic said:

Good server hardware helps but for large libraries etc. scans can still "overload" the server (actually the Emby application becomes unresponsive for http requests for a couple of seconds).

Even on my Dell server this can happen on long running (sqlite) database queries on the server.

If you think it's not a server issue, might be a network issue or Kodi bug. Impossible to say remotely, surly not a plugin issue.

-> Probably IPV6 issue? You could also try disable it.

Kodi cache helps if you buffer more data into the ram, or as I do using the complete disk.

Caching everything might wear out your disk! Read the Kodi docu.

btw, Cache settings are not respected for trans-coding streams (hls streams)

image.png.8c25d81351ab8e9b005ee0e56ab88460.png

 

Cause Emby server is sending realtime updates via websocket to Kodi and I assume you didn't modify metadata manually?

EMBY.hooks.websocket: [ LibraryChanged ]

 

Kodi log reports:

2025-05-17 19:59:41.325 T:13085   error <general>: CCurlFile::CReadState::FillBuffer - (0x78d06520) Failed: Timeout was reached(28)
2025-05-17 19:59:41.325 T:13085 warning <general>: CCurlFile::CReadState::FillBuffer - (0x78d06520) Reconnect, (re)try 1

Kodi tries to pull data, and usually a "(re)try)" works but if it's too much this happens ->

CVideoPlayerAudio::Process - stream stalled

 

 

Thank you for your insights. I will try changing some of the cache settings.

Correct that I am not editing any metadata manually. Do you know why that might be showing up in the log? Is there anything I can do reduce that from happening? 

quickmic
Posted
51 minutes ago, jonomite said:

Thank you for your insights. I will try changing some of the cache settings.

Correct that I am not editing any metadata manually. Do you know why that might be showing up in the log? Is there anything I can do reduce that from happening? 

You need to check what kind of tasks are running on the server. Probably enable debug log on Emby server for better insights.

supermood
Posted (edited)

hi @quickmiclong time no hear, that means your addon ROCKS!!! thanks again!! 

one question. only if that can be related to my error of installing the latest version before realizing that I'm of course not on Emby 4.9 beta but on 4.8. so I changed back to v29. 

since then, but can be unrelated, I have a constant pop up that my tmdb helper addon is not working / crashing. message says tmdb helper error and log is empty 

I can't see any difference in the menu, I think it's working. but the pop up is annoying. 

happy day! 

Edited by supermood
  • Like 1
quickmic
Posted
11 hours ago, supermood said:

I have a constant pop up that my tmdb helper addon is not working / crashing. message says tmdb helper error and log is empty

There should be something in the kodi.log. You could enable the debug log in Kodi for more information. Usually plugin issues are reported on startup, but might be also related to skin.

Can you force the issue? Also I would try to reinstall the helper or update the helper is a newer version is available.

quickmic
Posted
11 hours ago, supermood said:

before realizing that I'm of course not on Emby 4.9 beta but on 4.8. so I changed back to v29.

I know, it's a bit confusing at the moment. Next 12.X version will support both Kodi (21 and 22) versions. I'll also check both Emby servers.

dapharsyde
Posted

i just upgraded to emby 4.9.1 beta, with plugin 11.2.29 - it seems that dynamic node folder view is not working - it shows an empty folder with ".." - here is some debug info, let me know if a more complete log is required

2025-05-30 03:40:25.989 T:26312   debug <general>: EMBY.hooks.webservice: THREAD: --->[ worker_Query ]
2025-05-30 03:40:25.989 T:26312   debug <general>: EMBY.hooks.webservice: Incoming Data: EVENT service;7;?mode=browse&id=7075&parentid=7075&libraryid=7075&content=Folder&server=[REDACTED]&query=Folder;resume:false
2025-05-30 03:40:25.989 T:26312    info <general>: EMBY.helper.pluginmenu: Browse: Id: 7075 / Query: Folder / ParentId: 7075 / LibraryId: 7075 / Content: Folder / WindowId: 10025 / ServerId: [REDACTED] / ContentSupported: 
2025-05-30 03:40:25.989 T:26312   debug <general>: EMBY.helper.pluginmenu: WindowIdCheck: False
2025-05-30 03:40:25.989 T:31988   debug <general>: EMBY.emby.api: THREAD: --->[ load Items ]
2025-05-30 03:40:25.995 T:31988   debug <general>: EMBY.emby.api: THREAD: ---<[ load Items ] Limit: 100000 / ReceivedItems: 2
2025-05-30 03:40:25.996 T:32272   debug <general>: EMBY.emby.api: THREAD: --->[ load Items ]
2025-05-30 03:40:26.001 T:32272   debug <general>: EMBY.emby.api: THREAD: ---<[ load Items ] Limit: 5000 / ReceivedItems: 2
2025-05-30 03:40:26.002 T:31960   debug <general>: EMBY.emby.api: THREAD: --->[ load Items ]
2025-05-30 03:40:26.007 T:31960   debug <general>: EMBY.emby.api: THREAD: ---<[ load Items ] Limit: 5000 / ReceivedItems: 2
2025-05-30 03:40:26.008 T:15460   debug <general>: EMBY.emby.api: THREAD: --->[ load Items ]
2025-05-30 03:40:26.013 T:15460   debug <general>: EMBY.emby.api: THREAD: ---<[ load Items ] Limit: 5000 / ReceivedItems: 2
2025-05-30 03:40:26.014 T:22556   debug <general>: EMBY.emby.api: THREAD: --->[ load Items ]
2025-05-30 03:40:26.021 T:22556   debug <general>: EMBY.emby.api: THREAD: ---<[ load Items ] Limit: 1000 / ReceivedItems: 2
2025-05-30 03:40:26.022 T:23816   debug <general>: EMBY.emby.api: THREAD: --->[ load Items ]
2025-05-30 03:40:26.027 T:23816   debug <general>: EMBY.emby.api: THREAD: ---<[ load Items ] Limit: 1000 / ReceivedItems: 2
2025-05-30 03:40:26.028 T:21844   debug <general>: EMBY.emby.api: THREAD: --->[ load Items ]
2025-05-30 03:40:26.035 T:21844   debug <general>: EMBY.emby.api: THREAD: ---<[ load Items ] Limit: 10000 / ReceivedItems: 2
2025-05-30 03:40:26.035 T:22232   debug <general>: EMBY.emby.api: THREAD: --->[ load Items ]
2025-05-30 03:40:26.042 T:22232   debug <general>: EMBY.emby.api: THREAD: ---<[ load Items ] Limit: 5000 / ReceivedItems: 2
2025-05-30 03:40:26.042 T:25724   debug <general>: EMBY.emby.api: THREAD: --->[ load Items ]
2025-05-30 03:40:26.048 T:25724   debug <general>: EMBY.emby.api: THREAD: ---<[ load Items ] Limit: 5000 / ReceivedItems: 2
2025-05-30 03:40:26.048 T:31768   debug <general>: EMBY.emby.api: THREAD: --->[ load Items ]
2025-05-30 03:40:26.054 T:31768   debug <general>: EMBY.emby.api: THREAD: ---<[ load Items ] Limit: 20000 / ReceivedItems: 2
2025-05-30 03:40:26.055 T:29444   debug <general>: EMBY.emby.api: THREAD: --->[ load Items ]
2025-05-30 03:40:26.057 T:31656   debug <general>: ------ Window Init (DialogBusy.xml) ------
2025-05-30 03:40:26.059 T:31656   debug <general>: ------ Window Deinit (DialogBusy.xml) ------
2025-05-30 03:40:26.061 T:29444   debug <general>: EMBY.emby.api: THREAD: ---<[ load Items ] Limit: 5000 / ReceivedItems: 2
2025-05-30 03:40:26.061 T:27456   debug <general>: EMBY.emby.api: THREAD: --->[ load Items ]
2025-05-30 03:40:26.067 T:27456   debug <general>: EMBY.emby.api: THREAD: ---<[ load Items ] Limit: 1000 / ReceivedItems: 2
2025-05-30 03:40:26.067 T:29752   debug <general>: EMBY.emby.api: THREAD: --->[ load Items ]
2025-05-30 03:40:26.073 T:29752   debug <general>: EMBY.emby.api: THREAD: ---<[ load Items ] Limit: 5000 / ReceivedItems: 2
2025-05-30 03:40:26.073 T:7988    debug <general>: EMBY.emby.api: THREAD: --->[ load Items ]
2025-05-30 03:40:26.079 T:7988    debug <general>: EMBY.emby.api: THREAD: ---<[ load Items ] Limit: 1000 / ReceivedItems: 2
2025-05-30 03:40:26.080 T:17072   debug <general>: EMBY.emby.api: THREAD: --->[ load Item by Ids ]
2025-05-30 03:40:26.088 T:17072   debug <general>: EMBY.emby.api: THREAD: ---<[ load Item by Ids ]
2025-05-30 03:40:26.088 T:26312   debug <general>: EMBY.helper.pluginmenu: Dynamic nodes: addDirectoryItems
2025-05-30 03:40:26.088 T:26312   debug <general>: EMBY.helper.pluginmenu: Dynamic nodes: addSortMethod Folder / Folder
2025-05-30 03:40:26.088 T:26312   debug <general>: EMBY.helper.pluginmenu: Dynamic nodes: endOfDirectory
2025-05-30 03:40:26.088 T:26312   debug <general>: EMBY.hooks.webservice: THREAD: ---<[ worker_Query ] event browse
2025-05-30 03:40:26.088 T:584     debug <general>: CPythonInvoker(19, C:\Users\DaPharSyde\AppData\Roaming\Kodi\addons\plugin.service.emby-next-gen\service.py): script successfully run
2025-05-30 03:40:26.088 T:584     debug <general>: CPythonInvoker::onExecutionDone(19, C:\Users\DaPharSyde\AppData\Roaming\Kodi\addons\plugin.service.emby-next-gen\service.py)
2025-05-30 03:40:26.089 T:29836   debug <general>: Thread waiting 29836 terminating
2025-05-30 03:40:26.090 T:27608   debug <general>: Thread BackgroundLoader start, auto delete: false
2025-05-30 03:40:26.091 T:27608   debug <general>: Thread BackgroundLoader 27608 terminating
2025-05-30 03:40:26.091 T:31656   debug <general>: CDirectoryProvider[plugin://script.embuary.helper/?info=jumptoletter&showall=false&reload=0]: refreshing..
2025-05-30 03:40:26.091 T:25800   debug <general>: CScriptRunner: running add-on script Embuary Helper('plugin://script.embuary.helper/', '8', '?info=jumptoletter&showall=false&reload=0')
2025-05-30 03:40:26.091 T:1920    debug <general>: Thread LanguageInvoker start, auto delete: false
2025-05-30 03:40:26.092 T:1920    debug <general>: initializing python engine.
2025-05-30 03:40:26.092 T:1920    debug <general>: CPythonInvoker(20, C:\Users\DaPharSyde\AppData\Roaming\Kodi\addons\script.embuary.helper\plugin.py): start processing
2025-05-30 03:40:26.149 T:584     debug <general>: Python interpreter stopped
2025-05-30 03:40:26.149 T:584     debug <general>: Thread LanguageInvoker 584 terminating

 

  • Like 1
quickmic
Posted
10 minutes ago, dapharsyde said:

i just upgraded to emby 4.9.1 beta, with plugin 11.2.29 - it seems that dynamic node folder view is not working - it shows an empty folder with ".." - here is some debug info, let me know if a more complete log is required

2025-05-30 03:40:25.989 T:26312   debug <general>: EMBY.hooks.webservice: THREAD: --->[ worker_Query ]
2025-05-30 03:40:25.989 T:26312   debug <general>: EMBY.hooks.webservice: Incoming Data: EVENT service;7;?mode=browse&id=7075&parentid=7075&libraryid=7075&content=Folder&server=[REDACTED]&query=Folder;resume:false
2025-05-30 03:40:25.989 T:26312    info <general>: EMBY.helper.pluginmenu: Browse: Id: 7075 / Query: Folder / ParentId: 7075 / LibraryId: 7075 / Content: Folder / WindowId: 10025 / ServerId: [REDACTED] / ContentSupported: 
2025-05-30 03:40:25.989 T:26312   debug <general>: EMBY.helper.pluginmenu: WindowIdCheck: False
2025-05-30 03:40:25.989 T:31988   debug <general>: EMBY.emby.api: THREAD: --->[ load Items ]
2025-05-30 03:40:25.995 T:31988   debug <general>: EMBY.emby.api: THREAD: ---<[ load Items ] Limit: 100000 / ReceivedItems: 2
2025-05-30 03:40:25.996 T:32272   debug <general>: EMBY.emby.api: THREAD: --->[ load Items ]
2025-05-30 03:40:26.001 T:32272   debug <general>: EMBY.emby.api: THREAD: ---<[ load Items ] Limit: 5000 / ReceivedItems: 2
2025-05-30 03:40:26.002 T:31960   debug <general>: EMBY.emby.api: THREAD: --->[ load Items ]
2025-05-30 03:40:26.007 T:31960   debug <general>: EMBY.emby.api: THREAD: ---<[ load Items ] Limit: 5000 / ReceivedItems: 2
2025-05-30 03:40:26.008 T:15460   debug <general>: EMBY.emby.api: THREAD: --->[ load Items ]
2025-05-30 03:40:26.013 T:15460   debug <general>: EMBY.emby.api: THREAD: ---<[ load Items ] Limit: 5000 / ReceivedItems: 2
2025-05-30 03:40:26.014 T:22556   debug <general>: EMBY.emby.api: THREAD: --->[ load Items ]
2025-05-30 03:40:26.021 T:22556   debug <general>: EMBY.emby.api: THREAD: ---<[ load Items ] Limit: 1000 / ReceivedItems: 2
2025-05-30 03:40:26.022 T:23816   debug <general>: EMBY.emby.api: THREAD: --->[ load Items ]
2025-05-30 03:40:26.027 T:23816   debug <general>: EMBY.emby.api: THREAD: ---<[ load Items ] Limit: 1000 / ReceivedItems: 2
2025-05-30 03:40:26.028 T:21844   debug <general>: EMBY.emby.api: THREAD: --->[ load Items ]
2025-05-30 03:40:26.035 T:21844   debug <general>: EMBY.emby.api: THREAD: ---<[ load Items ] Limit: 10000 / ReceivedItems: 2
2025-05-30 03:40:26.035 T:22232   debug <general>: EMBY.emby.api: THREAD: --->[ load Items ]
2025-05-30 03:40:26.042 T:22232   debug <general>: EMBY.emby.api: THREAD: ---<[ load Items ] Limit: 5000 / ReceivedItems: 2
2025-05-30 03:40:26.042 T:25724   debug <general>: EMBY.emby.api: THREAD: --->[ load Items ]
2025-05-30 03:40:26.048 T:25724   debug <general>: EMBY.emby.api: THREAD: ---<[ load Items ] Limit: 5000 / ReceivedItems: 2
2025-05-30 03:40:26.048 T:31768   debug <general>: EMBY.emby.api: THREAD: --->[ load Items ]
2025-05-30 03:40:26.054 T:31768   debug <general>: EMBY.emby.api: THREAD: ---<[ load Items ] Limit: 20000 / ReceivedItems: 2
2025-05-30 03:40:26.055 T:29444   debug <general>: EMBY.emby.api: THREAD: --->[ load Items ]
2025-05-30 03:40:26.057 T:31656   debug <general>: ------ Window Init (DialogBusy.xml) ------
2025-05-30 03:40:26.059 T:31656   debug <general>: ------ Window Deinit (DialogBusy.xml) ------
2025-05-30 03:40:26.061 T:29444   debug <general>: EMBY.emby.api: THREAD: ---<[ load Items ] Limit: 5000 / ReceivedItems: 2
2025-05-30 03:40:26.061 T:27456   debug <general>: EMBY.emby.api: THREAD: --->[ load Items ]
2025-05-30 03:40:26.067 T:27456   debug <general>: EMBY.emby.api: THREAD: ---<[ load Items ] Limit: 1000 / ReceivedItems: 2
2025-05-30 03:40:26.067 T:29752   debug <general>: EMBY.emby.api: THREAD: --->[ load Items ]
2025-05-30 03:40:26.073 T:29752   debug <general>: EMBY.emby.api: THREAD: ---<[ load Items ] Limit: 5000 / ReceivedItems: 2
2025-05-30 03:40:26.073 T:7988    debug <general>: EMBY.emby.api: THREAD: --->[ load Items ]
2025-05-30 03:40:26.079 T:7988    debug <general>: EMBY.emby.api: THREAD: ---<[ load Items ] Limit: 1000 / ReceivedItems: 2
2025-05-30 03:40:26.080 T:17072   debug <general>: EMBY.emby.api: THREAD: --->[ load Item by Ids ]
2025-05-30 03:40:26.088 T:17072   debug <general>: EMBY.emby.api: THREAD: ---<[ load Item by Ids ]
2025-05-30 03:40:26.088 T:26312   debug <general>: EMBY.helper.pluginmenu: Dynamic nodes: addDirectoryItems
2025-05-30 03:40:26.088 T:26312   debug <general>: EMBY.helper.pluginmenu: Dynamic nodes: addSortMethod Folder / Folder
2025-05-30 03:40:26.088 T:26312   debug <general>: EMBY.helper.pluginmenu: Dynamic nodes: endOfDirectory
2025-05-30 03:40:26.088 T:26312   debug <general>: EMBY.hooks.webservice: THREAD: ---<[ worker_Query ] event browse
2025-05-30 03:40:26.088 T:584     debug <general>: CPythonInvoker(19, C:\Users\DaPharSyde\AppData\Roaming\Kodi\addons\plugin.service.emby-next-gen\service.py): script successfully run
2025-05-30 03:40:26.088 T:584     debug <general>: CPythonInvoker::onExecutionDone(19, C:\Users\DaPharSyde\AppData\Roaming\Kodi\addons\plugin.service.emby-next-gen\service.py)
2025-05-30 03:40:26.089 T:29836   debug <general>: Thread waiting 29836 terminating
2025-05-30 03:40:26.090 T:27608   debug <general>: Thread BackgroundLoader start, auto delete: false
2025-05-30 03:40:26.091 T:27608   debug <general>: Thread BackgroundLoader 27608 terminating
2025-05-30 03:40:26.091 T:31656   debug <general>: CDirectoryProvider[plugin://script.embuary.helper/?info=jumptoletter&showall=false&reload=0]: refreshing..
2025-05-30 03:40:26.091 T:25800   debug <general>: CScriptRunner: running add-on script Embuary Helper('plugin://script.embuary.helper/', '8', '?info=jumptoletter&showall=false&reload=0')
2025-05-30 03:40:26.091 T:1920    debug <general>: Thread LanguageInvoker start, auto delete: false
2025-05-30 03:40:26.092 T:1920    debug <general>: initializing python engine.
2025-05-30 03:40:26.092 T:1920    debug <general>: CPythonInvoker(20, C:\Users\DaPharSyde\AppData\Roaming\Kodi\addons\script.embuary.helper\plugin.py): start processing
2025-05-30 03:40:26.149 T:584     debug <general>: Python interpreter stopped
2025-05-30 03:40:26.149 T:584     debug <general>: Thread LanguageInvoker 584 terminating

 

Confirmed, will be fixed in next version.

  • 2 weeks later...
whisperer
Posted

Hi, I set the "Max resume percentage" for my TV library to 85% (default is 90%), but Kodi doesn't seem to use this setting.
Based on my testing, it always uses 92%, only marks it watched if you play past that..

Not sure if this is a Kodi or plugin thing

quickmic
Posted (edited)
1 hour ago, whisperer said:

Hi, I set the "Max resume percentage" for my TV library to 85% (default is 90%), but Kodi doesn't seem to use this setting.
Based on my testing, it always uses 92%, only marks it watched if you play past that..

Not sure if this is a Kodi or plugin thing

A Kodi thing, it's globally adjustable in https://kodi.wiki/view/Advancedsettings.xml

-> playcountminimumpercent, ignorepercentatend, ignoresecondsatstart

I already had a poc totally disabling the resumepoints in Kodi, which means the resumepoints must be set by the plugin for every content (even not Emby content) to make it work.

It wasn't too reliable and I removed it (also needed admin previlegies on Emby to read the library settings), however, it's on the long term Agenda but needs a lot of work.

Edited by quickmic
  • Like 1
  • 2 months later...
Posted (edited)

Hi Mic,

I recently investigating some problems on my installation. I've tried first 12xx latest beta but fallen back to 11xx.

I've an Emby server with well sorted SMB shares (movies, TV shows, etc.) so I opted for Native mode with path substitution. The 11xx addon writes an advancedsettings.xml to the kodi/userdata folder with the following content.

Quote

<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<advancedsettings>

    <network>
        <disablehttp2>true</disablehttp2>
        <curlclienttimeout>5</curlclienttimeout>
    </network>
    <pathsubstitution>
        <substitute>
            <from>/emby_addon_mode/</from>
            <to>http://127.0.0.1:57342/|redirect-limit=1000</to>
        </substitute>
    </pathsubstitution>
</advancedsettings>

 

It seems to me not coherent with native mode and path substitution. Is it all right this way?

Edited by karmantyu
quickmic
Posted
14 hours ago, karmantyu said:

Hi Mic,

I recently investigating some problems on my installation. I've tried first 12xx latest beta but fallen back to 11xx.

I've an Emby server with well sorted SMB shares (movies, TV shows, etc.) so I opted for Native mode with path substitution. The 11xx addon writes an advancedsettings.xml to the kodi/userdata folder with the following content.

It seems to me not coherent with native mode and path substitution. Is it all right this way?

The path substitution is not used in native mode, so it doesn't matter.

  • Like 1
e123enitan
Posted

Hi pls I have issue  when I rebuild my LE, TV show scraping was fine, but the movies did not.

Any solution   

Log

quickmic
Posted
10 hours ago, e123enitan said:

Hi pls I have issue  when I rebuild my LE, TV show scraping was fine, but the movies did not.

Any solution   

Log

Because you use "22.0-ALPHA1". plugin 11.X versions are not compatible, you must update to 12.X or downgrade Kodi to stable version.

e123enitan
Posted
1 hour ago, quickmic said:

Because you use "22.0-ALPHA1". plugin 11.X versions are not compatible, you must update to 12.X or downgrade Kodi to stable version.

the reason why  i am on 22 is live Tv on LE flickers when changing channel on LE 20 and 21 the issue has now been resolved in 23

I  loaded 12.2.1 every thing is fine 

Thanks

 

  • Like 1
e123enitan
Posted

I have a question Emby for Kodi Next Gen is under Type as services, therefore it did not displayed under video > addon in Kodi, also for my Skin Titan is not showing 

since its coded as emby video addon -next-gen therefore all my skin setting for emby4kodi are messed up.

any suggestions 

Thanks

quickmic
Posted (edited)
2 hours ago, e123enitan said:

I have a question Emby for Kodi Next Gen is under Type as services, therefore it did not displayed under video > addon in Kodi, also for my Skin Titan is not showing 

since its coded as emby video addon -next-gen therefore all my skin setting for emby4kodi are messed up.

any suggestions 

Thanks

Install the helper addons.

https://kodi.emby.tv/Public testing/emby-for-kodi-next-gen-11X/helpers/plugin.video.emby-next-gen-10.1.2.zip

https://kodi.emby.tv/Public testing/emby-for-kodi-next-gen-11X/helpers/plugin.audio.emby-next-gen-10.1.2.zip

https://kodi.emby.tv/Public testing/emby-for-kodi-next-gen-11X/helpers/plugin.image.emby-next-gen-10.1.2.zip

Edited by quickmic
e123enitan
Posted
On 24/08/2024 at 14:23, quickmic said:

Ill check that.

Thanks everything is back to normal 

e123enitan
Posted

Hi I have an issue with movie playlist when I click on movie section to watch it will hanged for a very long period before movies are displayed 

I am not sure what could be the issue, on the log llist there are several warnings lines, errors etc. could pls advise which of thihttps://paste.kodi.tv/iyevokeyads error may have caused the hanging and what need to be done to fixed issue

 

 

https://paste.kodi.tv/iyevokeyad

Posted (edited)
2 hours ago, e123enitan said:

Hi I have an issue with movie playlist when I click on movie section to watch it will hanged for a very long period before movies are displayed 

I am not sure what could be the issue, on the log llist there are several warnings lines, errors etc. could pls advise which of thihttps://paste.kodi.tv/iyevokeyads error may have caused the hanging and what need to be done to fixed issue

 

 

https://paste.kodi.tv/iyevokeyad

The log is absolutely clean, I guess some Kodi process is scanning. Can you try to switch to default skin and see what happens?

You could also send me debug log via PM, don't post debug logs in public. Regular logs are fine to share.

Edited by quickmic

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...