Reply to thread

Message

<blockquote data-quote="ltfearme" data-source="post: 1023921" data-attributes="member: 52219">That's cool that you already have a plugin.&nbsp;There is a handler for each mediaportal plugin that we support in the Trakt Plugin e.g. the user can turn MP-TVSeries and MovingPictures plugin on and when they watch something in that respective plugin we can match that in the respective databases to determine if we should scrobble that media. Similarly the same occurs for library sync.&nbsp;The reason we do it this way is that sometimes there is just not enough information available from the MP core player to get an exact match online, by using the metadata from the respective plugins we can get other info such as IMDb/TMDb IDs etc. It's also done this way so we don't try to do collection/watched syncing on every plugin installed (there is a lot of media plugins).&nbsp;It seems to make more sense to handle this from the MediaBrowser server rather than implement another plugin handler in the Trakt plugin for MediaPortal. I guess the only question I want to ask is if the MediaBrowser trakt plugin on the server detects media playing from a MediaPortal client does it send &quot;MediaPortal&quot; or &quot;MediaBrowser&quot; as the client playing to Trakt? It would be nice if distinguished between clients.&nbsp;The Trakt plugin can still be used with-in MediaPortal for other stuff as its very feature rich and pretty much implements 90% of the trakt API in a nice GUI e.g. view Recommendations, Trending, Watchlists, Activity Dashboard etc.</blockquote>

[QUOTE="ltfearme, post: 1023921, member: 52219"] That's cool that you already have a plugin. There is a handler for each mediaportal plugin that we support in the Trakt Plugin e.g. the user can turn MP-TVSeries and MovingPictures plugin on and when they watch something in that respective plugin we can match that in the respective databases to determine if we should scrobble that media. Similarly the same occurs for library sync. The reason we do it this way is that sometimes there is just not enough information available from the MP core player to get an exact match online, by using the metadata from the respective plugins we can get other info such as IMDb/TMDb IDs etc. It's also done this way so we don't try to do collection/watched syncing on every plugin installed (there is a lot of media plugins). It seems to make more sense to handle this from the MediaBrowser server rather than implement another plugin handler in the Trakt plugin for MediaPortal. I guess the only question I want to ask is if the MediaBrowser trakt plugin on the server detects media playing from a MediaPortal client does it send "MediaPortal" or "MediaBrowser" as the client playing to Trakt? It would be nice if distinguished between clients. The Trakt plugin can still be used with-in MediaPortal for other stuff as its very feature rich and pretty much implements 90% of the trakt API in a nice GUI e.g. view Recommendations, Trending, Watchlists, Activity Dashboard etc. [/QUOTE]

Verification