Luke 37062 Posted August 2, 2022 Share Posted August 2, 2022 Have you tried the new trakt plugin update that went out? Link to comment Share on other sites More sharing options...
ginjaninja 533 Posted August 3, 2022 Author Share Posted August 3, 2022 (edited) 18 hours ago, Luke said: Have you tried the new trakt plugin update that went out? 3.5.9.0? yes no change... original Case - Crazy Ex-Girlfriend - S04E18 - Yes, It's Really Us Singing - The Crazy Ex-Girlfriend Concert Special!.mkv Trakt and TVDB agree on the TVDBID for the show but not the index...end result this watched episode becomes unwatched after trakt import. Interestingly although i may be misremembering...the watched event on emby for this episode is now triggering a watched event on trakt (so that might be a step forward)...but in the Trakt>Emby direction the 'link' is not made and the episode is made unwatched on next import. Found a related case whilst testing - South Park - S00E45 - South Park - The Streaming Wars.mkv Trakt has no equivalent episode at index S00E45 and Trakt has no entry for this episode at any other index for the TVDBID..end result same...this watched episode becomes unwatched after trakt import For the original case if the trakt 'history read' can include TVDBIDs [*insert other provider ids as relevant], then perhaps before watched is flipped to unwatched, the trakt history should be checked for matching TVDBID? For the both cases before a watched is flipped to unwatched, can Trakt be queried for what indexes and tvdbids[*] Trakt is authorative for. If Trakt is not authorative then the unwatched import routine shouldnt flip watched to unwatched. If its not possible to query what indexes and tvdbids[*] trakt is authorative for then perhaps the plugin should have a tweak on the 'import watched' status routine so that it can not overwrite the emby history of a valid 'watched' event. Perhaps if there is not a workable outcome from the available data exchange then really the "import watched status" flag on the trakt plugin is only really valid for fresh builds / fresh databases to get 99% there and then tidy up the rest...but its not really suitable to keep switched on during normal use when you have multiple media servers, the user is trying to keep in sync? Edited August 3, 2022 by ginjaninja Link to comment Share on other sites More sharing options...
Luke 37062 Posted August 3, 2022 Share Posted August 3, 2022 Quote For the original case if the trakt 'history read' can include TVDBIDs [*insert other provider ids as relevant], then perhaps before watched is flipped to unwatched, the trakt history should be checked for matching TVDBID? The sync api's from trakt only contain the series ids and then a list of episode/season numbers. No unique identifiers for episodes unfortunately. Link to comment Share on other sites More sharing options...
ginjaninja 533 Posted August 3, 2022 Author Share Posted August 3, 2022 50 minutes ago, Luke said: The sync api's from trakt only contain the series ids and then a list of episode/season numbers. No unique identifiers for episodes unfortunately. i wonder wether the get collection endpoint can be used to confirm what trakt is authorative for. Ie limit the emby indexes for which the unwatched import can operate on to where the indexes in the trakt collection exist in the emby collection. Spoiler ...i dont know if its a practical endpoint to use for a full trakt import...but the get history endpoint does seem to support tmdb/tvdb ids for episodes alongside watched events.. ie return all watched [history] events from the beginning of time to the end of time [so that emby has all the tvdbids for the episodes/watched events] Link to comment Share on other sites More sharing options...
ginjaninja 533 Posted October 16, 2022 Author Share Posted October 16, 2022 Been experiencing a separate issue for a few months now and just realisd that sits probably caused by trakt plugin. Steps to reproduce: watch an episode 70% trakt playback progress gets stored as 70% decide you dont want to watch the end, so mark the episode watched in emby. (trakt playback progress is not updated) next scheduled import, episode gets put back on continued watching at 70% when a show is marked watched or unwatched in emby, the trakt playback progress for episode should be zeroed i think. Link to comment Share on other sites More sharing options...
Luke 37062 Posted October 31, 2022 Share Posted October 31, 2022 Quote when a show is marked watched or unwatched in emby, the trakt playback progress for episode should be zeroed i think. Hi, yes I think you're right. Thanks. Link to comment Share on other sites More sharing options...
Luke 37062 Posted November 19, 2022 Share Posted November 19, 2022 Hi, please try the 3.6.3 update to the Emby Trakt plugin and let us know how that compares. Thanks ! Link to comment Share on other sites More sharing options...
ginjaninja 533 Posted November 20, 2022 Author Share Posted November 20, 2022 (edited) On 19/11/2022 at 05:18, Luke said: Hi, please try the 3.6.3 update to the Emby Trakt plugin and let us know how that compares. Thanks ! no change unfortunately. The trakt playback progress is left unchanged when a half watched episode is marked played or unplayed in Emby Given that the pluggin is reliable at scrobbling played and unplayed events to trakt but neither trakt nor emby updates playback progress on trakt after an abrupt played/unplayed event "midprogress" yet, may a quick n dirty solution is a plugin option to not import "playback progress". This is a fairly nieche function for persons with multiple media servers who might start playback on one media server and continue media playback on another. Edited November 20, 2022 by ginjaninja Link to comment Share on other sites More sharing options...
Luke 37062 Posted November 20, 2022 Share Posted November 20, 2022 Ok yes that part isn't done yet but the update has lots of other improvements. Thanks. Link to comment Share on other sites More sharing options...
ginjaninja 533 Posted November 21, 2022 Author Share Posted November 21, 2022 18 hours ago, Luke said: Ok yes that part isn't done yet but the update has lots of other improvements. Thanks. ah ok didnt realise .. i will check it more generally against some of the other outstanding issues in the thread 1 Link to comment Share on other sites More sharing options...
Recommended Posts
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 accountSign in
Already have an account? Sign in here.
Sign In Now