- Dismiss NoticeWe're currently conducting systematic tests with the release version of macOS 11 (Big Sur) in order to offer full compatibility of our products as soon as possible. You can find our latest compatibility status - herePlease note that although announced at the same time as macOS Big Sur, Apple Silicon processors are an independent release with separate compatibility concerns for NI products. Compatibility with macOS Big Sur will not yet ensure compatibility with Apple Silicon processors. At the moment, Native Instruments products are not supported on computers with Apple Silicon processors. Read more - here
Changing the asio buffers makes no difference, and none of the performance metres are anywhere near peaking. In the processs of troubleshooting I tried using wasapi drivers and found that the problem immediately dissapeared, and I was able to achieve lower latency as well (though for live performance that is not crucial). Contrary to popular 'audiophile' claims, there are NO benefits from using ASIO as far as music playback quality is concerned, while bugs in ASIO drivers may severely degrade the performance. Current version: 2.1.2, released on 2012-06-06.
Discussion in 'Technical Issues (Archive)' started by Thoifl, Jun 21, 2009.
- Thread Status:
- Not open for further replies.
- Thread Status:
- Not open for further replies.
I have reported before that the driver installer executable rmeinstaller.exe does not work properly. I have used it on three different Windows 10 Pro 64 bit machines, all of which are updated to the latest version ( 1803 ). The installer hangs after the first screen. The task continues to run without any CPU activity and after waiting for approximately 60 seconds appears to continue and finish correctly. However after a reboot the icon for the control tool is not present. To get around this is was necessary to go to the
C:Users%username%AppDataLocalTemprme directory and run or rerun dpinst64.exe. Incidentally I also tried running as administrator but that made no difference.
C:Users%username%AppDataLocalTemprme directory and run or rerun dpinst64.exe. Incidentally I also tried running as administrator but that made no difference.
Foobar2000 No Asio Drivers Foundation
On the particular machine I was building today ( core -I7 but with a fairly old socket LGA 1366 motherboard) there was a further problem even then because the ASIO drivers were not working. In Audacity ( built with ASIO support ) no ASIO drivers were even detected. In Foobar 2000 the output could be set to Madiface ASIO but when play was pressed it said that the driver could not be loaded. I checked a number of things but eventually found that I had to disable the Realtek HD Audio ( Realtek ALC889 codec) by switching off the on board audio device in BIOS. Not the first time I have found that Realtek drivers break ASIO ( and not only the RME ASIO drivers).