How to exclude a parameter in presets?

[Per Boysen]

I'm working with a bunch of presets in a stack to "change chords" in three audio loopers in other stacks. This is handled by a FaderBox + ParamMod assigned to the continuous pitch parameter in each of the loopers. One problem I can't solve is that I want to control Glide of the FaderBox manually, from a MIDI fader in real-time. But the presets I create for pitching the loopers into different chords also snatches the value of the FaderBox's Glide parameter and I don't want that to happen. Any suggestions?

I have already tried to bind the Glide value to another FaderBox at another stack. My hope was to that binding to take over the not wanted binding to presets inside the first stack. But it didn't ;-(

I wish Numerology had a function to exclude certain parameters from the normal preset functionality, to let people play those parameters manually (live). I do a lot of live performance work but when trying to use Numerology this issue is always blocking the way for me.

[jim]

There is a mechanism for doing that in the code, which is called "static" params, but there is no UI for it yet. There will be in the pro version. However, I'm also trying to determine if the behavior for 'midi assign' is appropriate here, I'll have to think about that a bit more. I will also see if I can come up with a workable solution with the current release. For instance, depending on what else is in the current stack, you could probably use a secondary stack (with its own presets) with a FaderBox and ParamMods to modify the 'main' FaderBox, but that is kinda silly....

Be sure to ping me on this if you haven't heard anything in a couple weeks.

Best,
Jim

[Per Boysen]

Ah, thanks! I can sort of use Bidule while awaiting the pro version then.

Greetings from Sweden

Per Boysen
www.boysen.se
www.perboysen.com



On Tue, Jun 23, 2009 at 6:42 PM, jim<> wrote:

> There is a mechanism for doing that in the code, which is called "static" params, but there is no UI for it yet. Â*There will be in the pro version. Â*However, I'm also trying to determine if the behavior for 'midi assign' is appropriate here, I'll have to think about that a bit more. Â*I will also see if I can come up with a workable solution with the current release. Â*For instance, depending on what else is in the current stack, you could probably use a secondary stack (with its own presets) with a FaderBox and ParamMods to modify the 'main' FaderBox, but that is kinda silly...