1 |
Alan McKinnon writes: |
2 |
|
3 |
> On Monday 01 March 2010 18:08:05 Alex Schuster wrote: |
4 |
> > On the other hand, from time to time I have show-stoppers, and then I |
5 |
> > cannot use kmail, or no KDE4 at all. And have to invest time to solve |
6 |
> > this. And there are these annoying things. Like Amarok being very |
7 |
> > unstable, and taking 5 minutes to start. What the heck is it doing in |
8 |
> > this time? |
9 |
> |
10 |
> Fuck knows what amarok-2x does for the first 5 minutes. I *think* On my |
11 |
> system it scans the music directory, presumably to find updates that |
12 |
> happened when amarok was not running. Fair enough, can't argue that, |
13 |
> but why is it so *slow*??? |
14 |
|
15 |
Yes, it scans the collection, I just verified that by removing a folder |
16 |
from my collection. Start-up takes 7 minutes, I guess this also slows down |
17 |
my KDE4 start-up even further (strigi also scans some stuff for about a |
18 |
minute, along this music files I did not touch in any way). So when I save |
19 |
my KDE session I have to remember to quit amarok before that. Of course, I |
20 |
also have to remember to start amarok some time after I logged in, so I |
21 |
can play music when I want without having to wait 7 minutes first. |
22 |
|
23 |
This does not feel right... |
24 |
|
25 |
BTW, a find /data/mp3 -type d takes about a minute. Checking the date of |
26 |
the directories to verify they did not alter since the last scan should |
27 |
not take that much longer. |
28 |
|
29 |
Ah, I see the problem. It mainly scans /data/mp3/incoming, a directory I |
30 |
have NOT selected as collection folder (but most other directories in |
31 |
/data/mp3 are selected). Still, those files do not show up in my |
32 |
collection, which is fine - some time ago amarok did index all in |
33 |
/data/mp3, even if a directory was not selected. |
34 |
|
35 |
|
36 |
> Fuck also knows what the amarok devs are doing in general. I still |
37 |
> can't find a way to move stuff to an mp3 player like the old 1.4 |
38 |
> version did. And the library thingamagij still doesn't always update |
39 |
> tags, or put tag changes that it itself did into it's own database. It |
40 |
> gladly accepts any changes you make in the Edit Tags dialog, and tries |
41 |
> to write them, even if it knows it cannot do it (no support for that |
42 |
> format, permissions, etc). Then, no warning or message about this. |
43 |
|
44 |
Ah, this looks familiar, I ran into this, too. |
45 |
|
46 |
> Depending on which bleeding edge latest-svn commit build you happen to |
47 |
> get on any given day, this last might or might not tell you something |
48 |
> in the status bar. |
49 |
|
50 |
I'm always using the newest version that is not hard-masked. with every |
51 |
new version, some things get better, but others get worse. This delays and |
52 |
startup times are new to me, but on the other hand I did not get any file |
53 |
corruption for a long time. |
54 |
I do not like the new toolbar though. Where are the stop, forward and back |
55 |
buttons? And for the volume control I have to move the mouse in a circle |
56 |
around it... or use the scroll wheel, okay. Nah, I liked it better the way |
57 |
it was before. |
58 |
|
59 |
|
60 |
> For all the above reasons, and more, I have switched to clementine |
61 |
> (it's in portage). It's a Qt port of amarok-1.4 and has equivalents of |
62 |
> all the music- playing goodness that amarok used to have. It doesn't |
63 |
> do tags, external players, wikipedia etc etc, it just plays music. And |
64 |
> you have to tag your music by other means with eg kid3. I can live |
65 |
> with that. At least it starts and stays up. |
66 |
|
67 |
Nice! But not for me. I like the wikipedia stuff. And tagging, now that it |
68 |
seems to work. And what amarok is supposed to become. Yes, I like it much |
69 |
better than the old amarok, it's just that things do not already work |
70 |
fine. So I will keep suffering, until some day amarok will not do all the |
71 |
annoying stuff it currently does. The day will come! Hopefully long before |
72 |
they start coding amarok-3 and all gets worse again. I'll just have to |
73 |
wait. And wait. |
74 |
|
75 |
Thanks anyway for the tip, at least I can use clementine when I see that |
76 |
amarok is not running yet and did not do its 7 minutes of scanning |
77 |
already. |
78 |
|
79 |
Wonko |