OutrageProductions

This is true for their lower end I/O's from 2021 onwards. Prior to that... not so much. Hence the A4A issues.

Start HERE with an excellent series on the basics of the application.

Learn how to understand and use all of the options available in the Export Dialog.

Real ASIO drivers don't go through the audio profile dialog AFAIK. Only WDM & WASAPI. There isn't currently a true ASIO driver for MOBO audio (coming soon on next gen HW tho!), only for external audio interfaces. If you have a fake (ASIO4ALL/Realtek/Behringer, et al) driver that says it's ASIO, then you're asking for problems.

I love it so far.

@Tom Bednarz I run sessions that will eat up to 80-90 Gb of my 128 available, but after flushing back to just the basic OS requirements leaves me with about 4.2Gb actually in use. I've found that NI Kontakt (et al), Spitfire, and UVI have a tendency to hang around in the Standby ram waiting for cocktails or the after party for some reason, so... {Some folks have an issue with, and will argue about my method, but I've been using it for 25+ years with zero issues:} DL "Rammap(dot)exe" and unzip it somewhere convenient. Create a batch file to open a CMD window and (with echo on, and a 2 second delay between each command) run the <Empty Standby List> & <Empty Working Sets> commands to flush the ram. Store the batch file somewhere convenient like the desktop and name it "Flush Ram(dot)bat" or something. I do this after and/or between each session. Works like a charm. It has never failed. Not even once. [Here's the batch file:] ::@echo off echo cd\{YOUR EXACT LOCATION OF RAMMAP} START rammap -Et timeout/t 2 /nobreak START rammap -Ew timeout/t 2 /nobreak Exit

To convert an analog audio source to a digital (computer/DAW) data stream you MUST have an AD/DA audio interface. If you want to track (in real time) multiple sources (like a drum kit), said interface MUST have a discrete input channel for each microphone desired.

If the track you are viewing has been frozen, it will just show the latter. Unfreeze it and the keyboard comes back.

Not gonna happen. All DAWs that support VST3 are from 2018 or later. Deal with it as is, or upgrade.

Have you enabled Echo Input on the channel?

Have you used any MIDI monitor (Midi-OX for example) to confirm that your keyboard is still sending out data? You may have had a component level failure in your keyboard. If your MSK25 is BlueTooth [MkII], you may have lost the transmitter.

The latest version of Kontakt is 8. Session Percussionist requires v7.7 or later of either Kontakt Full or Player. Works here in that configuration in both CbB & Sonar. You might try posting this issue on the NI forum in the Kontakt sub.

Amazon can source nearly everything, especially when NewEgg is out of stock or subbing out sources.

As @Kurre mentioned, watch to see if Sonar is a background or lesser function in Task Manager. If so, go to the executable for Sonar, RMB to properties and set to elevate priority.