4 ms·
Or how about: anything I do in iTunes makes it freeze for five seconds. It's been explained to me that this is because my music collection is around 200GB, so
by crazygringo 15y ago
Or how about: anything I do in iTunes makes it freeze for five seconds.
It's been explained to me that this is because my music collection is around 200GB, so my iTunes Library.xml file is around 60MB, and any action (playing a song, renaming, etc.) rewrites the entire XML file on disk (incrementing play count, renaming, etc.).
And this is on a MacBook Air with SSD under Lion!
- evoxed 15y agoYep, this is extremely annoying. For an application that is supposed to catalog my library of media, it's quite inefficient with a large number of items. Without knowing what the possible solutions to this are, all I can say is that there needs to be a distinction between collections of media which are expected to be more reasonable in size (say an album, or one artist's catalog) and libraries which may grow to be quite huge. I have terabytes on external HDs that I won't let iTunes touch for a variety of reasons, leaving it pretty much no function other than to push things to the iPod or AppleTV.
- koenigdavidmj 15y agoWhose idea was it to use an XML file for a non-human-readable library file? SQLite would sing in this use case.
- derefr 15y agoThere's a regular (possibly SQLite-based) database format as well. The XML file is the backup.
- drivebyacct2 15y agoMy friends swear I'm an idiot, despite having written my own music library software because I couldn't stand the others, but I've had the same problem with iTunes being slow as shit. My initial import takes thousands of times the time it takes for other software to do the same thing and it has a nasty habit of "forgetting" where your library is if you don't leave it at the default. I love it, I just reloaded OS X and it keeps trying to start iTunes. Everytime I just deny the TOS and it slinks away. Good riddance.
- shinratdr 15y agoTechies that find iTunes so frustrating do amuse me. My iTunes library has been located in a non-default location since the original iTunes for OS 9. External drives, network locations, internal secondary drives, over the years my needs and requirements have changed. iTunes has worked in all those locations. My current library has a creation date of 2009. Initial import does take quite some time. Good thing I haven't had to do it since... well 2009 I guess. iTunes isn't the black box people make it out to be. iOS device management through iTunes is, I'm not even going to touch that one. However the regular library functions of iTunes are quite simple and keeping a library from being destroyed isn't difficult. > Good riddance. Still the best library based jukebox for OS X. I'm willing to put it up against any other option.
- ImprovedSilence 15y agoI've never had freezing/crashing/apocalyptic issues with iTunes on Win or OSX, but for a company that prides itself on user experience, iTunes leaves a lot to be desired. I pine for the day when a real Winamp gets on OSX, and not in that half assed form they came out with a few months ago. But maybe thats just cuz I'm old and set in my ways. Or maybe I just like a simple way to queue up some songs, or the ability to see 50 songs in my playlist, while only taking up a narrow side of my screen. But that's just the retro grouch in me... Your right as far as I know on your last point, not that I've done much searching, but I can hope there's something out there someday.
- deleted 15y ago[deleted]
- drivebyacct2 15y agoYes, many people have no problems with iTunes. However I find it amusing that people think the large population of the rest of us to be 'crazy' or some such because we all seem to experience the same problems and can reproduce them very easily. Itunes is the very definition of a black box. If you have an even slightly large library, it becomes a slow behemoth writing it's awkward binary-xml-shit files every time a change is made. And no offense, you did not move your library across all those spots without issue. It's frankly not possible. Moving those files causes iTunes to lose it's absolute references to them and you have to do a reimport.
- johnpowell 15y agoSince it is on a Air with a SSD I assume your library is on a external drive. Mine does the same since it is on a external USB HDD. On a internal SATA drive it is instant.
- crazygringo 15y agoMy music files themselves are on a network drive, but I keep the library files themselves on my SSD (as is recommended). So for file renames I understand, but not for playcounts or playlist changes or anything like that -- because those should access my SSD only, and not touch the external drive.
- shinratdr 15y agoI have to call shenanigans on this one. My music library is about 100GB and accordingly, my iTunes library XML is 31.2MB. My system operates on an SSD, but the entire iTunes DB is located on an internal 2TB hard drive, it's my slow one too. Never experienced this or anything close to this. It could be a bug related to libraries around 200GB or an XML file of over 60MB or something, but it's not directly because of the fact that iTunes re-writes the XML file when you make any change. That does happen, but it shouldn't lock up iTunes unless there is something wrong with your computer. Why? Because iTunes doesn't even use that XML file. It only exists to give 3rd party apps direct access to the iTunes library info. I can jump through my 20,700 song library, with the iTunes folder open watching it rewrite that XML file every time I do anything. No machine slowdown to speak of, on both a Mac Pro and an 11 inch MacBook Air where the library is in the same location as the system. I think there is something wrong with your machine. This would drive me absolutely insane, and I use iTunes every single day for hours a day, almost without exception.