cubace
August 23, 2020, 10:16am
19
Macken:
Steinberg does take some shady actions, occasionally. Such as bricking audio interfaces, in order to try to force its customers to buy new hardware. However, in this case I believe that Stenberg is without blame. Of the three audio interfaces (Steinberg MR816X, Behringer UMC1820 and MOTU 828es), I’ve used with Cubase the last couple of years, only one (the 828es) has exhibited this issue. Therefore I don’t think that Steinberg is to blame here.
I’d like to see people shouting out about Apple’s hypocracy, though. Apple keeps telling us how they consider security and integrety to be priorities. So why are they forcing us to take actions that entails a clear security risc ?
Hackers gaining access to the cameras and microphones in modern computers (pads and phones) is a serious security problem. The more applications that has been given access to these, the more options the criminals have! It is important to deny any software that doesn’t clearly access the camera or michrophone that access, is very important. Just ask anyone dealing with cyber security and cyber crime.
This is something that all audio software manufacturers (not only Steinberg) should take up with Apple, and piont out that this is a serious security risc .
Giving a DAW access to the computers michrophone is not neccasy for it to have accsess to an audio interface, which the MR816 and UMC1820 proves. The only time Cubase needs access to the camera (but not the michrophone) is when you’re using VST Connect.
Apple has made it easy. A audio input streams are equal. And there is no way that apple can know what you connect to your audio stream. And I think most of the audio interfaces connected to a computer is not intended for music production.