Ever since I upgraded to 1.4.2 amarok won't build a collection.  It aborts saying libTag may be corrupt and it lists a few offending files.  This problem wasn't present in any previous versions of amarok.  I tried compiling libTag from source....same problem.  I use mysql for the db.  I have tried removing the amarokrc file and everything in .kde/share/apps/amarok and re-installing, using a different database....same error.  I have opened the offending files with easytag to see if the tags are there and all looks good.

This is beginning to frustrate me.

I get no errors in the console when running it from there...Oh, I'm using the xine engine.

Help Please
Thanks,
Bill

Try to move the problematic files out of your collection.

I wish it were that simple....I've got almost 11,000 tracks and the problem files seem to number in the hundreds.....I've removed entire directories of music.....One thing I noticed is that the "problem files" seem to all be on one particular server....I have my collection spread across three servers, all connected through cifs mounts in the fstab.

I can provide an example of a song that crashes the collection builder.....I think the whole cd crashes it....By the way, I ripped this cd myself using kaudiocreator.

....update...I'm moving the entire 65 gigs from one server to another to see if anything changes......

Copied all music files to another fileserver......same errors....diferent tracks though...What was changed in the collection scan code from 1.4.1 to 1.4.2 ??  Is there a way to work around this and force amarokcollectionscan to build the collection despite taglib errors?  This is really a pain because I can't access almost 6000 tracks that I had access to last week (1.4.1)

From the error message, it seems that the number of taglib errors is causing it to fail.....not just one or two corrupt files....

If I drag a whole bunch of "offending" music folders from the FILES tab in amarok and place them in the playlist area, everything is fine....all tags look good....no errors.

Maybe I should try to post this in the bugs area???

here is the error that pops up :

Sorry, the Collection Scan was aborted, since too many problems were encountered.
Advice: A common source for this problem is a broken 'TagLib' package on your computer. Replacing this package may help fixing the issue.
The following files caused problems:
/home/bill/napoleon/Music/music/Guitar Hero Original Cuts/disc 2/Bark At The Moon.mp3
/home/bill/napoleon/Music/music/ZZ Top/1979 Degüello/01 I Thank You.m

"1979 Degüello/01 I Thank You.m" looks weird. Is that really the correct path?

no....the error mesg truncated it a little and some of the character coding didn't survive the cut and paste.....

I just ran amarokcollectionscanner from the command lind and let it chug through the offending collection and it spit out a ton of xml....I ran it again and piped it to a text file and while it was running the console filled with taglib errors about invalid sample rate....:

TagLib: MPEG::Header::parse() -- Invalid sample rate.

here is the xml from the first track listed in the error msg:



and the next:

The error message "Invalid sample rate" is irrelevant, it can be ignored. TagLib prints this all the time, it's just for debugging.

figured that since I get those on all my music directories....


Anything else I can do to help diagnose this??

I noticed in another topic that someone had a 200GB collection that wouldn't build so he split it up into sections and it seems to build ok now....Could that be the issue? I rechecked and I have 20GB, 38GB and 20GB chunks in my collection scan paths....the 38GB chuck is the one that fails every time.

Ok, This must be a bug...please fward to the devel team.....

I hacked my collection up into chunks and individually everything is fine (build collection one chunk at a time)

when I add more scan folders and rescan collection wham....collection scanner aborts and I get nothing.....

Again...Karma thank for trying but this should be forwarded to the devel team.....if it hasn't already been addressed...

Good luck

I've been having the same exact problem with SimplyMepis 6.0 and 1.4.2 stable.

I tried the above + installing the dev package for libtag1c2a 1.4-3 and doing a forced upgrade to libtag1c2a and the dev package to version 1.4-4. Still having the same issue. My music is all stored on another computer on my network as well and mounted via Smb4k.

We've recently dealt with a very similar incident on IRC. This guy had his collection mounted via Samba, and that was the problem. Switching to NFS magically fixed all collection issues.

Please note that smbfs isn't a fully compatible file system, there are various issues with it that can confuse TagLib. Give NFS a shot, it's a lot more reliable.

NFS fixed this issue for me....I wonder why two of my cifs shares work fine....seems like there is an issue in how amarok handles taglib errors. 

I have been using cifs shares with amarok for at least a year without issue....1.4.2 broke the cifs share, this should be fixed.

Switching to NFS is a good workaround but there is a problem in the code.

Thanks for your help, Mark.

Bill

Umm... as far as I know that's not possible whenever the machine I'm getting the share from is running WinXP...

Hi, I have the same problem using Mandriva 2006 and Amarok 1.4.2.

The collection build fails ALWAYS in 85%, no matter what file it scans at that point. I just added 500 MB with mp3 files and it again failed at 85%, then I removed the "conflictive file" pointed in collection_scan.files and then failed, with the previous file. Then, I removed the entire album, so it failed on another directory.

My collection is about 12G, located in my /home directory, in my local hard disk (No NFS or Samba).

As they said before, this didn't happend on previuos versions.