[mmortal03]

I PM'd you a test version of swmc for you to try.  GetServiceStatus has not been completely removed, because its main function is to tell kodi that swmc is online.  But all the other things that happen in the GetServiceStatus have been gutted.

Thanks! I've just done some testing with it, but, unfortunately, no change. I've just sent a donation; thanks for your time on this, and at least that rules it out. I'm getting the impression that the issue is not with the server software, but something with the client plugin or Kodi itself. I've got to do some further testing to confirm, but it seems as if the server doesn't even get the request for a while after the mouse click happens in the client, which makes me think it's something with the client. I'm going to try to get more precise with my system clocks to try to verify this.

Based on the assumption that the cause is with the client software, I decided to try some of the Kodi 18 nightlies (just a random sample of a few of them from the last few months), and I actually experienced *much* worse, just *horrible* unresponsiveness whenever the TV menu is interacted with, as long as "Store Resume/Watched status on server" is enabled. (Even just moving the mouse over the main TV menu, and not even clicking anything, caused Kodi to go *completely* unresponsive.) At least with 17.6 it's still mostly usable, *even with* that setting enabled. With that setting disabled, the menus no longer freeze up in 18, but video playback and stopping the video takes *much* longer than with 17.6.

[krustyreturns]

Thanks.  What/where is this setting "Store Resume/Watched status on server"?

[mmortal03]

It's in the PVR WMC Client add-on settings. Go to: My add-ons->PVR clients->PVR WMC Client->Configure button.

[krustyreturns]

Lol, right, I should probably know that.  But even with the resume setting enabled, the swmc log showed that it only took a fraction of a second for swmc to send back the resume time.  So I don't understand why that can make such a big lag.  Are you running the standard skins?  How many recordings do you have in the rec tv folder?  Could this be a network problem?

FYI: Pvr.wmc is going to have to get rev'd again for kodi18 to support some changes in kodi, which I so far have not done.  Maybe you should wait until that stuff is ironed out (although I don't know why the changes would make a difference for what you are seeing).

[mmortal03]

Lol, right, I should probably know that.  But even with the resume setting enabled, the swmc log showed that it only took a fraction of a second for swmc to send back the resume time.  So I don't understand why that can make such a big lag. 

Yeah, that's another reason why I don't think the cause is happening on the server side.

Are you running the standard skins?

Yep.

How many recordings do you have in the rec tv folder?

It does it even when there is just one recording. I just tested that right now to be sure.

Could this be a network problem?

I doubt it, as I've tried it when connected over Ethernet for the client. I tested it again just now to be sure. To be sure, the server is *always* connected over Ethernet. I've also disabled all of the UPnP devices that were popping up in the logs (initially the router's UPnP service was still enabled, but I've disabled that now, too). Keep in mind that HD videos play back fine, so the bandwidth is there. I mean, there could be some sort of weird latency issue, but I doubt that being the case over Ethernet.

Btw, another good way to produce the unresponsiveness is to click "Mark as Watched" or "Mark as Unwatched" in the context menu of the recording. The issue varies in length of time, and sometimes it doesn't occur at all, but it's easy to reproduce and happens enough times that fixing it would make the user experience *a lot* better. I'm going to do some more testing with the system clocks synced and looking at the logs and then I'll get back with you.

FYI: Pvr.wmc is going to have to get rev'd again for kodi18 to support some changes in kodi, which I so far have not done.  Maybe you should wait until that stuff is ironed out (although I don't know why the changes would make a difference for what you are seeing).

  
For sure. Just thought you should know that I gave it a shot and that it's gotten worse.

[krustyreturns]

Right.  I will try to get into it this week, if I need you test something I'll let you know.  In the meantime, let me know what else you find.