famadorian 3 Posted July 29, 2016 Share Posted July 29, 2016 Doesn't the android client keeps some kind of buffer? If I replay the song, it still takes a while, cause it wants to start streaming from the server again; is it not already buffered? Also, if I skip back to beginning, shouldn't it just start playing. It seems it's contacting the server again to get data, something it already played. The track is like 3 minutes long. It doesn't buffer anything at all? Link to comment Share on other sites More sharing options...
Luke 36999 Posted July 29, 2016 Share Posted July 29, 2016 Hi, we use the native android media player, so it decides the buffering characteristics. If you would like to download the media locally onto the device, you could check out the sync feature. Link to comment Share on other sites More sharing options...
softworkz 3325 Posted July 30, 2016 Share Posted July 30, 2016 Currently, Emby is starting a new transcoding session on the server for every seek operation you are performing in the client and does not allow seeking via http range requests. The media playback implementation in Chromium (I would suppose the Android player is based on this as well), is very strict: If the server does not support range-requests, it doesn't use any local buffering at all when the user tries to seek. Link to comment Share on other sites More sharing options...
famadorian 3 Posted August 6, 2016 Author Share Posted August 6, 2016 Has a bug been filed on this? Link to comment Share on other sites More sharing options...
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