3 ms·

> 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 probl

> 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. That's not the reason. It's because you choose to bitch about them instead of attempting to solve them, even though they are completely solvable problems that don't happen in a clean setup. Reproducing means nothing, except that you didn't bother to try and solve the problem. > 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. This is just patently false. See my other comment for a detailed explanation. Long and short of it is iTunes doesn't even use the XML file, it exists for 3rd party apps to use. If your machine locks up every time a 30MB file is written (written, not even accessed) then there is something wrong with your storage media, not iTunes. Perhaps you have some sort of 3rd party syncing app that immediately accesses the iTunes XML every time it is re-written? That's more likely than Apple not noticing that their media player locks up every time when accessing a large library. > And no offense, you did not move your library across all those spots without issue. Hard to take offence to something I didn't say. My iTunes library has existed on all of those locations at one time or another, it wasn't the same library every time. Like I said, last time I recreated it was in 2009. It still existed in those locations and didn't randomly reset itself as you claim. > 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. Oh no! Exclamation marks everywhere! Click the song, browse to the song, iTunes asks if you want to check the folder for any other references. 5 minute scan later, all pointers are fixed. It's not only possible, it's dead simple. It's almost like you could have discovered that with a simple Google search. Or hell, just actually trying instead of jumping immediately to whining.

drivebyacct2 15y ago
Again, I love the fact that you, just like the people I talked about in my first fucking comment, treat me like I'm stupid, despite the fact that I know what I'm doing (hell, enough to reproduce 90% of iTunes's features in my own media library/player). You even imply that I run to whinning instead of Googling. Why don't you Google these issues. You'll find dozens of other people with the exact same issue. You wasted a lot of effort typing that reply. One of my more infuriating replies I've gotten here. edit: Annnnnd a quick look at your other comments in this thread tell me everything I need to know. You're even running around telling other people describing the exact same problem and acting like they're crazy. You realize that something working for you doesn't mean it's bug free, right? My media library takes an arbitrary number of sources, takes 2 minutes to parse my library, works with more file formats, doesn't store an incomprehensible, incompatible format that no one else can write, doesn't require inane Terms of Service and more. I'm very, very happy that iTunes works for you. For a ton of people, it's a damn headache.
- shinratdr 15y ago
  > Again, I love the fact that you, just like the people I talked about in my first fucking comment, treat me like I'm stupid, despite the fact that I know what I'm doing I treat you like you're stupid because you present stupid little issues as insurmountable problems. > (hell, enough to reproduce 90% of iTunes's features in my own media library/player) Programmers IMO are some of the worst for jumping to "I can do this better!" instead of again attempting to solve the problem. > You even imply that I run to whinning instead of Googling. Why don't you Google these issues. You'll find dozens of other people with the exact same issue. I don't imply it, I say it. Because you do. Also, Google offers the EXACT same solution: Clean up your machine because if it can't write a 30mb file that isn't even being read without locking up, there is something wrong with it. > You wasted a lot of effort typing that reply. Personally I think it was used perfectly. > One of my more infuriating replies I've gotten here. Yeah, being challenged on your BS can be frustrating. I'm glad I could be a part of that. > Annnnnd a quick look at your other comments in this thread tell me everything I need to know. You're even running around telling other people describing the exact same problem and acting like they're crazy. You call it crazy, I call it lazy. Whatever, it's still bitching over fixing. I'm not calling them crazy for having the problem, I'm calling them lazy for having the problem for so long and just bitching about it instead of doing something about it. > You realize that something working for you doesn't mean it's bug free, right? Of course, just because something isn't working on a particular setup doesn't mean its bug-ridden either.
  - drivebyacct2 15y ago
    >I don't imply it, I say it. Because you do. >Why don't you Google these issues. You'll find dozens of other people with the exact same issue. You're a stupid little fuck, aren't you. I DID Google them instead of whining first. You really think I sunk probably a hundred hours into writing something purely from scratch before Googling. Good god how can you breath with your head that far up Apple's ass? >Of course, just because something isn't working on a particular setup doesn't mean its bug-ridden either. And we've always been at war with Oceania.
    - 15y ago
crazygringo 15y ago
> Long and short of it is iTunes doesn't even use the XML file, it exists for 3rd party apps to use. If your machine locks up every time a 30MB file is written (written, not even accessed) then there is something wrong with your storage media, not iTunes. It doesn't matter that iTunes doesn't read the XML file. Any machine will take at least a couple seconds to write out an entire 30MB file. And if it does this every single time you update a playcount or rename a playlist, and blocks your user interface during this, then there's a fundamental flaw with the software.
- shinratdr 15y ago
  > It doesn't matter that iTunes doesn't read the XML file. Yes, it does. > Any machine will take at least a couple seconds to write out an entire 30MB file. True, but if it's locking up iTunes every time that occurs then THERE IS SOMETHING WRONG WITH YOUR MACHINE OR SETUP. End of story. > And if it does this every single time you update a playcount or rename a playlist, and blocks your user interface during this, then there's a fundamental flaw with the software. No doubt. Since that doesn't actually happen, there isn't such a fundamental flaw.

drivebyacct2 15y ago

Again, I love the fact that you, just like the people I talked about in my first fucking comment, treat me like I'm stupid, despite the fact that I know what I'm doing (hell, enough to reproduce 90% of iTunes's features in my own media library/player). You even imply that I run to whinning instead of Googling. Why don't you Google these issues. You'll find dozens of other people with the exact same issue. You wasted a lot of effort typing that reply. One of my more infuriating replies I've gotten here. edit: Annnnnd a quick look at your other comments in this thread tell me everything I need to know. You're even running around telling other people describing the exact same problem and acting like they're crazy. You realize that something working for you doesn't mean it's bug free, right? My media library takes an arbitrary number of sources, takes 2 minutes to parse my library, works with more file formats, doesn't store an incomprehensible, incompatible format that no one else can write, doesn't require inane Terms of Service and more. I'm very, very happy that iTunes works for you. For a ton of people, it's a damn headache.

shinratdr 15y ago
> Again, I love the fact that you, just like the people I talked about in my first fucking comment, treat me like I'm stupid, despite the fact that I know what I'm doing I treat you like you're stupid because you present stupid little issues as insurmountable problems. > (hell, enough to reproduce 90% of iTunes's features in my own media library/player) Programmers IMO are some of the worst for jumping to "I can do this better!" instead of again attempting to solve the problem. > You even imply that I run to whinning instead of Googling. Why don't you Google these issues. You'll find dozens of other people with the exact same issue. I don't imply it, I say it. Because you do. Also, Google offers the EXACT same solution: Clean up your machine because if it can't write a 30mb file that isn't even being read without locking up, there is something wrong with it. > You wasted a lot of effort typing that reply. Personally I think it was used perfectly. > One of my more infuriating replies I've gotten here. Yeah, being challenged on your BS can be frustrating. I'm glad I could be a part of that. > Annnnnd a quick look at your other comments in this thread tell me everything I need to know. You're even running around telling other people describing the exact same problem and acting like they're crazy. You call it crazy, I call it lazy. Whatever, it's still bitching over fixing. I'm not calling them crazy for having the problem, I'm calling them lazy for having the problem for so long and just bitching about it instead of doing something about it. > You realize that something working for you doesn't mean it's bug free, right? Of course, just because something isn't working on a particular setup doesn't mean its bug-ridden either.
- drivebyacct2 15y ago
  >I don't imply it, I say it. Because you do. >Why don't you Google these issues. You'll find dozens of other people with the exact same issue. You're a stupid little fuck, aren't you. I DID Google them instead of whining first. You really think I sunk probably a hundred hours into writing something purely from scratch before Googling. Good god how can you breath with your head that far up Apple's ass? >Of course, just because something isn't working on a particular setup doesn't mean its bug-ridden either. And we've always been at war with Oceania.
  - 15y ago

crazygringo 15y ago

> Long and short of it is iTunes doesn't even use the XML file, it exists for 3rd party apps to use. If your machine locks up every time a 30MB file is written (written, not even accessed) then there is something wrong with your storage media, not iTunes. It doesn't matter that iTunes doesn't read the XML file. Any machine will take at least a couple seconds to write out an entire 30MB file. And if it does this every single time you update a playcount or rename a playlist, and blocks your user interface during this, then there's a fundamental flaw with the software.

shinratdr 15y ago
> It doesn't matter that iTunes doesn't read the XML file. Yes, it does. > Any machine will take at least a couple seconds to write out an entire 30MB file. True, but if it's locking up iTunes every time that occurs then THERE IS SOMETHING WRONG WITH YOUR MACHINE OR SETUP. End of story. > And if it does this every single time you update a playcount or rename a playlist, and blocks your user interface during this, then there's a fundamental flaw with the software. No doubt. Since that doesn't actually happen, there isn't such a fundamental flaw.