Because Native Instruments have unlimited resources and only four major hardware lines and several dozen major plug-ins to support on all platforms, while Big Sur only hit Golden Master a few weeks ago — and it seems like the problem might actually be on APPLE's side?Native Instruments has had how long to figure this out? Come on.
*should* is correct.Sounds like a hardware problem ... for Native Instruments. There should be no way any digital input should damage peripheral hardware (different if it is analog).
That's not a great analogy, because it's more like all that but when the thief came the house spontaneously sank into the earth.It's sort of like if I forget to lock my front door and a burglar just walks in and steals stuff — yes, I should have locked my door, but it was the burglar who actually ruined the day.
*should* is correct.Sounds like a hardware problem ... for Native Instruments. There should be no way any digital input should damage peripheral hardware (different if it is analog).
However, if there is some unfixable design flaw that could damage the hardware (I've seen synthesizers permanently bricked by sending the wrong kind of Sysex data via MIDI, resulting in Boot Flash corruption that required replacement*), and Apple's update is sending spurious, errant data that it shouldn't be, then the problem is indeed Apple's to fix.
It's sort of like if I forget to lock my front door and a burglar just walks in and steals stuff — yes, I should have locked my door, but it was the burglar who actually ruined the day.
This is speculation, of course.*) The guy who told me this was using it as an example of how software engineering had gone to shit since the days when he still wrote the code for that brand's machines. He'd always test the resiliency of the machines he was writing for by sending them a huge .TIFF file via SysEx to see if they'd lock up.
I understand what you’re saying and agree to a point, BUT: If an error I made didn’t show up until somebody else also started doing something wrong, that doesn’t mean that the other person didn’t do something wrong.*should* is correct.Sounds like a hardware problem ... for Native Instruments. There should be no way any digital input should damage peripheral hardware (different if it is analog).
However, if there is some unfixable design flaw that could damage the hardware (I've seen synthesizers permanently bricked by sending the wrong kind of Sysex data via MIDI, resulting in Boot Flash corruption that required replacement*), and Apple's update is sending spurious, errant data that it shouldn't be, then the problem is indeed Apple's to fix.
It's sort of like if I forget to lock my front door and a burglar just walks in and steals stuff — yes, I should have locked my door, but it was the burglar who actually ruined the day.
This is speculation, of course.*) The guy who told me this was using it as an example of how software engineering had gone to shit since the days when he still wrote the code for that brand's machines. He'd always test the resiliency of the machines he was writing for by sending them a huge .TIFF file via SysEx to see if they'd lock up.
Er … no.
If their hardware can be damaged by data, then that's their problem to fix, not Apple's.
When folk start sending odd text messages that causes the iPhone to reset itself, then that's Apple's problem to fix, and Apple fixed it. What they didn't do was ask politely for folk to stop sending dodgy text messages.
Apple can't reasonably expected to cater for design flaws in everyone else's products.
And your burglary analogy doesn't apply here because burglary is a deliberate act, this was not. Apple did not deliberately send data that damaged their flawed system. What Native Systems did was fail to design a resilient system.
A better analogy would be building a house made of paper in a flood zone.
You mean controller hardware like the Logic Control Mackie built for Emagic in 2002?This is terrible and needs to be fixed.
Also will Apple ever provide hardware for Logic? We desperate need this!
Sanitizing input data is something that is the responsibility of the designer. Relying on a third-party to do the “right” thing is going to bite you in the ass. Whether you are designing a web page or firmware doesn’t much matter. If your device bricks because of spurious data sent by Apple or Bob’s MIDI shack has no bearing. You are still going to be on the hook for warranty support. Write better software.*should* is correct.Sounds like a hardware problem ... for Native Instruments. There should be no way any digital input should damage peripheral hardware (different if it is analog).
However, if there is some unfixable design flaw that could damage the hardware (I've seen synthesizers permanently bricked by sending the wrong kind of Sysex data via MIDI, resulting in Boot Flash corruption that required replacement*), and Apple's update is sending spurious, errant data that it shouldn't be, then the problem is indeed Apple's to fix.
It's sort of like if I forget to lock my front door and a burglar just walks in and steals stuff — yes, I should have locked my door, but it was the burglar who actually ruined the day.
This is speculation, of course.*) The guy who told me this was using it as an example of how software engineering had gone to shit since the days when he still wrote the code for that brand's machines. He'd always test the resiliency of the machines he was writing for by sending them a huge .TIFF file via SysEx to see if they'd lock up.