Jump to content

kryptonyte
Go to solution Solved by kryptonyte,

Recommended Posts

kryptonyte
Hi, over the last couple of weeks I have been receiving regular freezes/lagging whilst watching several TV Shows in a row with the "Play next video automatically" option enabled in the Settings -> Video -> Playback on Kodi.

 

I have always had this setting enabled as it is useful for my kids to automatically watch a few shows in a row without needing to manually start a new episode after the previous one concluded. Up until recently this setting has worked well and as intended without any issues for months.

 

Now randomly (albeit most of the time) after watching an episode or two, Kodi will freeze/become unrepsonsive. This occurs at the end of an episode as it tries to commence playing the next episode. Through trial and error I determined if you leave it long enough ie ~ 15 mins Kodi will eventually display an error on screen stating it failed to open the source file. Obviously this is not preferable and the only way to continue is forcefully close the frozen Kodi app, re-open and start play the next episode manually.

 

My setup:

 

Emby Linux Mono Version 3.1.47.0 Beta (running on Asustor AS 7010T x64 running latest v2.6.2 linux firmware)

Emby for Kodi Sync Queue on Emby Server version 1.0.6020.14567 (although I disabled this on the client for testing and the freezing seems to occur both with/without Fast Sync enabled)

Emby for Kodi Beta 2.2.12

SPMC Jarvis 16.3.0 (based on Kodi 16.1 for Android) (running on Nvidia Shield Android TV v3.2)

Vanilla SPMC install, running standard Confluence skin with only a couple of simple other addins: Oz Weather, HD Homerun & Multicam (view security cameras) plugins

Wired 1Gb ethernet network

(I have just tested and the problem occurs also occurs on the standard clean install of the App store version of Kodi 16.1 for Android on the same Nvidia Shield. So I am deducing that it is not a SPMC specific problem)

 

In the below log file, the episode I watched concluded around the 21:43:31 mark. Kodi then Lagged/froze/became unresponsive for ~ 15 mins and at the 22:01:17 mark Kodi finally displayed an error onscreen saying failed to open source for next episode.

 

Kodi/SPMC Log:


 

Thanks for your help and please let me know if you require any additional information.

Link to comment
Share on other sites

Angelblue05

You had major updates going on at the same time (from emby). Do you always have this many updates? Do you use nfo? Or perhaps the content is not properly identified on your server, causing your server to send updates over and over when it tries to identify the content? Let me know.

 

I'm fairly certain you experience that freeze simply because the add-on is busy processing all those updates and trying to query the path in real time from the server.

Edited by Angelblue05
Link to comment
Share on other sites

kryptonyte

Many thanks for your reply Angelblue.

 

Yes I do use NFO files.

 

I had assumed regular library updates like that were normal as it has always been that way since I setup Emby almost 12 months ago. My library contains ~ 1424 Movies & 241 TV Series, a full Library scan takes around 5 mins or so. I was running the full scan every hour to capture newly added content more regularly.

 

I've tweaked a couple more settings, reduced the library scans back to 6 hours, removed some plugins that update info such as Trakt, Timelord etc and initialised a full Metadata refresh.

 

I'll report back in a few days to see if these tweaks resolves the constant library updates and hence as you suggest may then resolve the "play next video automatically" video freezing.

 

Cheers

Link to comment
Share on other sites

Angelblue05

In my case, having the option to save image path within nfo enabled generated a lot of updates (especially when the refresh people task ran). You can try disabling it - emby dashboard > metadata > nfo settings. Keep me posted :)

Link to comment
Share on other sites

kryptonyte

Oh that is interesting. Many thanks! I also had that option enabled. I will disable it and see how that progresses too.

  • Like 1
Link to comment
Share on other sites

xnappo

I think we need to always show it if more than 10 items are being processed.

 

It is super annoying to have it flicker for just small updates.

Link to comment
Share on other sites

  • Solution
kryptonyte

Cheers for all the Devs that made the changes to Emby for Kodi to show the updates being displayed by default.

 

That is a feature that I personally had always enabled. Since my setup was always showing regular updates since I setup Emby over 12 months ago, I had always assumed that was the norm (perhaps a simple user such as my self should not make assumptions!).

 

I made the below changes, which dramatically reduced the amount of updates occurring within Kodi:

 

  • Under Metadata Manager, for each media source eg TV Shows, Movies etc I did a Metadata Refresh using "Replace all Media" (with my large library and an average speed internet connection this took a very long time!)
  • As per Angelblue05's recommendation, I disabled saving the image paths within NFO files via Admin -> Manage Server -> Metadata -> NFO Settings and deselected "Save image paths within NFO files"
  • Set "Scan Media Library" Scheduled Task back to 6 hours, rather than hourly as I had previously set it to
  • Whilst testing I also disabled all plugins such as Trakt, Time Lord etc

Doing the above dramatically reduced the amount of items being regularly updated & reduced the time for a complete "Scan Media Library" by a couple of minutes. It also appeared to fix the problem as per above of "Play next video automatically" causing freezing/lagging.

 

However, I noticed items that I was not watching/changing such as older TV Shows/Movies were still being updated. After a bit more testing, I believe it might be Sonarr and CouchPotato creating NFO metadata. Sonarr especially will regularly update NFO files for new seasons, content etc for existing shows. I have now disabled metadata creation in both Sonarr and CouchPotato and see how it goes.

 

My main issue is now resolved.

 

So as usual many thanks for the assistance, especially for AngelBlue05 for your tireless dev work and for taking the time to troubleshoot all of our emby issues. Even if they are often caused by us end users!

  • Like 1
Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
×
×
  • Create New...