Kodi Community Forum

Full Version: Media importing and library integration (UPnP, Emby, Plex, ...)
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
Ok thank you
After update the plugin it shows myPlex as an option and it connects through myPlex.
Thank you again
Can we use emby for kodi together with this implementation just for the music library?
Yes it is possible but but unfortunately these builds require python 3 compatibility, and Emby for Kodi is not. EmbyCon is, so you can use it instead.
@ntilagoa,
If you don't absolutely have to use a server for music, I would recommend that you try Kodi's music section. I did and WOW!!. It is quite impressive, especially for collections. It allows to easily split your music into different "libraries" using the new Sources node. You will not be disappointed. It made fire up a tag editor to correct my tags. I have been using Kodi for more than a decade and I always use file mode for music. @DaveBlake and his new partner, @black_eagle have made Kodi's music section one of if not the best for managing your own music collection.
reading the first post, could this be used to use a bluray / dvd iso (or bdmv / video_ts file system) as a "source" of multiple videos.  i.e. enumerating the playlists and allowing kodi to associate metadata with individual playlists (or ignore playlists one doesn't care about)
Unfortunately not in this case. Source in this case refer to a media server (Kodi, Emby, Plex or Jellyfin currently) or a plugin for an online source (none so far).

Cheers,
LongMan
(2020-02-15, 08:26)sualfred Wrote: [ -> ]@Montellese 
Is there any chance for a optional "native path" sync? With Emby for Kodi we have a option to scan the native paths to the library. This is useful for local setups and addons which require direct access to the folders.
For Emby you can enable "Direct Play" (IIRC it is enabled by default) and then during importing the add-on checks if Kodi can access an imported item's path directly through its VFS. If it can it will use the direct path instead of going through the Emby server's Direct Stream functionality.
@Montellese 

Yes, but the DB has plugin:// paths stored and not the native paths. That's what other addons require. They cannot access a plugin:// path that is going to be resolved on a playback attempt
(2020-02-19, 22:51)sualfred Wrote: [ -> ]@Montellese 

Yes, but the DB has plugin:// paths stored and not the native paths. That's what other addons require. They cannot access a plugin:// path that is going to be resolved on a playback attempt
Neither mediaimporter.emby nor mediaimporter.plex store any plugin:// paths. This is on the TODO list but I never looked into it so far. They either store "direct play paths" or "direct stream URLs" (e.g. http://localhost:8096/emby/Videos/<ItemI...y=<ApiKey>).
Sorry, I meant it stores http:// paths but smb/nfs paths would be nice for local networks.
(2020-02-20, 07:17)sualfred Wrote: [ -> ]Sorry, I meant it stores http:// paths but smb/nfs paths would be nice for local networks.
I only tested it with local paths and there the add-on detects that the paths are directly accessible to Kodi (using xbmcvfs.exist()) and stores the "raw" paths in the database. I'll give it a try with Samba or NFS paths when I get some time.
(2020-02-20, 14:15)Montellese Wrote: [ -> ]
(2020-02-20, 07:17)sualfred Wrote: [ -> ]Sorry, I meant it stores http:// paths but smb/nfs paths would be nice for local networks.
I only tested it with local paths and there the add-on detects that the paths are directly accessible to Kodi (using xbmcvfs.exist()) and stores the "raw" paths in the database. I'll give it a try with Samba or NFS paths when I get some time. 
OK I was able to reproduce this with UNC paths in Emby and https://github.com/Montellese/mediaimpor...193db756e5 (on master branch) should fix it.

Please use the pre-installed media import repository to install / update the media importer add-ons from there. This way you should get all necessary dependencies.

ATTENTION: If you were running a previous test-build delete your MyVideosxXX.db.

Changelog