Skip to main content
Skip table of contents

Neural DSP

Controlling Plugins with MIDI

https://neuraldsp.com/getting-started/controlling-plugins-with-midi

MIDI Mapping

If you are intending to send only one message to trigger a function in a Neural DSP plugin, be sure to set the MIDI Type to CC Toggle. The CC message needs to have a value of 127.

Running in Logic Pro X

Make sure you open your Neural plugin in a Software Instrument track and not an Audio track. If you use an Audio Track, you will not be able to MIDI control the plugin. In the plugin window, select Side Chain > Input > Select the input your guitar is connected to. As shown below.

Screenshot 2024-08-19 at 1.26.30 PM.png

MIDI mapping for Neural plugins works the same in Logic Pro X as in standalone. However, one quirk we noticed is that using PC messages to recall presets does not work when running in Logic. Instead, you will need to use ‘CC Preset’ and CC messages to recall your Neural presets.

Running in Ableton Live

MIDI mapping for Neural plugins works the same in Ableton Live as the standalone plugin. However, one quirk we noticed is that CC messages do not work for MIDI mapping, instead you need to use Note On messages (Note Off not required). Also, the base C used is different from what we use on our controllers. C-0 on a Morningstar does not correspond with C-0 in the Neural plugin. Instead, Morningstar Note 0 → C-1 corresponds with Neural C-0. See below for an example of what works.

This mapping will work with the preset in the screenshot below
for toggling on/off the Big Rig effect pedal.

Note On message that corresponds with above screenshot for toggling the effect on/off. Toggle Mode not required as Neural has a built-in toggle function.

Quad Cortex

Controlling the Looper

When controlling REC/STOP, PLAY/STOP etc via MIDI on the QC, the Looper UI needs to be accessed via MIDI i.e assigning the Looper UI to a Preset and then accessing it via MIDI. If you access the Looper UI via the QC directly, the MIDI commands will not work.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.