Midi control the neural dsp plugin in Ableton

[ericpranachi]

How to setup a midipedal to control a neural dsp plugin within Ableton. In the standalone version it works easily, but in Ableton it does not work at all.
In case it only works in the standalone version there is another question; how to sent the output of the standalone version directly to an audioinput in Ableton?

[epichicken]

MIDI control only works in standalone, not DAW

I just bought this plugin today after my trial expired, and I’m loving it! I have an old BOSS GT-10 that I decided to use as a midi controller with the Plini plugin. When I run the standalone Plini program, I can program the midi map and switch presets successfully with the 6 pedals in my midi controller. I play live almost every week and wanted to try this out. However, when I run Plini as a vst in my DAW, Studio One 4.6 (I’ve tested in Reaper and Fl Studio as well), the Plini plugin does not …

Problem midi mapping

I use Ableton live on stage. How do I map preset changes to my softstep pedalboard? I have tried everything (I think)

Using MIDI controllers with Live

Do any of the above resources help? Also what plugin and MIDI controller are you using?

[Victo]

Hello.

You can control any parameters from a plugin in Ableton and map it to the Midi control you want.

For this you will need to deploy the parameters of your plugin, then add the parameters you want to control, then MIDI map them.

In fact, when you know the mechanic, it’s super easy.

• Add the VST/AU to an audio track
• Deploy the parameter arrow (#1 on the screenshot)
• Click configure (#2) = button goes green, it waits for you to add the parameter you want to control on the plugin
• Click on any parameter on the Plug-In interface (in my exemple #3 for Overdrive Active), it will add the control on the Ableton plugin box
• Then use Ableton Midi Learn function to assign the added function with the button/switch/knob/fader you want. (#4)

(Sorry my screenshot is in French ^^)

[ravmitterhoff]

Thanks, this worked but I have some questions:

1. Is there a way to save the configured VST to use it again? I tried saving it as a device but when I load it into another track the configurations are not there.
2. Does this mean none of the midi mappings on the actual VST (and or standalone) won’t work in Ableton?
3. Is this the actual way this should be done MIDI on Ableton ?
4. At Guitar Plugin Foot Controller - ft. Neural DSP - YouTube

I found this comment: NOTE TO ABLETON USERS: For MIDI controlling Neural DSP plugins within Ableton. You will need to use Note messages with positive note velocities instead of CC messages. That is the only way Neural’s plugins respond to Ableton MIDI right now.

Is this true?
Thanks

[Victo]

Hey ravmitterhoff !

I’ll try to answer as simple I can

1. In fact you can’t save Midi mapping of any daw on the VST itself.
   Anyway, as Ableton Live is (for me), the best daw to do mapping stuff, there’s a workaround.
   Select your VST loaded into a tray, then righclick and “Group it”. It will put your VST into a “group Rack”, were you can also create Macro control.
   The idea is then to save the Ableton rack itself with the VST in it when your setup is made.
   When you reload the Rack, it will keep the settings.
   ANYWAY, it will not keep the custom MIDI assignation.

That’s why I use the Macros (here’s a video to know how to make a macro for 3rd party plugin)

And As I have Midi Controller that are official control unit for Ableton Live (I got the PUSH2), I can see the macro on screen and control any stuff.

In a Daw, if you are using a Midi unit that is not a “control surface”, in that case : One button will be assigned to One action in One specific VST.
The same midi message can be assigned to several actions, but they will work all together at the same time.

Another thing : If have mapped MIDI stuff like you wanted to, you can save your project as a template project.
That way, Midi assignation will be kept when you reload the project.

2. Yes, and if i remember it will be the same for all the DAWs.
   When you launch a VST or Audio Unit it’s different that the Standalone App. (so the Midi assignation too).

3. This way is more technical, and is aimed to make automations when rolling a show.
   For exemple, you’re playing with a backing track, and you will use the “midi” track to program automatic changes ! No more Footswitches needed ^^

4. True and False. It depends if you want to control a Slider or a button. Or maybe he don’t know about the thing you learned on the first post I made.

To make it “simple” : CC message (Control changes) are message that has been made to control a slider or a knob (with min/mac value).
Note messages are just “ON/OFF” buttons.

The thing is that lots of Midi device you can buy on the market does respect the general midi norm, and sometimes assigns CC control to a button, with different values (I’ll not go into the details, but it will be too long to explain).
But in the Logic things :
Sending a Note is better to control a “ON/OFF” action in a software (so a button)
Sending a CC is better to control a linear thing (volume slider, amount etc…)

[ravmitterhoff]

Does this article MIDI on Ableton change anything in terms of savings the mid mappings to the VST? I tried do do what it says but could not get it work at all.