Problem: Metadata is being reset after organizing.

I have indicated the disc number in the album name up to now, I'm now trying to update my mp3's to use the disc number field.

I can change the album name and disc number, BUT, when I go to organize these files, all metadata is reset to the original metadata, but the actual files are organized using the new metadata, now nonexistent. The kicker on this one is that, the first track retains the new metadata, and sometimes the mp3 has been completely destroyed (it sounds like beeping).

So...

For all tracks:
"Album (CD1)" -> "Album" [DN = 1]

'Organize'

Track 1:
"Album" [DN = 1]
mp3 = garbage (occurred twice)

Tracks 2..12:
"Album (CD1)"

All files are in the 'new' directory.


I don't know how amarok deals with ID3 (I was under the impression that it didn't touch the ID3 at all, all the metadata just when into the db), but it seems after it organizes the files it reads the ID3 for metadata, hence the reset. I have no idea why the first track behaves differently.

Ideally I'd like the ID3 to be updated with the metadata but I guess this isn't possible...?

BTW, I'm using Fedora, everything is current.

Amarok changes the metadata of a track if you use amarok to edit track details. The only things that are NOT written to the actual file are labels, covers, ratings and scores, and lyrics.

Can't offer any insight on your organisation... I've used the organise feature to move tens of thousands of mp3 tracks without losing metadata or destroying music. The only times anything has gone wrong, the metadata has been wrong in the first place.
Perhaps you could try a rescan before organising?

Ok yeah, I see now that Amarok was writing the tags. Still, for some reason the album is listed under the old name in the collection plane. A rescan does fix this.

A track was destroyed twice, but I can't reliably reproduce this, so it could be anything... I did actually organize 1000's of songs successfully, I only had problems after tagging, etc. I was curious if this ever happened to anyone else.

Sounds like a rescan glitch - is your music on a network share? there are occasionally issues with collection scanning if music is on a samba share, but these are generally related to the way the drive is mounted. nfs doesn't seem to have the same problems.

No. But my music is on a NTFS drive, and I'm using ntfs-3g. I know this isn't the best setup, but this is for my laptop which is a dual-boot with windows. It sounds like this is probably the source of the problem.

Edit #1:

Yes, apparently the drive is to blame, according to this:
http://forum.ntfs-3g.org/viewtopic.php? ... eac719ce49

Edit #2 (Solution):

After looking through the log I realized the the problem was indeed with the ntfs-3g driver. Actually the problem was with the actual files: The mp3s that were giving me trouble where compressed. I decompressed these files in windows and now Amarok works beautifully.