[prev in list] [next in list] [prev in thread] [next in thread] 

List:       amarok-bugs-dist
Subject:    [Bug 276822] New: cache tracks that take a long time to load
From:       Ivan Vasin <nisavid () gmail ! com>
Date:       2011-06-30 13:20:39
Message-ID: bug-276822-71684 () http ! bugs ! kde ! org/
[Download RAW message or body]

https://bugs.kde.org/show_bug.cgi?id=276822

           Summary: cache tracks that take a long time to load
           Product: amarok
           Version: 2.4.1
          Platform: Ubuntu Packages
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: wishlist
          Priority: NOR
         Component: general
        AssignedTo: amarok-bugs-dist@kde.org
        ReportedBy: nisavid@gmail.com


Version:           2.4.1 (using KDE 4.6.4) 
OS:                Linux

currently, when a track is played, there is a delay before it is played that
seems to be roughly proportional in length to the length of the track.  this is
not noticeable if the track is stored locally, but it is very noticeable if the
track is stored on a remote server.

in my case, i store some of my music on a cloud server hosted by PackageCloud. 
i mount the storage using WebDAV via davfs and symlink the mount into my home
directory.  for most tracks, the delay is around 10-60 seconds.

a caching mechanism in Amarok would, after some time, alleviate these delays,
especially for commonly played tracks.  the cache should be stored somewhere on
the local disk.  the cache size limit should default to something large enough
for at least one typical FLAC track (at least 50 MB) and perhaps large enough
for at least one typical WAV track, and it should be configurable, with no
upper bound on the limit, since some users (such as myself) have plenty of
local disk space to spare and would gladly trade it for smoother playing of
remote tracks.  the location of the cache should also be configurable,
defaulting to something under /var/tmp.

this is motivated by the following principles:
  * if a user wants to play music, he or she prefers that it plays now.
  * up to a point, disk space should be sacrificed for the sake of usability.
  * up to a point, disk space should be sacrificed to save bandwidth usage.
  * for the vast majority of users, disk space is cheap.

Reproducible: Always

Steps to Reproduce:
play a track that is stored on a remote server.

Actual Results:  
there is a long delay before the track is played, even if it was played
recently or is the next track in the playlist.

Expected Results:  
if the track was played recently ("recently" being defined according to the
configured cache size) or is the next track in the playlist, it should play
with little or no delay.

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
Amarok-bugs-dist mailing list
Amarok-bugs-dist@kde.org
https://mail.kde.org/mailman/listinfo/amarok-bugs-dist
[prev in list] [next in list] [prev in thread] [next in thread]