This forum has been archived. All content is frozen. Please use KDE Discuss instead.

Re:unable to (re)build collection :-(

Tags: None
(comma "," separated)
imported-wireman
Registered Member
Posts
3
Karma
0

unable to (re)build collection :-(

Mon Feb 13, 2006 11:22 am
version: 1.3.1 (KDE 3.4.2)
engine: arts

Following an addition to my collection Amarok now insists that I haven\'t got a collection set-up (I did have yesterday) and any attempt to Build a new one goes through the motions (progress bar goes from 0% to 100%), but still results in no collection.

I\'ve tried removing the amarok directory under ~/.kde to start afresh with the same result. collection_scan.log has the right number entries and so amarok seems to seeing all the files, and yet no collection :-(

Also, it\'s really annoying that selecting a directory will automatically sleect all subdirectories, but unselecting it doesn\'t. It\'s a real pain to unselect 30+ entries :-(

Can anyone shed any light on this? Any idea why amarok lost my collection in the first place and why it won\'t re-find it? Please, no comments on Amarok implementing a \'taste\' filter to my collection ;-)
TIA
Chris.
imported-wireman
Registered Member
Posts
3
Karma
0
Does no one have any pointers on how to sort this out?

I did used to like Amarok, but something like this is really bad for the perceived quality of a piece of software. :angry:

All I need is something to help myself, but I can\'t find any error messages anywhere so I am stumped for where go next to try and sort this out.

Is there anyone out there? Or are you all too busy trying to work out what the next new feature to add will be, rather than worrying about problems with current versions?!!
User avatar
markey
KDE Developer
Posts
2286
Karma
3
OS

Re:unable to (re)build collection :-(

Tue Feb 14, 2006 10:02 am
It\'s a bit funny that you expect to get support for amaroK 1.3.1, which is 7 versions behind. You\'re wasting other people\'s time.

*rolleyes*


--
Mark Kretschmann - Amarok Developer
wireman
Karma
0
Aha, I knew that would get a response...

It may be 7 versions behind to you, but it is the most current version for users of Mandriva 2006. Plus you\'re exaggerating a bit - I don\'t consider the difference between v1.3.1 v1.3.8 to be at that great - it should only be bug/security fixes. The 1.3.x series will be sharing the same code-base and as such a bug in 1.3.1 could easily still be present in 1.3.8

Anyway, if my problem is a known issue then that is all I need to be told and which newer version has the fix. Simple really ;) All I got, however, was stoney silence, which is a shame as I want to like and use Amarok.

I was using v1.2.2 on Suse until very recently with no major issues (at least none that stopped me from listening to music). So from my experience v1.3.x has taken a retrograde step.

Clearly if you think that it\'s a waste of time for users to share their experiences of software and highlight potential issues - then I fear for the future of OSS or at least of Amarok. As an administrator you should know better than to **** off users.

Regards...
User avatar
dangle_wtf
Moderator
Posts
1252
Karma
0

Re:unable to (re)build collection :-(

Tue Feb 14, 2006 10:57 pm
Thing is... simply reading this forum would have given you plenty of suggestions involving upgrading. Checking the \'downloads\' page on the amarok wiki would have shown you that there are indeed mandriva packages for 1.3.8, and also 1.4-beta1.


"There are two theories to arguing with women. Neither one works."
.
If men could get pregnant, we'd learn the true meaning of "screaming nancyboy wuss"
imported-wireman
Registered Member
Posts
3
Karma
0

Re:unable to (re)build collection :-(

Wed Feb 15, 2006 11:25 am
Thanks for the information, dangle.

I posted here first to see if my issue wasn\'t due to some config error rather than a bug in Amarok. Esp. seeing as a previous version of Amarok worked fine with the exact same files. Simply upgrading may not have solved it.

TBH I find the \'debug\' output of amarok to be very sparse. It would be very useful to have some sort of logfile with verbose output of any errors. As it stands there is no easy way to find out what\'s gone wrong. :(

Looks like I\'ll have to download v1.3.8 and hope for the best... :unsure:

BTW do I also need to download a new engine if I build from source ?

Post edited by: wireman, at: 2006/02/15 06:27
Omari Norman
Karma
0
Upgrading might not help him. I have had the same problem on 1.3.8 and on 1.3.6 as well. Also, the automatic rescan seems to be sporadic at best. I will file a bug.
jmccarthy14
Karma
0
i have the same problem with the early version - i changed it so that it doesn\'t rescan my library every time (i keep around 11 thousand songs on my external) and now it just crashes when i boot it. Even when it worked i had difficulty with the collection. it wouldnt show my files unless i manually dropped the folder in to the window, and even then i\'m sure it only added it to a playlist, not the collection. when i added the folders to the collection it said something like 300 artists - im pretty sure tahts right- but showed no albums or songs or anything. i\'m upgrading to 1.4 but will that fix the collection issues?


Bookmarks



Who is online

Registered users: Bing [Bot], Google [Bot], Yahoo [Bot]