Widget Incrementor /Decrementor

[WITELITE]

I read through @npudar post on this

[Gig] CC and PC Incrementer

This scriptlet provides a simple way to increment or decrement either Control Change (CC) message values or Program Change (PC) messages. [Program-Change-Control-Change-Incrementer] It is commonly used to move up/down through plugin internal presets, or those on external controllers/hardware. Map the ‘Previous’ and ‘Next’ parameters in the scriptlet to two pad or button widgets (set as ‘Momentary Touch’ in the widget settings). The scriptlet’s MIDI out port should then be connected to your p…

though it got my interest in a different way.

Is there a way to have buttons on a midi controller increment or decrement by 1 or a specific number?

Let’s say I’m playing live and have three sounds (acoustic, electric and synth) in my case for the guitar.

It would be cool to have buttons for each of them that would increase or decrease by 1 db on each press. I looked at the post but that seemed more related to a plug in versus say a volume control.

And then ideally a way to set them back to default values on song change (as most of these are in my global rackspace)

Thanks

MM

[pianopaul]

Scripting is your friend
The gain control is also a plugin and you can manipulate the level via scripting.
I could be a little bit tricky to control by 1db as you have levels between 0.0 and 1.0
1.0 means +6db and 0 means silence

[WITELITE]

Thanks. Why 0 to 1.9 when widget values are 0 to 100?

With widget values of 0 to 100 I could just write down the values at each db increment but the 0 to 1.9 throws me a bit.

And I assume the script would have all 3 volume controls in them.

MM

[rank13]

I’ve done a few different variations of this scriptlet. This one includes a ‘step size’ parameter and an option to route the midi output to the ‘GP Local Port’, which means it can be learned to widgets.

See if this example works - it is already set up to increment/decrement a Gain plugin.

CC and PC Incrementer 1.3.gig (286.7 KB)

[WITELITE]

@rank13 Brilliant!. I was able to adapt it to my rig for the first control (Electric Volume). I assume as constructed it simply has to be in the Global Rackspace (ala System Actions) versus connected to anything. I’m even looking at your coding to try and learn what you are doing!! I also assume for 3 of these I would need to not only change CC#s but also the variable names in the script ?

And I assume my solution will need to tweak the “On Program Change” to “On Song Change”

Here’s my twist. I also have a volume slider for each of the outputs. For performance mode, I think the +/- 1 db will be easier to use but if the slider is changed, I would like the current value in the script to update. And when the song changes , I would like it to reset to the default values. (let’s say -6db but I’ll figure out what that translates to).

Make sense?

Thanks (you’re awesome and the power of scripting is really something)

MM

[rank13]

I’d actually recommend you not try and use this scriptlet. I think what you’re trying to accomplish is probably best as a global rackspace and/or gig script.

[rank13]

@WITELITE see if this is close.
Volume Increment with Song Reset.gig (127.6 KB)

I’ve got a manual array of the db-to-param conversion, so have only done -6dB to +6dB. You can add further values for < -6dB if you want.

The reset to default on song change uses OSC, so you’ll need to have OSC activated in GP options for this part to work.

[WITELITE]

This looks awesome! I have to incorporate it into my gig file to be sure but you are a rockstar my friend.

If I already have a global rackspace script I assume I just copy this in as well?

And I need to study the OSC piece too.

Keep you posted but THANKS!!!

[WITELITE]

@rank13 Worked Brilliantly. I removed the OSC part and just changed it to on song change so that it resets.Then I realized that it would be better to have a premier output (that I can adjust on the fly) which resets on every song (thanks to your brilliant work) and a post mixer output (that I would set and adjust via the control surface that wouldn’t change) for more flexibility. So in effect I have this

So is there a downside to having the two audio mixers. (The one you worked on defaults to 0 +/- 6 db) and the post mixer is set at -6db as a start to avoid clipping?

@dhj - I hope the option to move the Global Panels to the top is being considered. I find the visibility to Global Panels is much more important than the Rackspace ones (or at least the option to close the rackspace panels like you can the Global ones

MM

[rank13]

@WITELITE

So is there a downside to having the two audio mixers.

I guess I don’t follow why you need another mixer. You can control the faders in the first mixer via the usual midi/osc methods, in addition to using the increment/decrement buttons. The script will always check the current value first, when you use the increment/decrement buttons.

But, ultimately, whatever works for you is the right answer

[WITELITE]

I do have a control surface for the sliders which is good for the master levels. having the secondary mixer ensures the hardware faders won’t jump when I move them while the db increment buttons can adjust per song in real time. This worked brilliantly!!!

MM