Version: 2.3.1-GIT (using KDE 4.4.95) OS: Linux amarok reads all playlists on disk on startup. this makes amarok startup very slow when collection is on networked drives (but at least it does not seem to access every file in the playlists as it used to do before). additionally, the "view sources" button that contains settings to hide playlists on disk does not remember its settings across restarts. Reproducible: Always
Confirmed, I also would like to have this done only once I switch to the Saved Playlists. Since I have a lot of playlists, this takes easily 10 seconds at startup. BTW, it did not scan those at some point anymore in the git branch, it only started to do so again a few weeks back.
*** Bug 248922 has been marked as a duplicate of this bug. ***
So the problem is twofold: 1) elements in the amarok playlist are checked on startup (should not need to be done) 2) elements in EACH SAVED m3u playlist are also checked on startup And I do not believe it is a valid alternative to do 2) EVEN when switching to the saved playlists view. what for? what would be the point? and this will cause errors if e.g. playlists point to files in an NFS server that is not mounted (Frequent use case for laptop users), and be excruciatingly slow for lots of saved playlists / network mounts.
Confirmed. Version 2.3.0, Kubuntu 10.04, KDE 4.4.2 For me Amarok takes about 10 minutes to start. All my music (about 4000 tracks) is located on a NAS storage, mounted with NFS. On startup Amarok checks all files for metadata (ID3 tags). I've used version 1.4 for some months (used this: http://www.dwasifar.com/?p=1111) because of this problem with startups. Tried the latest version again to check if the problem still existed. Unfortunately it does. Can't Amarok store the metadata for known files and only check metadata for new and updated files?
Sorry Fred, but this report is about the developer version, which is 2 versions ahead of yours, so your confirmation is not really useful. Also, this bug is already confirmed, as its status is set to "New", not to "Unconfirmed"
Since today saved playlist will load tracks only when required. i.e. on demand when the user expands one in the view. This already dramatically improves the startup time and performance. It can be improved even more by loading the playlists in the background (thread). But this will have to wait until post 2.4.