The only options that seem to work are to double-click them one by one or to "Consolidate Library", which could move the Library to an entirely different location in the process. Secondly, once a lot of files have been marked by the dreaded exclamation mark, it's quite difficult to get rid of them. ![]() In this case iTunes should have waited for the OS to signal a timeout connecting to the NFS share on my server, but it timed out quite before that (the OS never reported any issues connecting to the share). The bug(s) remain however.įirst of all, it appears that iTunes uses an internally specified timeout to determine whether a music file is available or not, regardless whether the resource it's on is controlled by the OS or not. In the meantime, what's the most efficient workaround?Īfter upgrading my server OS (from FreeBSD 6.3 to 7.2) the symptoms are gone. To fix the exclamation marks I need to open my entire iTunes library and double click several thousand files! Over time more and more songs in my library get incorrectly marked as "not available", causing my background music to become less and less varied. However, it marks several other songs as "not available" behind my back, which I don't see it doing as I usually use the iTunes DJ. ![]() ![]() If I double-click it after it did that it plays it alright and unmarks it, so it looks like an innocent problem. I have seen this issue with older versions as well, but not since a long time (more than a year I think).Įvery time I haven't played any music for a while (for example the next morning) iTunes marks the current song as "not available" (the dreaded exclamation mark). That works great, except for the problem I'm describing here which started to occur since the last iTunes update. I have my iTunes library on a remote NFS share on my home LAN.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |