-
|
do we have a way to enable strict ID matching only option? Thanks |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 1 reply
-
|
CrossWatch first normalizes both sides into: type, title, year, ids (and for episodes also show_ids, season, episode). On the Jellyfin side, IDs come from Jellyfin item ProviderIds when available (IMDb/TMDb/TVDb). For episodes, the Jellyfin adapter also tries to include show context in show_ids, so an episode match isn’t “episode title only”. If external IDs are missing, matching can fall back to title/year In short: it first looks for external ID's if that doesnt work the last fall back is title/year. Be absolute 100% jellyfin has the correct metadata for all the items. In most cases thats the issue. Also syncing from tracker to mediaserver is always more tricky: https://wiki.crosswatch.app/related-information/trackers-vs.-media-servers the best practice is always source: media-server to tracker (one-way or two-way) to answer you question: I don’t have a strict ID-matching mode right now, but it could be a good idea. The catch is: as soon as it’s enabled, people will start asking why certain items aren’t syncing..... The fallback on title/year isnt perfect but will work in i think 90% of the cases. |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.

No worries...ive already added it and will be available in version 0.91.
It will be under pair config - providers - media server (plex, emby etc) enable or disable. default is disabled and can be configured per pair.