I have read several postings where a problem was reported that certain tracks' tags could not be updated. I have had this problem persistently and finally was motivated to solve the problem (at least for my library). I have about 16,000 tracks and about 2/3 of them are classical music. As per classical titles, the names are frequently verbose. When the file name + path exceeds the NTFS limit (and probably the same thing happens with FAT32), the tags cannot be written out to the file.
When I shortened file names on the hard drive, the problem was solved. However, this process pointed out the need for a 'YAFF' (yet another frivolous feature?). It would be great for those of us who use players such as the Archos or move content between machines in general, to have a combines update/reimport function in the library manager. Since some players (Archos, eDigital Odyessy, etc) do not read tags but read folder name/ file name for accessing content, it is helpful to store MC9 tracks in some kind of folder hierachy. This is also helpful when one has a large and complex library of music jsut to keep order in the relm.
The current workflow for my library is if I move folders around or rename files or fix anything that changes the physical database of tracks, I need to run "update library" to purge the old name and then run "import media" to recover renamed or moved content into the library. It would be great if a variation of "update library" would find and remove entries that are missing as well as discover new content to be entered (maybe call it "adjust library"?). If the update function got really cleaver, it could read a unique ID for each track and notice that only its physical location or file name changed and update the MC9 indexing as needed?
Author
Topic: Why some tags do not update... (Read 1763 times)