vidar wrote:Somewhat unrelated, I've considered actually developing my own client if this isn't going to happen in the official one. I don't have a lot of experience coding for android, so I'm curious if there's some technical reason for the caching. I'd prefer to have it simply stream directly to the music player backend.
The source code for the android app is in the repositories already. You can just patch it and if you do a good job I'm sure Sindre would include it.
The reason for it being a cache is because the first version released tried to stream it straight into the music player as expected, but it failed constantly and just didn't work very well over 3g or edge. The caching gave him the ability to set a size requirement for buffer as well as store the file itself as it played.
I'd like to see the "restart" issue resolved (which causes a stutter and the play to show up in the notify again) fixed asap. That's the one thing really holding me back. It's hard to jam out when the thing skips or pauses

. Also if the cache had a simple song number choice that'd be great. If I was able to cache the currently playing song plus one more I think that'd solve my problems just fine. That'll also give the player a quick start for the next file since it won't need to buffer before starting like most other streamers tend to do. Since this is album based, I'd like seemless tracks.