extragear/multimedia/amarok
Martin Aumueller
aumueller at uni-koeln.de
Mon Jul 24 19:01:36 UTC 2006
There is still a downside to ATF in its current state: every time a MetaBundle
is created, its corresponding file will have to be read for finding the
unique id. This will slow down the loading of large playlists considerably.
Why not just store the unique id in the database?
On Mon July 24 2006 20:37, Jeff Mitchell wrote:
> SVN commit 565899 by mitchell:
>
> 1) Use all ATF features that only require reading the UID at all times.
> GUI option now controls whether new UIDs are written to files. Note that
> this helps generalize ATF; we can use this to now enable other writes to
> metadata if we wish and have it be a global "yes you can touch my files"
> setting. 2) Only force a rescan/playlist clear the first time ATF is turned
> on (err, since this commit...) 3) If Amarok is closed before rescan
> finished, don't force it on restart...takes too long for some people. 4)
> ChangeLog updates.
>
>
>
> M +7 -0 ChangeLog
> M +4 -4 src/Options7.ui
> M +2 -1 src/Options7.ui.h
> M +5 -1 src/amarokcore/amarok.kcfg
> M +19 -22 src/app.cpp
> M +5 -16 src/collectiondb.cpp
> M +32 -23 src/metabundle.cpp
> M +3 -5 src/playlist.cpp
> M +3 -3 src/playlistitem.cpp
> M +2 -4 src/playlistloader.cpp
> M +2 -2 src/scancontroller.cpp
More information about the Amarok
mailing list