punkid 2 Posted July 12, 2018 Posted July 12, 2018 (edited) I have Emby Server on an AMLogic box running CoreELEC. Its working, mostly. Here's the setup: Box running Coreelec with the server, which is also one of the clients. Then some other clients (local) on the network. The client which is on the server is also using path substitution, even though it has access to the same paths as Emby. Any way to remedy this? I have problems playing files on the server device, sometimes files take very long to play, sometimes they just refuse to start playing. Also,I feel this drags out library scans more than it should. Sorry, also shouldve mentioned that im using Kodi as the client on all devices, in Direct Path mode. Edited July 12, 2018 by punkid
Solution Luke 42078 Posted July 12, 2018 Solution Posted July 12, 2018 Right because it's going through the network? Currently these settings will apply to all apps, but this is probably a scenario we should consider allowing adjustment for in the future. Thanks. 1
punkid 2 Posted July 12, 2018 Author Posted July 12, 2018 Thankyou! Thing is, this device is already quite weak, and this method adds extra stress because of resolving the smb address etc. Would be helpful if there was an option to bypass path substitution on a per client basis. Should be built into the Kodi addon maybe? I'm sure you guys will come up with an excellent solution.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now