MIDI cc beyond 127

General discussion about Gig Performer
1

Dear Community

I have found a pitch shifter plugic called Kuassa Efecttor Whammo Pitch Shifter, and whle trying to use some scripting for modifiying some parameters, i have noticed that this plugin uses midi cc beyond 127, as far as i know MIDI 2.0 can use something like that but i am not sure if this plugn really uses MIDI 2.0

what i try to do is to modify the scripting created by @rank13 to do the same changes on a rackspace, (Changing script behavior from CC steps to full semitones - #14 by Josehdx) but even when i modify it and set for example midi CC 131, and after compiling, the script does not work. IDK why this developer decided to use the midi CCs on the next attahment

Any help is appreciated

Screenshot 2023-07-22 192210

2

I don’t believe that for one moment. I bet those are not MIDI CC values but rather they’re host parameters misnamed as CC values.

3

Use widgets and map to the plugin that way. The same parameters are there and then you don’t have to concern yourself with the CC’s above 127.

ScreenHunter 146
ScreenHunter 146382Ă—652 58.1 KB

1 Like
4

Yes, i had already saw that is possible to map to a knob, but as i mentioned on the original post, i would not like to use knobs but the script on the link i pasted. And then i can not relate the script to the midi ccs on the attached screenshot :confused:

5

The script you referenced was based on the scriptlet in the gig file from the link below. Could you modify that to work?

6

CC numbers only go to 127. Check with the developer - I’m certain his documentation is incorrect

7

where did you this cc list from?

8

It’s in the documentation for that plugin - I downloaded it myself and took a look.

I’ve already emailed the developer to ask him why he has that information.

9

I also tested that and this are the exposed parameters

10

Right - I’m pretty sure it’s a “typo” and he meant to refer to host automation parameters

2 Likes
11

@edm11

I have already modifed the script but adding cc 130 or 131 do not work as those values are out of scope. The Midi monitoring returns 127 instead

image
image1839Ă—1060 317 KB

Attaching the rackspace with the script working on Helix native (in helix you can personalize the CCs, on the Kuassa plugin, is not possible)

whammo.rackspace (443.7 KB)

Thanks to all of you for your feedback and assistance

Cheers

12

There is no CC greater than 127

13

What is the issue you want to solve with the scriptlet?

14

Interesting that you succeed to assign the value 130 to parameter CC_NUM which ranges from 1 through 127. I would have expected that the compiler would catch that.

15

The goal is to use 4 buttons to modify the pitch up and down values without opening the plugin

basically the same behavior that was achieve on the same effect but on helix native.

As @edm11 mentined, is possible to map it with a knob, but with the script is possible to have jumps on integer values, and also to see on the rackspace the value that is shown on the plugin GUI.

Hope is clear :slight_smile:

16

Im am sure this CC List in the documentation is not correct.

17

well. i dont know if i did the “right” thing there, i am not a scripter but i know how to read it and modify it. If it is not an expected behavior, maybe is it a bug? :smiley:

18

I do not think it is a bug, CC values greater than 127 do not exist

19

@pianopaul

we agree in that :slight_smile: i just wanted to try it :smiley:

20

So you want 2 buttons to increase/decrease pitch start
and 2 buttons to increase/decrease pitch end?