croneter/PlexKodiConnect

[strm files] use PKC alongside plugin.video.netflix and plugin.video.amazon-test

padok asked for this feature 5 months ago — 2 comments

padok commented 5 months ago

Origin: https://github.com/croneter/PlexKodiConnect/issues/920

The current version of PKC doesn't play nice with different add-ons or offline media.

The add-ons CastagnaIT/plugin.video.netflix and Sandmann79/plugin.video.amazon-test offer greater interoperability though the way they integrate themself in the Libary. Instead of writing directy to the database like PKC does, they create placeholder directory trees in there add-on data directories, which can easily be integrated using Kodi's internal scrapers.

plugin.video.amazon-test
├── Movies
│    └── _Movie_name_
│           └── _Movie_name_.strm
└── TV
    └── _Show_name_
            └── _Show_name_ - S00E00 - _Episode_name_.strm
plugin.video.netflix
├── movies
│    └── _Movie_name_
│           └── _Movie_name_.strm
└── shows
    └── _Show_name_
            └── _Show_name_ - S00E00 - _Episode_name_.strm

The strm files itself contain internal add-on links, that can start every add-on process needed for proxying or playback. That way it's easily possible to merge my netflix, amazon and offline librarys and keep them up to date, since the add-ons keep there directory trees in sync and Kodis scraper do there thing. The Amazon add-on even provides additional information through *.nfo files.

I would love to get an option for PKS, that also create a placeholder directory trees using strm files. Since the only important information, that I got from the wiki is the URL "https://192.168.1.2:32400/library/metadata/1234", strm files could look like this:

plugin://plugin.video.plexkodiconnect/?mode=PlayVideo&url=https%3A%2F%2F192.168.1.2%3A32400%2Flibrary%2Fmetadata%2F1234

That way the PKS can be provided with all needed information.

That way PKC woud play nicely along every other add-on and configuration. It could also be a great alternative to writing directly to Kodis database, that I would consider as risky.

| michaelarnauts commented 4 months ago

This is exactly what I need. I think this is a better wat to integrate with Kodi vs the database access. We probably still need to read the database to sync the watched status.

Join the discussion!

Sign-in with GitHub to comment