Search the Community

During the setup of the client I selected to use direct paths. After the synchronization it defaults to web streaming. If I look into the settings the direct path option is greyed out. I have the problem with the native Emby client and also with Kodi (via Emby for kodi). My Synology NAS doesn't have a powerfull CPU (DS414), so I used direct path as I think the NFS server is built-in and it would require less CPU then the webstreaming. Secondly, where I live, the movies are not dubbed and we are heavy users of subtitles. That is the reason why I also use Kodi. Kodi has more features to download another subtitle when the current one is not correct. I know that Emby made some good progress in this direction but Kodi still offers more choices. By using direct paths, it shows the full path and filename. webstreaming shows only the user-friendly name (and a URL). It is very difficult to match the subtitle to the movie within the full filename. This worked great in the past. There were some issues with the built for the Synology DS414 and I had to uninstall and reinstall it a few times. During the uninstallation all my settings were lost and I had to start over again. I know I should have taken a backup, but it was already to late. I started with a clean installation. I also purchased a lifetime subscription. I never hit the issue that I need to unlock the application. But you guys gave me great support with the builds for the DS414, so I decided to purchase a lifetime subscription. I have the issue on a Nvidia Shield and a Google TV (2020). Both are running Android TV. I have an old PC laying around and I installed Ubuntu on it. This PC has also this problem. Any idea how to get back to direct path?

First of all, let me say that I searched the forum and haven't found anything that covers this topic. I have a few questions regarding the setup of Emby together with Kodi when they are running on the same machine, to be precise, a headless Ubuntu-based HTPC. I scanned my video files to Emby, they show up just fine on the server side. Emby fetches all the artwork properly, including extrafanart and extrathumbs. I use the Kodi addon (1.1.53) and want to get direct playback running as smooth as possible. As said, Kodi runs on the same device with the same user and same filesystem access. But now a few questions arise: 1. Do I need the option to use local paths instead of Emby redirection enabled? When I do not enable that option, Kodi does not see the extrathumbs Emby provides because the skin needs the actual filepath to see them. 2. Will a path substitution solve the issue mentioned above? My video files are stored under /media/Media, will a substitution /media/Media -> /media/Media make a difference? 3. And, next big issue: I know that Kodi handles music different from the video files. How will path substitution and direct playback work here? How does the add-on provide the music cdart to Kodi? Will it set the item.art(discart) property? Again, the problem is that the skin I use right now needs the actual filename path for cdart, extrafanart and extrathumb. It would not be a big problem to change the skin a little, but right now I just don't now how because I don't know what artwork is provided to the music.db directly and which not.