Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
What can't be confirmed? That iTunes can't distinguish different versions of the same song and replace it with whatever it have available? Older/newer/concert/remix etc. If it can't then it's not a "match".

iTunes Music can't distinguis different artist using same name, it lists them as one artist.

User error, my ass.

Failure to match correctly isn't the issue at hand here. The issue is matching failures or other issues in the iCloud Library getting written back to the local, primary library, which should never happen, and would be a serious bug.

The fact that some, possibly you, aren't able to make the distinction between their cloud library and the local one, is a failure of Apple's doing, is provably real, and would explain many problems users are having. The serious bug, doesn't need to exist, even though I don't doubt Apple are capable of writing such a thing.
 
  • Like
Reactions: xoAnna
Really? "You're holding it wrong!" never happened, right?

That problem came from Steve wanting a revolutionary design for the iPhone 4. iTunes deleting people's music is just poor software...

I don't know why people keep laughing at the "Steve would never have allowed this" comments. If you followed Apple under Steve Jobs, surely you realise there's an element of truth to that. Steve cared about making great products, where as Cook only cares about the business side of things.

This video sums up Apple's current situation

 
Last edited:
Apple are at fault no matter what. They don't make this stuff clear. In the information vacuum people make assumptions based in how other services work. Anybody who's made this error I don't blame one bit.

Apple has always clearly stated that iTunes Match only uploads music files that aren't matched by the software to iTunes music store content, and that the cloud matching service requires the $24.95 per year. I think what a lot of people actually do is use the cloud streaming for most the year, then rush to download the matches (because you can keep those permanently without the iTunes Match subscription) right before the subscription expires. Then they make mistakes with the downloaded matched content vs. their original files after Match has expired.
 
  • Like
Reactions: xoAnna
I'm not sure I understand your post - the headline states that the deletion glitch is confirmed, and the quoted text says the same thing

Headline: Apple Confirms Music Deletion Glitch...

Quote from Apple: "In an extremely small number of cases users have reported that music files saved on their computer were removed without their permission..."

One of these headlines tells us something new and dramatic. And one of them is true. Which is which?

Headline: Apple Confirms Reports of Music Deletion

Headline: Apple Confirms Music Deletion Glitch

Regardless of what you believe to be afoot, the news story is about the Apple statement, and the statement is quiet clear that no glitch has been found or fixed.
 
  • Like
Reactions: notrack
Maybe itunes knows what it must be deleted. What if this user had a folder with the entire paula Abdul's discography? I call this 'justice'.
 
This is one of the reasons why I have absolutely no interest in Apple Music, their matching service or iCloud. I keep my music on my drive locally and pull it into iTunes in referenced mode (I do not let iTunes sort my music).
 
It doesn't say if that deleted music can ever be recovered - or did I miss that?

Probably can be recovered if you use Time Machine. As you should.

If not, can your music be recovered if your MacBook is stolen? Or if it breaks, which one day it will? (I wonder how many people buy a laptop and use it until it breaks).
 

Probably can be recovered if you use Time Machine. As you should.

If not, can your music be recovered if your MacBook is stolen? Or if it breaks, which one day it will? (I wonder how many people buy a laptop and use it until it breaks).
But none of those are because of a programming issue.
 
Failure to match correctly isn't the issue at hand here. The issue is matching failures or other issues in the iCloud Library getting written back to the local, primary library, which should never happen, and would be a serious bug.
But it happens.
 
With this statement Apple confirms nothing. "Safe guards" sounds more like better wording in dialog boxes and maybe more of them too.
 
More like people would simply have given Apple a free pass under Steve Jobs. Products and services were never perfect nor bug free under Steve Jobs. Bad things happen. Live with it.

While that is undoubtedly true, it was also true that releasing obvious bugs was not the way to get on Jobs good side. Cook seems to be very nice and we just don't hear about irrational behavior regarding Cook. I just get the impression that when confronted with a serious bug Cook's response is something like, "Oh well, another bug. Bugs can't be prevented, so how was your holiday?"

That's the difference.
 
I've had it recently were three times, iTunes has deleted entire content in a favourite playlist on my MacBook. Not sure if it's my iPhone at fault or iTunes. But scary. Now I make a copy of every favourite playlist!
 
  • Like
Reactions: xoAnna
But that's a rather hacky approach to it. I believe in trying to find the root cause, even if I have to sit for hours stepping through code. Eventually I do, and it is something very simple and very easily over sighted. The end result in fixing it is much better, nicer, and cleaner, and avoids the constant loading on of needless subroutines to check for something, that is probably as small as someone using I instead of j.
That's nice if it works. But sometimes you just can't reproduce it. Because a problem happens only if certain conditions are met that have nothing whatsoever to do with the actual problem. You might have a bug that deletes songs but only if the last album in your library has more than 25 songs. That's probably something that would hit less than 1% of users.
[doublepost=1463227632][/doublepost]
What unique situations?
If Apple knew that, it would easy to fix the problem. I've had crashes that would only happen after six o'clock in the afternoon. I've had crashes that would only happen if your hard drive had a name with an odd number of characters. I've had a crash that only happened when you picked one particular shade of blue in a colour picker for some text. There were 256 colours to pick, and one of them crashed. All others worked fine.
[doublepost=1463227942][/doublepost]
But none of those are because of a programming issue.
So what? There are lots of different ways to lose your music, and people who have their laptops stolen will not come to MacRumors and complain about it. The only way to be save is to have a backup.
 
  • Like
Reactions: DiceMoney
That problem came from Steve wanting a revolutionary design for the iPhone 4. This bug is just a result of poor software...

I don't know why people keep laughing at the "Steve would never have allowed this" comments. If you followed Apple under Steve Jobs, surely you realise there's an element of truth to that. Steve cared about making great products, where as Cook only cares about the business side of things.

This video sums up Apple's current situation

While a lot of people seem to what to laugh at the "Steve would never have allowed this" comments, they seem to forget that Steve DIDN'T allow a lot of issues to be there, and did everything possible to make sure that Apple products were GREAT to use and as reliable as possible. Apple didn't get everything right under his leadership, but they did get things right MOST of the time. It certainly wasn't a situation where almost every software release had major bugs in it like today, or products were released with half finished operating systems (the Apple Watch).
 
While that is undoubtedly true, it was also true that releasing obvious bugs was not the way to get on Jobs good side. Cook seems to be very nice and we just don't hear about irrational behavior regarding Cook. I just get the impression that when confronted with a serious bug Cook's response is something like, "Oh well, another bug. Bugs can't be prevented, so how was your holiday?"

That's the difference.
How do we know that the people responsible aren't being taken to task for this issue?

Imagine you made a mistake at work. Would you like news of you being castigated by your boss making the news at 9? Companies typically project a united front to the public, but I am certain appropriate actions are being taken behind the scenes to rectify the mistake. It's how a company gets its act together and reacts calmly to a crisis that shows the effectiveness of its leadership, not just who can shout the loudest.

You can never have 100% bug-free software. If anything, blame Apple's insistence on sticking stubbornly to their annual software update cycle. With their hands full just rushing to push new software features on time, it's inevitable that bugs will slip through (or deemed not serious enough that Apple can close one eye and afford to fix it at a later date).

Ultimately, if you want someone to blame, it starts at the top.
 
Bugs happen although ones that unpredictably delete files should never get pass QA.
It is possible that a bug deletes files but only under particular circumstances. When you say "unpredictably" you mean "under particular circumstances, but I cannot figure out which circumstances". It is entirely possible that nobody in QA will ever create exactly the circumstances that are needed to reproduce the problem.
 
I still think it's more likely it was human error. Just my opinion.

As for losing data, I don't understand why anyone would not have 2 or 3 secure backups of anything important. Drives and cloud services are very cheap now.
 
Apple says they weren't able to recreate this. How can they fix a "bug" they can't re-create?
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.