Deliberate Distortion: Dissonance Mac OS

Posted:
in General Discussionedited November 2020
Native Instruments, maker of audio devices such as four-channel DJ controllers, has warned users that macOS Big Sur can potentially physically damage equipment.
Musicians have already toldAppleInsider that they plan to wait before moving to Apple Silicon Macs, but now a music company is telling users not to update to macOS Big Sur either.
'Using a Traktor Kontrol S4 Mk3 on macOS 11 (Big Sur) can cause malfunction and potentially damage your controller!' says the company in its certain older products'>support pages. 'We are working together with Apple to find a solution to this problem.'
Although the company does not specify how macOS can damage this particular popular device, it does go into more detail for the rest of its range. 'Using a Maschine Mk2 or Mikro Mk2... can cause high CPU spikes on your computer,' it says.
'Using a Komplete Audio 1, Komplete Audio 2, or Komplete Audio 6 Mk2... can cause CPU spikes and distortion with sample rates above 172kHz,' it continues. 'This can be avoided by selecting large buffer sizes (2000ms).'
Separately, the company notes that certain older products are not compatible with macOS Big Sur.
There's no information about compatibility with Apple Silicon M1 Macs. The company does not disclose in what form it is working with Apple, nor whether this has been taking place during the extended beta period.
This is not, however, the first time that Native Instruments has had issues with macOS updates. It previously took time to support Apple's Music app, which replaced the previous iTunes.
Similarly, Native Instruments and other music hardware companies initially found problems with Apple's T2 security chip. That was reportedly a glitch that Apple later addressed.

Comments

  • Would have been nice to announce this information before Big Sur was released but maybe they did directly to current users.
  • Native Instruments has had how long to figure this out? Come on.
  • Native Instruments has had how long to figure this out? Come on.
    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?
    Yeah, come on.
  • 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).
  • 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).
    *should* is correct.
    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.
    edited November 2020
  • This is terrible and needs to be fixed.
    Also will Apple ever provide hardware for Logic? We desperate need this!
  • 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.
    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.
  • 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).
    *should* is correct.
    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.
  • 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).
    *should* is correct.
    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.
    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.
    If the error I made is unfixable, then it really
    is up to the other person to stop doing something wrong — that does not mean that I didn’t fuck up; it just means that I’m not the one who can do anything about it at this point.
    If Apple‘s software is performing perfectly, and this bug can happen even under normal circumstances, then of course I agree that Apple carries no responsibility to fix this.
    OTOH, I know that the manufacturer of my audio interfaces spent so much time fighting obscure bugs in Apple‘s FireWire implementation back in the day that they eventually just fixed Apple’s FireWire stack for them.
    Courtesy.
    edited November 2020
  • This is terrible and needs to be fixed.
    Also will Apple ever provide hardware for Logic? We desperate need this!
    You mean controller hardware like the Logic Control Mackie built for Emagic in 2002?
    I doubt they ever will again. They make Logic Remote for iPad, which is much more flexible and adaptable to future feature sets and controller needs.
    Hardware controllers are a whole huge can of worms for a very, very niche market. The only reason the Logic Control existed was because Mackie standardised the control protocol ('Mackie HUI') and thus made it available to all other DAWs, so their hardware became compatible with the entire market. This introduces a huge support burden and is not at all in Apple's interest.
  • 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).
    *should* is correct.
    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.
    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.
  • NI at its finest - dear kit with bad drivers
    #pioneer4ever#serato4life
  • < Previous
  • Next >

Professional academic writers. Our global writing staff includes experienced ENL & ESL academic writers in a variety of disciplines. This lets us find the most appropriate writer for any type of assignment.

Title

Author

Deliberate Distortion: Dissonance Mac Os 11

Date of Award

5-2018

Deliberate Distortion: Dissonance Mac Os 7

Degree Type

Research Paper

Degree Name

  • The melody engine features a deliberate element of chance and controlled randomisation to offer up a diverse range of melody options. Advanced Algorithms Melody Sauce is capable of creating many millions of different permutations of melody through its complex algorithms, which are the result of 18 months’ research and collaboration with top.
  • List of Amc - Free ebook download as Word Doc (.doc /.docx), PDF File (.pdf), Text File (.txt) or read book online for free.
  • In that analysis, I looked at two years’ worth of patches issued to fix serious security bugs in Apple’s Mac OS X operating system, as well as other Apple software applications like iTunes.

Master of Arts in International Development and Social Change (IDSC)

Department

International Development, Community and Environment

Chief Instructor

Nigel Brissett, Ed.D.

Distortion:

Second Reader

Ramón Borges-Méndez, Ph.D.

Abstract

The 2016 election that catapulted Donald J. Trump to the U.S. presidency has raised questions for how Facebook may have enabled the emergence and coalescence of a social movement among traditionally improbable voters. The research in this paper engages with contemporary social movement theory, assessing its adequacy for explaining the role of Facebook as a primary method for facilitating a social movement among the civically-alienated, who are the most unlikely of all Americans to join an organized collective for change. From a methodological perspective, the exploration takes up the case as a strategy of inquiry to explore social movement theory in the context of algorithmically-mediated social networking environments. It is concluded that the presence of a proprietary algorithmic mediator deployed by Facebook creates deliberate effects among its users which cannot be explained with social movement theory. These effects cannot be easily studied without unethical cognitive manipulations or information distortion.

Recommended Citation

Stimmel, Carol L., 'Networks of Isolation: The Case of Donald J. Trump, Facebook, and the Limits of Social Movement Theory' (2018). International Development, Community and Environment (IDCE). 181.
https://commons.clarku.edu/idce_masters_papers/181

Deliberate distortion: dissonance mac os catalina

Included in

American Politics Commons, Civic and Community Engagement Commons, Other Social and Behavioral Sciences Commons, Political Theory Commons, Politics and Social Change Commons, Public Policy Commons, Science and Technology Studies Commons

COinS

To view the content in your browser, please download Adobe Reader or, alternately,
you may Download the file to your hard drive.

NOTE: The latest versions of Adobe Reader do not support viewing PDF files within Firefox on Mac OS and if you are using a modern (Intel) Mac, there is no official plugin for viewing PDF files within the browser window.