Auto engage Wah Wah

[miasei]

Can you realize a auto engage wah wah in gp3? So when you push the pedal it’s on and when you pull it to the first position it goes off! Thanks.

[pianopaul]

What wah wah plugin are you using?
The pedal you are using is sending midi messages to gp?

[miasei]

Using the Wah Wah from the plugin Cory Wong from Neural DSP. Only the Wah turned on.

[pianopaul]

OK, can you map a widget to the wah wah turning on?

[rank13]

There will be lots of options if you use GP Script. However I think the simplest place to start will be to look at using widget ‘groups’ and also value scaling. In this example I’m just using the internal gain plugin.

Add 2 widgets, one mapped to the wah pedal, the other mapped to wah on/off.
In the widget General settings, set them both to the same widget Group.
For the on/off widget, go to the widget settings ‘Value’ tab, and try these settings as a starting point:
[EDIT: I don’t have Neural but on my Mercuriall Euphoria plugin, these settings worked well]

The idea behind these scaling settings is that having 48 as the minimum and 51 maximum means that you’ll hit 50 (rounded) very quickly, which is the value at which most on/off parameters will turn on.

If your midi pedal isn’t calibrated to go fully 0 in the heel position, you might need to lower the minimum setting further (or calibrate!).

[miasei]

Great I will try this!

[rank13]

I decided to test the Cory. Min 48 and Max 51 for the wah on/off seems to work well.

[miasei]

Thanks man!

[David-san]

Yes, exactly what I wanted to propose

@David-san

Yes, this is doable with a GPScript. But, there is a slightly different solution which doesn’t require any scripting. The idea is that if your pedal is at 0 the plugin is bypassed, if not it is active.
To do so, you can:

• use a pedal widget together with a led button
• assign the pedal to the wah parameter of the plugin
• assign the led button to the bypass parameter of the plugin
• assign both widgets to the same widget group
• invert the led button value and modify its max range to 2.0.

This is done in the following gigfile (the associated plugin is a MIDI in block, only to illustrate the principle): wah_and_bypass.gig (6.1 KB)

[rank13]

I thought we’d had this query recently, but couldn’t find it. But it was there in my subconscious

[miasei]

This works great. Thank you all for the help!!!

[David-san]

I am happy if it works for you

[rank13]

I’ve come back to this again, and for my purposes have found the perfect solution using GPScript.
I wanted to avoid any pops/artefacts that I was getting when the wah effect was bypassed/enabled, and I also wanted to not disable it immediately in the heel-down position (value 0) to avoid it being switched off when I was using the pedal’s full range.

I’ve used timers in GPScript to check how long the wah parameter is in the heel-down position, and it will only disable it after 800ms (can be customised in the script).

I’m also using a GP balance control as the wah on/off mechanism. So the wah plugin is always active to avoid pops/artefacts and a button connected to Balance will immediately crossfade between L+R to either route my signal to the wah or bypass it. Any detected movement from the expression pedal will activate (route to) the wah.

Plugin routing:

Widgets: (also showing the Balance control: right is bypassed, left is enabled). As I’m moving it you can see that when the wah parameter value hits 0 it still stays active. But at the end, when I leave it at 0 it will turn off automatically (e.g. Balance moves fully right).

Wah Auto Engage and Timed Disable.gig (11.3 KB)

[elucid]

@rank13 Genius! Thank you so much for this solution! I’ve been wondering how to get that to work for ages and - like all clever things - it was so simple: a timer.

The problem with having it just cut off the wah on zero is that it will usually make the sound jump in and out of ‘wah’ mode: even with the pedal at the zero position, the sound will not be that same as with the wah bypassed. And I find it impossible not to accidentally go to zero while I’m using the pedal…

I had resorted to dedicating a button to turning the wah on and off - but now I don’t have to! Thank you so much!

[miasei]

Great solution. Will also try this!!! Thanks man.

[jpt]

Outstanding!

[tonycore]

yes, nice one on the timer!

[Dick]

Nicely done
Some clever thinking.

[miasei]

Hello, I have an issue with my Expression pedal. It does not go to 0.0, so with your Settings, the Wah stays enabled. I tried to fix it with some programming or value Settings, but I did not get it. The Wah value Shows 0.8 in the Widget. At this Point it should turn off. Can you help me how to Programm this to work. With the midi Controller, there is no way to calibrate the pedal!!! Thanks a lot.

[rank13]

Try this version. If you edit the script (Window > Show script editor), there is a line in the ‘Initialization’ section like:
MinThreshold = 0.0

You can change this value to whatever is the minimum value of your pedal (value must be between 0.0 and 1.0). Just hit the ‘Compile’ button at the bottom after you have made your change.

But when you say your minimum is 0.8 - do you mean your widget shows 1.0 with toe down, and 0.8 with heel down? If so, something is very wrong, as that is only 20% of what the normal range should be.

Wah Auto Engage and Timed Disable v2.gig (11.5 KB)