bigeyez 10 Posted October 22, 2017 Posted October 22, 2017 Hi, I am trying to use Emby with Neutron Player on Android. It works buttttt adding songs to the Neutron's database (it does caching)is slow, very slow, Neutron is able to cache up to 5 songs a second or less! I also tested Minidlna with Neutron player. And Minidlna can send songs to Neutron in hundreds so adding thousands of files takes less than 20 mins vs many hours with Emby. I do not know what the actual technical term is so I am calling it chunks. Is there a way to increase the number of file chunks to the clients? So that I can maybe match MiniDlna's speed with my player. thanks
Luke 42077 Posted October 22, 2017 Posted October 22, 2017 Probably because it's trying to pull down the whole library recursively at once which I've noticed some dlna apps do. Bubble upnp is nice and fast though
bigeyez 10 Posted October 22, 2017 Author Posted October 22, 2017 (edited) Yeah this is not about downloading the songs, it is trying to cache the library entries. I do not wnat to use Bubble Upnp or any other really those are almost too primitive to be a music player. Neutron is the best music player out there for mobile. So my question is this, how can I increase the speed of library caching from server to client? Is this something that I can adjust on the server side. Probably because it's trying to pull down the whole library recursively at once which I've noticed some dlna apps do. Bubble upnp is nice and fast though Edited October 22, 2017 by bigeyez
Luke 42077 Posted October 22, 2017 Posted October 22, 2017 I haven't tested that player, sorry, but you could tell it to not cache the entire library, if it has a setting for that.
bigeyez 10 Posted October 22, 2017 Author Posted October 22, 2017 (edited) Yeah that is not how it works. It does caching which helps with search and some other stuff. I am happy with its caching personally. And there is no setting for it in Neutron. Are you saying that increasing the chunk size(as I called it) not possible with Emby? Could this be a feature req? I haven't tested that player, sorry, but you could tell it to not cache the entire library, if it has a setting for that. Edited October 22, 2017 by bigeyez
Luke 42077 Posted October 22, 2017 Posted October 22, 2017 It is the client app that tells the server how many records to send back.
bigeyez 10 Posted October 22, 2017 Author Posted October 22, 2017 (edited) Well if that is the case how come Neutron can grab a hundred songs from MiniDlna at one go and only 5 songs from Emby (all running on the same server)? I think this is a server side thing because I tested bunch of Dlna servers with it and all varied and Emby and UMS being the slowest of all and MiniDlna being the fastest. It is the client app that tells the server how many records to send back. Edited October 22, 2017 by bigeyez
bigeyez 10 Posted October 22, 2017 Author Posted October 22, 2017 Can this speed be improved by editing those xml files under dlna/system?
Luke 42077 Posted October 22, 2017 Posted October 22, 2017 Our dlna testing has mostly been browse and play. We haven't done a whole lot of testing around apps that pull down the entire library at once. It's something to look at in the future. Thanks.
bigeyez 10 Posted October 22, 2017 Author Posted October 22, 2017 (edited) Understandable, I realize this use case is not the common Dlna use case. However please feel free to update this post if you can think of a solution. thanks Edited October 22, 2017 by bigeyez
Tuner 0 Posted October 1, 2019 Posted October 1, 2019 (edited) @@bigeyez, what did you settle on in the end? Was this a fair test between emby and minidlna? Edited October 1, 2019 by Tuner
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