Emby 4.8.0.26 - E4K Shows All Content as Unwatched

[DarWun 229]

After updating to Emby 4.8.0.26 on my Synology NAS I had issues with playback of a number of episodes using E4K installed on my rpi4. I did a database reset in E4K 7.x hoping that would fix the issue. After doing so all previously watched content is showing up as unwatched even though Emby shows the content as watched. I updated to E4K 8.x and reset the database. The result is the same. 

Kodi Log attached with scan from after updating to E4K 8.x.

kodi.log

[quickmic 1128]

9 hours ago, DarWun said:

After updating to Emby 4.8.0.26 on my Synology NAS I had issues with playback of a number of episodes using E4K installed on my rpi4. I did a database reset in E4K 7.x hoping that would fix the issue. After doing so all previously watched content is showing up as unwatched even though Emby shows the content as watched. I updated to E4K 8.x and reset the database. The result is the same. 

Kodi Log attached with scan from after updating to E4K 8.x.

kodi.log 1.87 MB · 1 download

Seems something changed in Emby server's API. The question, was it changed on purpose or is it a bug.

Currently I'm running .19 and cannot perform any tests with > .20

[Andy2k 57]

Same for music (the only i can sync atm;)), all previously played lists emty .

 

[quickmic 1128]

As soon as >.19 is stable enough for the plugin, I'll dig into that.

[DarWun 229]

3 hours ago, quickmic said:

As soon as >.19 is stable enough for the plugin, I'll dig into that.

@quickmicI'm a bit confused by this response. Other than the issue with having to reduce Paging to 1 for syncs, E4K has been perfectly stable for beta versions of Emby >.19. I agree it is is annoying that this wasn't fixed in 0.26. but it is not a showstopper by any means. Syncs take longer to complete. But they still complete.

Are you implying that you won't be doing anything to support E4K on post Emby 0.26 releases until the paging issue is resolved? I understand why you would take that position given that it was flagged to the developers long before 0.26 was released. But I would be lying to say I'm not disappointed.

Edited March 26 by DarWun

[quickmic 1128]

55 minutes ago, DarWun said:

@quickmicOther than the issue with having to reduce Paging to 1 for syncs, E4K has been perfectly stable for beta versions of Emby >.19. I agree it is is annoying that this wasn't fixed in 0.26. but it is not a showstopper by any means. Syncs take longer to complete. But they still complete.

This is an absolute showstopper for me and I think lot's of other people as well. Paging 1 may works for a smaller library, but mine would take a month or more to sync at this pace. Ero, useless.

Also I know users performing "manual" rollback to stable or <.20 for the same reason even if that's a hassle (Actually starting from scratch).

Quote

Are you implying that you won't be doing anything to support E4K on post Emby 0.26 releases until the paging issue is resolved? I understand why you would take that position given that it was flagged to the developers long before 0.26 was released. But I would be lying to say I'm not disappointed.

Frankly, I hope Luke releases are new version soon, addressing this issue. Otherwise I need to install a third test instance (yes, I already have 2 Emby servers running just for testing) and that's something I try to avoid.

If there is no fix for this bug (let's say in the next 1 or 2 weeks), I think I install a third one. But surly not in the next days.

Can you downgrade to .21? I know not possible from .21 to lower, but what about .26 to .21?

btw, The >.19 issue is also the reason why 7.X is not pushed to stable repo. Since January it's tagged as stable, but I don't wanna force people to init a resync. They would be all screwed.

Edited March 26 by quickmic

[DarWun 229]

3 hours ago, quickmic said:

Can you downgrade to .21? I know not possible from .21 to lower, but what about .26 to .21?

@quickmicYep, was able to roll back to 0.21 from 0.26. I know it is not recommended. But upon deleting library.db and rescanning, everything seems to be working okay...including E4K sync. I'll stick with it for now.

I have 32TB of data, and the time to sync with E4K paging settings at 1 was only about 20 minutes. So I can't imagine the size of your library that would lead to a month scan time. If I can help troubleshoot things for post .19 builds, let me know.

 

Edited March 27 by DarWun

[quickmic 1128]

6 hours ago, DarWun said:

I have 32TB of data, and the time to sync with E4K paging settings at 1 was only about 20 minutes.

 

Actually, I'm quite surprised that it "only" took 20 minutes. I have a lot of mp3 (recorded from a broadcaster), so the amount of items (roughly 500.000) is very high not the actual TBs (around 40).

Edited March 27 by quickmic

[minos 8]

i have the same problem, no watched / unwatched status get synct with .26 beta

[SwanStream 57]

Well, I gave the downgrade that seems to have worked for @DarWuna try and it bombed. Process: uninstall .26, install .21. Kill db in Kodi, start kodi. Emby seems fine with the downgrade, but the Kodi init sync only took a few minutes, shows a few thousand tv shows, but no episodes, etc.etc. I'm at paging val of 1, which worked before... Went back to .26 and I'm now back with an init sync that seems to be 'working'... but will take day(s). So I'm not sure if I'd recommend downgrading to anyone else in this particular purgatory... patience may be the best approach... I've been using Emby's client app in the interim... slow and definitely not as shiny as Kodi, but it's a working UI at the minute.

Edited March 27 by SwanStream

[DarWun 229]

25 minutes ago, SwanStream said:

Well, I gave the downgrade that seems to have worked for @DarWuna try and it bombed. Process: uninstall .26, install .21. Kill db in Kodi, start kodi. Emby seems fine with the downgrade, but the Kodi init sync only took a few minutes, shows a few thousand tv shows, but no episodes, etc.etc. I'm at paging val of 1, which worked before... Went back to .26 and I'm now back with an init sync that seems to be 'working'... but will take day(s). So I'm not sure if I'd recommend downgrading to anyone else in this particular purgatory... patience may be the best approach... I've been using Emby's client app in the interim... slow and definitely not as shiny as Kodi, but it's a working UI at the minute.

@SwanStreamI agree...patience is probably the best choice at this point. Just to clarify on my rollback process. I used the backup and restore plugin to capture playstates while still on 0.26. After reverting back to .21 I had to delete "library.db" and rescan my library. I then restored playstates using the backup and restore plugin. After doing that, everything was back to 0.21 status.

[DarWun 229]

17 hours ago, quickmic said:

Actually, I'm quite surprised that it "only" took 20 minutes. I have a lot of mp3 (recorded from a broadcaster), so the amount of items (roughly 500.000) is very high not the actual TBs (around 40).

@quickmicInteresting. Although I considered my library to be large (from my perspective), it only has about 8,000 media files. My content is almost entirely 25GB blu-ray rips of movies and tv shows. I just did a database rebuild to confirm my recollection of how long E4K took took to scan my movies and tv shows with paging set at 1. It was actually only about 7minutes, not 20minutes.

I can definitely understand the month long scan with 500,000 files.

[SwanStream 57]

@DarWunAh. Yeah an option for some, but for me a library scan just to catch new stuff takes a while already... with about 200TB and guess 300,000 items or so it takes a LONG time to do this on a small brain synology box.... I'll just wait. I can use the Emby app for now. cheers.

[quickmic 1128]

It's not only slower sync (in .26). btw, I'll review that again, maybe I can optimize some parts from plugin side.

The sync also crashes and get stuck in some cases. e.g. Multipart content crashes sync, Special feature content and maybe even trailers crashes as well (due to API changes in .26). This needs to be fixed, but you can send me a kodi.log for review.

Edited March 28 by quickmic

[SwanStream 57]

18 minutes ago, quickmic said:

This needs to be fixed, but you can send me a kodi.log for review.

Anyone in particular this is for @quickmic?

[quickmic 1128]

11 minutes ago, SwanStream said:

Anyone in particular this is for @quickmic?

While/after sync, but I'm quite sure you are affected by the crashes. If at some point the progress is stalled and not just slow, it indicates such a crash.

Edited March 28 by quickmic

[Mookdog 84]

Yeah I can confirm that it crashes out. Mainly on tv shows. Movies and stuff scan in fine. I reverted back to stable until this issue gets resolved. 

 

Mook

[SwanStream 57]

PM with logs of a small library init sync sent via pm...

or... would have been if I didn't get the message below. LMK when that's sorted and I'll try again....

"@quickmic cannot receive messages."

Or... were sent. Stay tuned for further updates live as they happen!

Edited March 28 by SwanStream

[quickmic 1128]

Update:

I tried a workaround for .26, but not gonna work.

You need to wait for .27 or downgrade.

[quickmic 1128]

1 hour ago, SwanStream said:

PM with logs of a small library init sync sent via pm...

or... would have been if I didn't get the message below. LMK when that's sorted and I'll try again....

"@quickmic cannot receive messages."

Or... were sent. Stay tuned for further updates live as they happen!

Thanks for the log, plugin seems to work fine. However I see after Season sync (next would be the episodes) an Error http 500 -> Internal server error.

Let's wait for .27 makes no sense to debug .26

Edited March 28 by quickmic

[SwanStream 57]

Oh... you think .27 will go in the right direction?

I'm doing what I can, as little as that is, to try and help the devs understand the problem. Patience not a problem,... as long as my TV still talks to me from time to time. Cheers.

[Luke 35274]

On 3/28/2023 at 12:50 PM, SwanStream said:

Oh... you think .27 will go in the right direction?

I'm doing what I can, as little as that is, to try and help the devs understand the problem. Patience not a problem,... as long as my TV still talks to me from time to time. Cheers.

HI, yes we are working hard on improving it. Thanks.

[Mookdog 84]

34 minutes ago, Luke said:

HI, yes we are working hard on improving it. Thanks.

We have faith in you @Lukeand @quickmic

 

Mook

[DarWun 229]

On 3/28/2023 at 12:44 PM, quickmic said:

Thanks for the log, plugin seems to work fine. However I see after Season sync (next would be the episodes) an Error http 500 -> Internal server error.

Let's wait for .27 makes no sense to debug .26

Hi @quickmic. I updated to Emby beta .27 and did a full database reset in E4K. I rescanned the libraries with the paging set to the default value of 70. As far as I can tell, there no longer seem to be issues with E4K crashing during the scan. The scan completed, and everything seems okay on that front. Hopefully others see the same.

Having said that, all previously watched content is still showing up as unwatched even though Emby shows the content as watched. This is with E4K 7.13.6. 

Kodi log attached.

kodi.log

[SwanStream 57]

Maybe @Lukecan comment on whether this issue is an intended api/db change or if this play state issue is unintended and to be put back... hate to see @quickmicdo work to fix that to see it undone in the next version.