loeffelpan 12 Posted February 22, 2019 Share Posted February 22, 2019 Sorry, but I'm new to this and didn't find any answer in other threads. What does this setting mean? Didn't I change between SMB and HTTP by selection of the playback mode (Addon / Native)? Or is this to fallback to HTTP with Native playback enabled? Link to comment Share on other sites More sharing options...
Angelblue05 4130 Posted February 22, 2019 Share Posted February 22, 2019 Playback mode: https://github.com/MediaBrowser/plugin.video.emby/wiki/Settings#sync Does this help for the setting itself? https://github.com/MediaBrowser/plugin.video.emby/wiki/Settings#playback It specifically states right above the settings block that these settings do not apply to native playback mode. Native playback is just that, Kodi will playback content as if you had a normal Kodi setup. The add-on still manages your Emby content artwork + metadata. Add-on playback mode is the add-on initiates playback, so it can do whatever it wants, direct play, play from HTTP, transcode, remote playback, etc. Link to comment Share on other sites More sharing options...
loeffelpan 12 Posted February 22, 2019 Author Share Posted February 22, 2019 (edited) Native playback is clear. But for me it‘s not clear what will change in addon mode when „Force HTTP“ is not set? Doesn‘t addon mode always use HTTP? Edited February 22, 2019 by loeffelpan 1 Link to comment Share on other sites More sharing options...
Angelblue05 4130 Posted February 22, 2019 Share Posted February 22, 2019 (edited) Ok. Add-on playback mode can direct play over your network (or local) and HTTP or transcode. The difference between the two modes is the path we add to the Kodi database. With add-on playback mode, it redirects to the add-on. This allows the add-on to control what happens before playback. We can enable cinema mode, support multi versions, support additional parts, tell Kodi to play x path (network or remote). However, this masks the true file location. Other Kodi add-ons that need to see the file location will not work correctly with add-on playback mode. With the beta version + add-on playback mode, we can finally achieve direct play as Kodi would normally load playback. This allows Kodi to load chapter images and subtitle add-ons (or other add-ons that operate at playback) can see the real file location. Hope this clarifies it! Edited February 22, 2019 by Angelblue05 Link to comment Share on other sites More sharing options...
loeffelpan 12 Posted February 22, 2019 Author Share Posted February 22, 2019 Thank for your explanation, but we seem to misunderstand each other. You have well explained the difference between addon and native playback mode. That’s clear. What I am asking is for, is the difference within addon playback mode when forcing http oder not? It’s true by default. So what happens with this checked or unchecked? Link to comment Share on other sites More sharing options...
tomimc 13 Posted February 22, 2019 Share Posted February 22, 2019 The wiki says: Force HTTP playback Play the file over HTTP, which is provided to Kodi by Emby. Useful if you have path issues. If the bitrate allows for it, there will be no modifications to the file, direct playing over HTTP. Enviado desde mi MI 5 mediante Tapatalk 1 Link to comment Share on other sites More sharing options...
loeffelpan 12 Posted February 23, 2019 Author Share Posted February 23, 2019 Clear enough. But my question is: What does the addon when not forcing HTTP? I thought addon always use HTTP to be sure it’s working out of the box. Link to comment Share on other sites More sharing options...
Angelblue05 4130 Posted February 23, 2019 Share Posted February 23, 2019 (edited) Ok. Add-on playback mode can direct play over your network (or local) or HTTP or transcode. When the option is disabled, it will try to play over your network. Yes the option is enabled by default, as to guarantee things work out of the box for users. As people don’t always know how to correctly setup their paths in emby so that Kodi can locate the files. Edited February 23, 2019 by Angelblue05 Link to comment Share on other sites More sharing options...
loeffelpan 12 Posted February 23, 2019 Author Share Posted February 23, 2019 Ok got it. On which way addon tries to access files directly? Is it smb? Or does this only work on the same device like Emby server is installed? Is there an guide to setup path correctly for addon (without http) or native path? Sorry for annoying you and thanks for your patience. Link to comment Share on other sites More sharing options...
Solution Angelblue05 4130 Posted February 23, 2019 Solution Share Posted February 23, 2019 (edited) It uses the path Emby returns. In your webclient, edit metadata of one of your content, you'll see the path at the top. That's what the add-on will use. Library path: https://github.com/MediaBrowser/Wiki/wiki/Library%20setup#library-paths Optional network path: https://github.com/MediaBrowser/Wiki/wiki/Optional-Network-Paths There is no guide. Just switch to add-on playback, and with trial errors. The path is retrieved at playback time, so you can update it in Emby with the optional network path and test it right away in Kodi. The only way to truly tell it works (direct play over network) is by checking your Kodi log and seeing the path Kodi loads. If it's a network one, then you are good to go. Edited February 23, 2019 by Angelblue05 Link to comment Share on other sites More sharing options...
loeffelpan 12 Posted February 23, 2019 Author Share Posted February 23, 2019 Ah now I got it. I will try to setup optional network path in emby and uncheck. Thanks for your patience. 1 Link to comment Share on other sites More sharing options...
Recommended Posts