Running in MIDI mode (set up through NI Controller Editor), it has all I need for assigning the eight knobs, but also for now reassigning the “useless” pitch wheel for orchestral work to another CC (Expression).
It is my main “desktop” keyboard for almost everything, though I still have my fully weighted StudioLogic NUMA as well. Tip: As a MIDI device, I color code JAM's LED strips to match whatever CC is represented in Logic's editor, which makes visually referencing everything much more cohesive. And, I already have full transport control in other devices. It's a sweet spot that is working well for me (despite the tone in that thread debunking this).Īs for DAW integration, I am not a fan of the beta template for Logic, whereas the Bitwig integration (and Live) seem far more realized, though I don't use those. With respect to swapping to MIDI mode, and I mentioned this in another thread, I have essential CC's assigned to the touch strips on the JAM, adjacent to my desktop controller where I comp in all my orchestrations in Logic. To me, the KK keyboard makes it all one cohesive beast now. The metaphors and overlap between the three devices running Maschine all made more intuitive sense, though with JAM becoming the catalyst.īut I can't fathom using the Mikro without JAM, and vice-versa, as the Mikro's velocity pads are essential, while the JAM workflow is far more advanced. When I took the plunge with JAM in December, after assessing it's double-duty as a MIDI configurable device (with both CC automation and potential DAW control in mind), the creative potential of Maschine suddenly clicked for me as well, in tandem with the Mikro I seldom used, and my Komplete Keyboard I'd already been using for 1.5 years. You can find detailed instructions for troubleshooting your specific NI controller in the Related Articles section below.So, it is OK to talk about Maschine here, lol? Should the problem persist, try temporarily removing the ".plugin" files from the HAL folder as explained in step 2. If there are more ".plug-in" files in this folder, visit the manufacturer's website and install the latest updates for these plug-ins. Remove these files from the HAL folder as explained in step 2. Updating / Removing Other Plug-insĪdditionally, these plugin files may cause similar problems when launching a NI application: If you should require this functionality again, move the file back to its original location in the HAL folder and restart your computer. While you can fully use Pro Tools without the Avid CoreAudio plug-in, it is not possible to monitor the audio output of any CoreAudio application using your Avid HD audio interface after removing the file. Type in the admin password when prompted.Delete the "Avid ugin" from the HAL Plug-in folder.Copy the "Avid ugin" to another location, for example the Desktop.MacOS 10.15: Macintosh HD > System > Library > Audio > Plug-ins > HAL MacOS 10.14 (or older): Macintosh HD > Library > Audio > Plug-Ins > HAL Open Finder and navigate to the folder:.Native Instruments cannot be held responsible for any damages to your system caused by following these instructions. Removing the Avid CoreAudio Plug-inĭisclaimer: This procedure describes the manual uninstallation of a third-party manufacturer component. If installing the latest update of the AVID CoreAudio Driver is not an option or the issue persists, please continue: 2. In most cases the issue will be fixed after the installation of the latest update of the AVID CoreAudio Driver. NI software with a hardware dependency, such as MASCHINE, KOMPLETE KONTROL, TRAKTOR, GUITAR RIG and Controller Editor, may not recognize the corresponding hardware devices when an outdated version of the AVID CoreAudio HAL plug-in is installed under OS X 10.10.5 or higher.