The 24" white iMacs were pretty well lemons*. I unfortunately bought two with identical overheating issues and the forums were full of people with exactly the same issue, Apple never owned up anything.
And yes Apple is reluctant to say anything until it knows what the issue is or has a fix, but I'd add to that also not until it is forced to do something about it. Sometimes massive consumer complaints extracts a fix/apology, sometimes it takes a court case.
* Not the only ones, but having multiple units made the problems much clearer.
That's not really true though. First, we don't know what this problem is. Is it Apple's or is it the software these lRticular people are using? I've had problems with third party software over the years that caused machines to crash consistently. So if the problem is seen to be coming from the software on,y, then it may not be an Apple problem at all. It's difficult to tell.
OSX is supposed to prevent problems like this with its sandboxing. For years I haven't even had the software kill keyboard shortcut do anything.
Command full stop also does practically nothing in OSX.
Lately I have had Safari totally lock up my Mac, forcing me to hard reboot.
Either way it is a problem affecting people's work. As has been pointed out it is the death of a thousand cuts as Apple trashes the software that professionals use, then slips the remaining few, who have stuck with Apple's solutions, expensive hardware that trashes their work. Whatever the cause, it seems the way to avoid it is to avoid Apple as a supplier.
I bagged my brother's old Dell laptop the other day and he pointed out it never ever has given him any grief, unlike his neighbour's Mac. Trouble is we patch the problems with excuses and too easily let Apple off the hook.
OSX is supposed to prevent problems like this with its sandboxing. For years I haven't even had the software kill keyboard shortcut do anything.
Command full stop also does practically nothing in OSX.
Lately I have had Safari totally lock up my Mac, forcing me to hard reboot.
Either way it is a problem affecting people's work. As has been pointed out it is the death of a thousand cuts as Apple trashes the software that professionals use, then slips the remaining few, who have stuck with Apple's solutions, expensive hardware that trashes their work. Whatever the cause, it seems the way to avoid it is to avoid Apple as a supplier.
I bagged my brother's old Dell laptop the other day and he pointed out it never ever has given him any grief, unlike his neighbour's Mac. Trouble is we patch the problems with excuses and too easily let Apple off the hook.
Unfortunately, sand boxing is just for memory protection. It doesn't do anything for other basic problems. Sand boxing for iOS is different from what OS X, Windows and other major computer OSs do.
Well, look at where Dell is these days, and you will see why their failing company needed to go private. Dell is not a high quality supplier. I could tell you Dell tales that would curl your toes, but you probably don't want to know any of that.
Need I mention that almost every system update from me over the past few years has borked up Windows machines in one way or the other, and needed to be recalled? I can Liu t to many other problems from other systems. So no, Apple isn't nearly in the same boat as those. You're trying to make it seem as though Apple problems are the norm for them rather than the exception. They are not.
I have had a fully maxed out late 2013 Mac Pro since mid-January of this year. Until Apple issued a software update, I had random horizontal lines in both playback and render of projects in Adobe's Premiere Pro CC. The update solved those problems for me, but based on several posts in the Adobe Premiere Pro Forum the software update did not solve the problem for everyone, and to this day there are occasional posts by people having a rendering problem with Adobe Premiere Pro CC. I also have Resolve 11 installed on this Mac Pro. I have used it infrequently and to date I have not had a problem, but once again I respect the fact that a number of posts on both the Apple Mac Pro Forum and other forums are reporting rendering problems with Resolve 11.
I purchased my late 2013 Mac Pro for the purpose of doing 4K video editing in Final Cut Pro X. The 2013 Mac Pro was optimized for this, and it works beautifully with that software. I am able to handle multiple 4K video streams with no problem, and renders are fast and flawless. I love my 2013 Mac Pro for its speed, small footprint, and quiet performance. I have never experienced any temperature issues even when doing 3D modeling or 3D animation work or working with 4K video in FCP X. This is a great computer -- perhaps the finest that Apple has ever released.
With the above said, I am glad that Appleinsider has posted this article. There are too many reports of problems with the late 2013 Mac Pro using Adobe Premiere Pro CC and Resolve 11 for this to simply be ignored. These are professional applications that many people depend upon for their living. I am hopeful that Apple is working with AMD, Adobe and BMD to solve this issue and correct it. This has gone on too long (since at least May of this year) to be ignored.
Tom
Like you all the way and I think Adobe et al need to get their act together to make sure their software runs as well as Apple's on the nMac Pro. Not that Adobe exactly has a history of stepping up to support Apple since the days they were 100% Apple ... :no:
Like you all the way and I think Adobe et al need to get their act together to make sure their software runs as well as Apple's on the nMac Pro. Not that Adobe exactly has a history of stepping up to support Apple since the days they were 100% Apple ...
Adobe was a very strong Apple supporter up until Apple sprang TrueType on them out of the blue at a launch they had invited John Warnock to attend.
You should have seen the look of shock and betrayal on Warnock's face. That was when Adobe decided Apple was a 'friend' best kept at a distance.
Yes it is an Apple problem. They choose the supplier and we as consumers get no say in that choice and no way to rectify the problems that that choice causes. If it was a PC you'd rip out the faulty part and replace it. But it is a Mac. What can you do?
Apple even solders or glues in elementary parts now, to make the difficult impossible.
THAT is all Apple!
If Apple can wear the responsibility for what it gets right, how does it not wear the responsibility for what it gets wrong.
Lets not forget all the deadend technologies they took their users down over the years.
You really are overdoing this. No one knows what this problem is yet, or even that it has anything directly to do with Apple, and yet, you are jumping to lay the blame on them. Shame!
You couldn't rip all of those hundreds of thousands of boards out of the laptops of pc manufacturers, which were where most of the problems ensued from, or from the one board pcs where this sub board was soldered in. Please, don't make claims about something about which you seems to know little. Apple repaired every one of their machines, even though they were years out of warrantee.
This problem is still an unknown, but, Apple is replacing every board, even though it may not even be their problem at all. That's standing behind your customer pretty well. At some point, the problem will be found. But if it has nothing to do with Apple and is entirely due to Discreet, what do want to see happen then?
Adobe was a very strong Apple supporter up until Apple sprang TrueType on them out of the blue at a launch they had invited John Warnock to attend.
You should have seen the look of shock and betrayal on Warnock's face. That was when Adobe decided Apple was a 'friend' best kept at a distance.
Adobe was a very strong supporter of Apple, and Apple was a very strong supporter of Adobe, actually, the reason why Adobe succeeded at all, until Apple's sales began to falter after the incompetent Michael Spindler made a couple of major blunders that had it appear that Apple might go under, and Adobe decided to port their software over to Windows, and then decided to support Windows by refusing to support Mac hardware and software features so that their software would be "feature equivalent" across platforms. This was purely a defensive move made because Adobe was afraid their market might disappear.
The nonsense about Truetype is just that, nonsense. TrueType wasn't an Apple thing, it was an Apple and Microsoft thing. They both invented this together. Both were ticked at Adobe for keeping the Type 1 specs for themselves, which allowed proper kerning, among other things, and just allowing developers to use Type 3 for their own fonts, which left Adobe with a major quality advantage. TrueType forced Adobe to open that spec up.
But it wasn't an Apple surprise. Both Apple and Microsoft were involved, and both were at the release announcement.
Unfortunately, sand boxing is just for memory protection. It doesn't do anything for other basic problems. Sand boxing for iOS is different from what OS X, Windows and other major computer OSs do.
Well, look at where Dell is these days, and you will see why their failing company needed to go private. Dell is not a high quality supplier. I could tell you Dell tales that would curl your toes, but you probably don't want to know any of that.
Need I mention that almost every system update from me over the past few years has borked up Windows machines in one way or the other, and needed to be recalled? I can Liu t to many other problems from other systems. So no, Apple isn't nearly in the same boat as those. You're trying to make it seem as though Apple problems are the norm for them rather than the exception. They are not.
You are looking at this through your one good "Apple" eye?
I have personally had 6 Macs with major problems, two had to eventually be recalled, and that did not count the many I had in studios which plagued us with all sorts of minor issues. That does not make me pick on Apple at all, just I can not let the Apple exceptionalism pass.
I have had much fewer PCs so not such a large sample, not without problems, but they were cheaply and quickly fixed, so didn't fester.
Dell still sells vastly more computers than Apple and higher end models as well. That it sells them cheaply and still does so so successfully shows they are just in a different market than Apple. My view is Dell's inferior rating is over stated, as is Apple's superior rating. That does not mean I would buy a Dell over an Apple, it is also no comfort to my brother's neighbour or anyone who has a problem with their purchase.
Adobe was a very strong supporter of Apple, and Apple was a very strong supporter of Adobe, actually, the reason why Adobe succeeded at all, until Apple's sales began to falter after the incompetent Michael Spindler made a couple of major blunders that had it appear that Apple might go under, and Adobe decided to port their software over to Windows, and then decided to support Windows by refusing to support Mac hardware and software features so that their software would be "feature equivalent" across platforms. This was purely a defensive move made because Adobe was afraid their market might disappear.
The nonsense about Truepe is just that, nonsense. TrueType wasn't an Apple thing, it was an. Apple and Microsoft thing. They both invented this together. Both were ticked at Adobe for keeping the Type 1 specs for themselves, which allowed proper keening, among other things, and just allowing developers to use Type 3 for their own fonts, which left Adobe with a major quality advantage. TrueType forced Adobe to open that spec up.
But it wasn't an Apple surprise. Both Apple and Microsoft were involved, and both were at the release announcement.
TrueType was an Apple invention, not Microsoft's, which Apple stupidly licensed to Microsoft in exchange for an equivalent non-Postscript printer language TrueImage, that Microsoft delivered late and which never went anywhere.
TrueType was developed in the late 1980s and was released with System 7 in 1991.
Michael Spindler didn't even become CEO of Apple until 1993.
I remember the launch and from memory John Warnock was close to tears.
Quality control in both hardware and software seems to have gone down since Steve Jobs died. Tim Cook needs to make fixing this first a top priority before it becomes ingrained in the brand instead of releasing new products at a fast pace.
Yeah ... Maybe Tim needs to do what Steve did ... Tell 'em they're holding it wrong!
Just looked up the details in case my memory was failing.
TrueType was announced at the 1989 Seybold conference. Apparently Adobe's Geschke found out about TrueType just 2 days before when he spoke to Bill Gates about licensing ATM. But I distinctly remember how upset Warnock was at the conference.
I consider myself very level headed when it comes to tech, because there is not one perfect device on the market. But I have to be honest and acknowledge that I've lost a little trust with Apple. If we're only looking at Apple compared to everything else on the market, then it's quite easy to say that comparatively they are the best and that the things we have to worry about are nowhere near what you have to worry about with other devices. But if we're comparing Apple to their own standard, which is what I care more about, there have been some things over the past year or two that have my worrying about things that I very seldom had to worry about before. I'm often scared to update now for fear that updates are going to completely break things, some with no support to fix. That's not just on computers, but iOS devices, airport routers and ATV. Every update to Airports over the last two years has made the routers worse. It's hard telling everyone around me to switch to Apple devices because they "just work," and then getting a million calls when things "just don't work." Normal end users are quick to blow things way out of proportion and I hate dealing with the blow back of trying to explain why it's not that big of a deal because Apple is usually pretty good about fixing things. I'm not freaking out, but I do not think that people are just complaining about nothing. Apple is having some quality control issues that they need to clean up and restore a little faith in it's users...
Well reasoned and well said!
My current disappointment is iTunes ... It's gone from "It just works" -- to It just sucks!
Just looked up the details in case my memory was failing.
TrueType was announced at the 1989 Seybold conference. Apparently Adobe's Geschke found out about TrueType just 2 days before when he spoke to Bill Gates about licensing ATM. But I distinctly remember how upset Warnock was at the conference.
None of which changes the fact that Adobe's insistence on keeping Type 1 proprietary was the reason for the development of TrueType. Warnock's subsequent whining and belated release of Type 1 notwithstanding.
It was their business, and Apple did knife them in the back, with no warning. They didnt even hear about it from Apple, they got the tiniest of warnings of what was going to happen to them from Bill Gates. At the time it was apparent that no-one at Apple had even considered how this would affect Adobe. For Apple the only thought is themselves, not out of any meanness, just there isn't anyone else.
Fortunately Adobe had Photoshop as their next best thing.
Was Apple "whining" when Adobe rightly saw Apple as unreliable and moved to Windows, which as it turned out stopped Adobe going bust and secured Adobe's future?
I am saying this with no particular attachment to Adobe. I have been working at extricating myself from their software over the last 5 years and will be very happy when I no-longer need to use Illustrator/Photoshop/Indesign/Acrobat again.
With all due respect, because these problems should really be resolved more quickly by Apple and the software developer.
When a business relies on something like a piece of software and a workflow - it's standard professional practice to do the following: 1. Run a test unit before upgrading other machines 2. Contact the software developer prior to upgrading to learn of any documented bugs with the new version 3. Read the release notes provided by Apple
Just because a software update becomes available doesn't mean that staff should have the ability to apply it the same day. In professional business, no one ever installs software blindly hoping for the best.
Apple release security updates separately for many reasons including this.
After working for Apple for nearly 10 years isolating and resolving issues like this, all I can say is - "do not buy a first generation build of a new product or major design refresh V1.0". That said, one needs to put things into perspective. Out of the 100.000's of Mac Pros sold "Only a few dozen complaints have surfaced in the wild".
- Applecare will run the numbers and be initially told (By AppleCare Engineering) to try a video card or board replacement. Upon realising (3 replacements in) that it does not resolve the issue, an internal notification will finally be sent (By AppleCare Engineering) listing it as a "known issue". i.e.: At which point offers to replace boards and machines will probably cease. (Think iMac screen condensation). Will most likely need a firmware update.
- As to the comment about quality control slipping under Cook, thats absolute rubbish. Quality control has improved year on year since Cook came on board. Some absolute shocking releases under Jobs and actually it was not Jobs fault, it was a simply the way the company was structured back then and they way products were rolled out and how early reports of faults were received, processed and addressed. Or in some cases, not addressed for months / years. Oh and oh course the odd design shocker.
At the end of the day, based on the time line (refresh pending) and the extremely low volume of complaints, it will be low on the list of things to do, but there will be someone working on it. A number of years back I worked on an audio playback issue with the Mac Pro (Not listing year). Only one customer picked it up, but he was a squeaky wheel. Anyway, secured a NDA with the customer and worked though with Engineering (Not Applecare Engineering - There is a major difference), and eventually resolved the issue about 6 months later. Worldwide firmware update finally released.
What I learnt from that process is that it was a "known issue" prior to release, however the probability of the required set of circumstances being used and implemented by the customer to reproduce it was like 0.00002 percent.
I am currently using the last Mac Pro tower with Resolve and a bunch of other BMD gear for editing RED 4K. It struggles. Tempted to get the new Mac Pro ... but have been holding out for exactly the reasons listed in this article. Will go for the 2015 model. Will it be perfect - no, but it certainly won't be like a water-cooled G5 - anyone remember that awesome piece of brilliantly designed engineering? Was that released under Cooks watch?
Comments
The 24" white iMacs were pretty well lemons*. I unfortunately bought two with identical overheating issues and the forums were full of people with exactly the same issue, Apple never owned up anything.
And yes Apple is reluctant to say anything until it knows what the issue is or has a fix, but I'd add to that also not until it is forced to do something about it. Sometimes massive consumer complaints extracts a fix/apology, sometimes it takes a court case.
* Not the only ones, but having multiple units made the problems much clearer.
That's not really true though. First, we don't know what this problem is. Is it Apple's or is it the software these lRticular people are using? I've had problems with third party software over the years that caused machines to crash consistently. So if the problem is seen to be coming from the software on,y, then it may not be an Apple problem at all. It's difficult to tell.
OSX is supposed to prevent problems like this with its sandboxing. For years I haven't even had the software kill keyboard shortcut do anything.
Command full stop also does practically nothing in OSX.
Lately I have had Safari totally lock up my Mac, forcing me to hard reboot.
Either way it is a problem affecting people's work. As has been pointed out it is the death of a thousand cuts as Apple trashes the software that professionals use, then slips the remaining few, who have stuck with Apple's solutions, expensive hardware that trashes their work. Whatever the cause, it seems the way to avoid it is to avoid Apple as a supplier.
I bagged my brother's old Dell laptop the other day and he pointed out it never ever has given him any grief, unlike his neighbour's Mac. Trouble is we patch the problems with excuses and too easily let Apple off the hook.
HAHAHAHAHA
That's right, Apple gets a free pass on everything while everyone else gets every minor CE issue on a thousands websites and news channels¡ :rolleyes:
Unfortunately, sand boxing is just for memory protection. It doesn't do anything for other basic problems. Sand boxing for iOS is different from what OS X, Windows and other major computer OSs do.
Well, look at where Dell is these days, and you will see why their failing company needed to go private. Dell is not a high quality supplier. I could tell you Dell tales that would curl your toes, but you probably don't want to know any of that.
Need I mention that almost every system update from me over the past few years has borked up Windows machines in one way or the other, and needed to be recalled? I can Liu t to many other problems from other systems. So no, Apple isn't nearly in the same boat as those. You're trying to make it seem as though Apple problems are the norm for them rather than the exception. They are not.
Like you all the way and I think Adobe et al need to get their act together to make sure their software runs as well as Apple's on the nMac Pro. Not that Adobe exactly has a history of stepping up to support Apple since the days they were 100% Apple ... :no:
I had to put my glasses on there .. I wish you'd use /s, I get a scare with that damn tiny thingy ...
I take it you think we are singling out Apple on this, and you are sweeping this one under the carpet.
Must be a very lumpy carpet at your place.
Like you all the way and I think Adobe et al need to get their act together to make sure their software runs as well as Apple's on the nMac Pro. Not that Adobe exactly has a history of stepping up to support Apple since the days they were 100% Apple ...
Adobe was a very strong Apple supporter up until Apple sprang TrueType on them out of the blue at a launch they had invited John Warnock to attend.
You should have seen the look of shock and betrayal on Warnock's face. That was when Adobe decided Apple was a 'friend' best kept at a distance.
You really are overdoing this. No one knows what this problem is yet, or even that it has anything directly to do with Apple, and yet, you are jumping to lay the blame on them. Shame!
You couldn't rip all of those hundreds of thousands of boards out of the laptops of pc manufacturers, which were where most of the problems ensued from, or from the one board pcs where this sub board was soldered in. Please, don't make claims about something about which you seems to know little. Apple repaired every one of their machines, even though they were years out of warrantee.
This problem is still an unknown, but, Apple is replacing every board, even though it may not even be their problem at all. That's standing behind your customer pretty well. At some point, the problem will be found. But if it has nothing to do with Apple and is entirely due to Discreet, what do want to see happen then?
Adobe was a very strong supporter of Apple, and Apple was a very strong supporter of Adobe, actually, the reason why Adobe succeeded at all, until Apple's sales began to falter after the incompetent Michael Spindler made a couple of major blunders that had it appear that Apple might go under, and Adobe decided to port their software over to Windows, and then decided to support Windows by refusing to support Mac hardware and software features so that their software would be "feature equivalent" across platforms. This was purely a defensive move made because Adobe was afraid their market might disappear.
The nonsense about Truetype is just that, nonsense. TrueType wasn't an Apple thing, it was an Apple and Microsoft thing. They both invented this together. Both were ticked at Adobe for keeping the Type 1 specs for themselves, which allowed proper kerning, among other things, and just allowing developers to use Type 3 for their own fonts, which left Adobe with a major quality advantage. TrueType forced Adobe to open that spec up.
But it wasn't an Apple surprise. Both Apple and Microsoft were involved, and both were at the release announcement.
Unfortunately, sand boxing is just for memory protection. It doesn't do anything for other basic problems. Sand boxing for iOS is different from what OS X, Windows and other major computer OSs do.
Well, look at where Dell is these days, and you will see why their failing company needed to go private. Dell is not a high quality supplier. I could tell you Dell tales that would curl your toes, but you probably don't want to know any of that.
Need I mention that almost every system update from me over the past few years has borked up Windows machines in one way or the other, and needed to be recalled? I can Liu t to many other problems from other systems. So no, Apple isn't nearly in the same boat as those. You're trying to make it seem as though Apple problems are the norm for them rather than the exception. They are not.
You are looking at this through your one good "Apple" eye?
I have personally had 6 Macs with major problems, two had to eventually be recalled, and that did not count the many I had in studios which plagued us with all sorts of minor issues. That does not make me pick on Apple at all, just I can not let the Apple exceptionalism pass.
I have had much fewer PCs so not such a large sample, not without problems, but they were cheaply and quickly fixed, so didn't fester.
Dell still sells vastly more computers than Apple and higher end models as well. That it sells them cheaply and still does so so successfully shows they are just in a different market than Apple. My view is Dell's inferior rating is over stated, as is Apple's superior rating. That does not mean I would buy a Dell over an Apple, it is also no comfort to my brother's neighbour or anyone who has a problem with their purchase.
Adobe was a very strong supporter of Apple, and Apple was a very strong supporter of Adobe, actually, the reason why Adobe succeeded at all, until Apple's sales began to falter after the incompetent Michael Spindler made a couple of major blunders that had it appear that Apple might go under, and Adobe decided to port their software over to Windows, and then decided to support Windows by refusing to support Mac hardware and software features so that their software would be "feature equivalent" across platforms. This was purely a defensive move made because Adobe was afraid their market might disappear.
The nonsense about Truepe is just that, nonsense. TrueType wasn't an Apple thing, it was an. Apple and Microsoft thing. They both invented this together. Both were ticked at Adobe for keeping the Type 1 specs for themselves, which allowed proper keening, among other things, and just allowing developers to use Type 3 for their own fonts, which left Adobe with a major quality advantage. TrueType forced Adobe to open that spec up.
But it wasn't an Apple surprise. Both Apple and Microsoft were involved, and both were at the release announcement.
TrueType was an Apple invention, not Microsoft's, which Apple stupidly licensed to Microsoft in exchange for an equivalent non-Postscript printer language TrueImage, that Microsoft delivered late and which never went anywhere.
TrueType was developed in the late 1980s and was released with System 7 in 1991.
Michael Spindler didn't even become CEO of Apple until 1993.
I remember the launch and from memory John Warnock was close to tears.
Yeah ... Maybe Tim needs to do what Steve did ... Tell 'em they're holding it wrong!
Just looked up the details in case my memory was failing.
TrueType was announced at the 1989 Seybold conference. Apparently Adobe's Geschke found out about TrueType just 2 days before when he spoke to Bill Gates about licensing ATM. But I distinctly remember how upset Warnock was at the conference.
Well reasoned and well said!
My current disappointment is iTunes ... It's gone from "It just works" -- to It just sucks!
It may be time to Snow Leopard Yosemite and iOS!
Just looked up the details in case my memory was failing.
TrueType was announced at the 1989 Seybold conference. Apparently Adobe's Geschke found out about TrueType just 2 days before when he spoke to Bill Gates about licensing ATM. But I distinctly remember how upset Warnock was at the conference.
None of which changes the fact that Adobe's insistence on keeping Type 1 proprietary was the reason for the development of TrueType. Warnock's subsequent whining and belated release of Type 1 notwithstanding.
I think it's called a pronequark or some such!
It was their business, and Apple did knife them in the back, with no warning. They didnt even hear about it from Apple, they got the tiniest of warnings of what was going to happen to them from Bill Gates. At the time it was apparent that no-one at Apple had even considered how this would affect Adobe. For Apple the only thought is themselves, not out of any meanness, just there isn't anyone else.
Fortunately Adobe had Photoshop as their next best thing.
Was Apple "whining" when Adobe rightly saw Apple as unreliable and moved to Windows, which as it turned out stopped Adobe going bust and secured Adobe's future?
I am saying this with no particular attachment to Adobe. I have been working at extricating myself from their software over the last 5 years and will be very happy when I no-longer need to use Illustrator/Photoshop/Indesign/Acrobat again.
When a business relies on something like a piece of software and a workflow - it's standard professional practice to do the following:
1. Run a test unit before upgrading other machines
2. Contact the software developer prior to upgrading to learn of any documented bugs with the new version
3. Read the release notes provided by Apple
Just because a software update becomes available doesn't mean that staff should have the ability to apply it the same day. In professional business, no one ever installs software blindly hoping for the best.
Apple release security updates separately for many reasons including this.
- Applecare will run the numbers and be initially told (By AppleCare Engineering) to try a video card or board replacement. Upon realising (3 replacements in) that it does not resolve the issue, an internal notification will finally be sent (By AppleCare Engineering) listing it as a "known issue". i.e.: At which point offers to replace boards and machines will probably cease. (Think iMac screen condensation). Will most likely need a firmware update.
- As to the comment about quality control slipping under Cook, thats absolute rubbish. Quality control has improved year on year since Cook came on board. Some absolute shocking releases under Jobs and actually it was not Jobs fault, it was a simply the way the company was structured back then and they way products were rolled out and how early reports of faults were received, processed and addressed. Or in some cases, not addressed for months / years. Oh and oh course the odd design shocker.
At the end of the day, based on the time line (refresh pending) and the extremely low volume of complaints, it will be low on the list of things to do, but there will be someone working on it. A number of years back I worked on an audio playback issue with the Mac Pro (Not listing year). Only one customer picked it up, but he was a squeaky wheel. Anyway, secured a NDA with the customer and worked though with Engineering (Not Applecare Engineering - There is a major difference), and eventually resolved the issue about 6 months later. Worldwide firmware update finally released.
What I learnt from that process is that it was a "known issue" prior to release, however the probability of the required set of circumstances being used and implemented by the customer to reproduce it was like 0.00002 percent.
I am currently using the last Mac Pro tower with Resolve and a bunch of other BMD gear for editing RED 4K. It struggles. Tempted to get the new Mac Pro ... but have been holding out for exactly the reasons listed in this article. Will go for the 2015 model. Will it be perfect - no, but it certainly won't be like a water-cooled G5 - anyone remember that awesome piece of brilliantly designed engineering? Was that released under Cooks watch?