| 1 |
I wrote: |
| 2 |
|
| 3 |
> Alan McKinnon writes: |
| 4 |
|
| 5 |
> > On Monday 01 March 2010 18:08:05 Alex Schuster wrote: |
| 6 |
|
| 7 |
[...] |
| 8 |
> > > solve this. And there are these annoying things. Like Amarok being |
| 9 |
> > > very unstable, and taking 5 minutes to start. What the heck is it |
| 10 |
> > > doing in this time? |
| 11 |
> > |
| 12 |
> > Fuck knows what amarok-2x does for the first 5 minutes. I *think* On |
| 13 |
> > my system it scans the music directory, presumably to find updates |
| 14 |
> > that happened when amarok was not running. Fair enough, can't argue |
| 15 |
> > that, but why is it so *slow*??? |
| 16 |
> |
| 17 |
> Yes, it scans the collection, I just verified that by removing a folder |
| 18 |
> from my collection. Start-up takes 7 minutes, I guess this also slows |
| 19 |
> down my KDE4 start-up even further (strigi also scans some stuff for |
| 20 |
> about a minute, along this music files I did not touch in any way). So |
| 21 |
> when I save my KDE session I have to remember to quit amarok before |
| 22 |
> that. Of course, I also have to remember to start amarok some time |
| 23 |
> after I logged in, so I can play music when I want without having to |
| 24 |
> wait 7 minutes first. |
| 25 |
> |
| 26 |
> This does not feel right... |
| 27 |
> |
| 28 |
> BTW, a find /data/mp3 -type d takes about a minute. Checking the date |
| 29 |
> of the directories to verify they did not alter since the last scan |
| 30 |
> should not take that much longer. |
| 31 |
> |
| 32 |
> Ah, I see the problem. It mainly scans /data/mp3/incoming, a directory |
| 33 |
> I have NOT selected as collection folder (but most other directories |
| 34 |
> in /data/mp3 are selected). Still, those files do not show up in my |
| 35 |
> collection, which is fine - some time ago amarok did index all in |
| 36 |
> /data/mp3, even if a directory was not selected. |
| 37 |
|
| 38 |
More precisely: Amarok scans folders not selected as collection for *.m3u |
| 39 |
playlists, and looks up their files. I had reported this in [*], and got |
| 40 |
some responses, but no solution or even confirmation. But today I emerged |
| 41 |
Amarok 2.3.0.90, and startup time went from 7 minutes to around half a |
| 42 |
minute now, so this bug seems to be fixed. |
| 43 |
|
| 44 |
Wonko |
| 45 |
|
| 46 |
[*] https://bugs.kde.org/show_bug.cgi?id=229239 |
Archives