Many knobs to control even more pitch modulators in a scalable fashion. How?

[ulrik]

@Christoph-Hart I guess the difference is that in your example, all references are already made pre callback, and it will be faster? Is there a big difference in runtime?

[Christoph Hart]

@ulrik yes when you automate a control in the daw it will be called in the audio thread so going through the module tree and comparing strings to add to a array is absolutely out of the question.

If it‘s not automated it still might clog the scripting thread more than necessary.

[Christoph Hart]

I usually try to create all references on init or when you load a preset or other singular events.

[ulrik]

@Christoph-Hart good to know!

[gorangrooves]

@Christoph-Hart Thanks, Christoph.

I do get why it is a much better idea to connect everything at initializing rather than doing it on the fly. However, I haven't come across any issue with the simpler script, as the intention is not to automate and change pitches while playing, but rather "set and forget."

I'll look into this more closely and run some tests.

My primary concern is "change this for every project."

Why did you write this line like this?

const var PITCH_TARGET_INDEXES = [[1], [2, 3, 4], [5, 6]];

And not like this?

const var PITCH_TARGET_INDEXES = [1, 2, 3, 4, 5, 6];

[Christoph Hart]

@gorangrooves this way you can define how many targets you want to control with each slider.

[gorangrooves]

For reference, here is the scalable working script that doesn't mess up with Pro Tools' onNoteOn and timers.

It creates arrays onInit by pulling all components and synth modulators with matching names. Then, in the callback, it iterates through the arrays to match portions of names. It works like a charm.

const var PitchModules = Synth.getAllModulators("PitchModule");
const AllPitchTuneKnobs = Content.getAllComponents("PitchTuneKnob");

inline function onPitchKnobCallback(component, value)
{
    local id = component.get("id");
    local fxid = "PitchModule" + id.substring(id.length - 2, id.length);
    
    for (m in PitchModules)
    {
        // Check if the modulator's ID starts with the fxid
        if (m.getId().contains(fxid))
            m.setIntensity(value);
    }
}

for (k in AllPitchTuneKnobs)
    k.setControlCallback(onPitchKnobCallback);

[Lindon]

@gorangrooves

are you saying this doesnt work inProTools?

const var PitchModules = Synth.getAllModulators("PitchModule");
const AllPitchTuneKnobs = Content.getAllComponents("PitchTuneKnob");

inline function onPitchKnobCallback(component, value)
{
    local pos = AllPitchTuneKnobs.indexOf(component);
    PitchModules[pos].setIntensity(value);
}

for (k in AllPitchTuneKnobs)
    k.setControlCallback(onPitchKnobCallback);

[gorangrooves]

@Lindon This line was causing an issue in PT, when included within a knob callback:

local mods = Synth.getAllModulators(fxid);

Your code is fine, although it wouldn't work in my use case, as I have a single knob like PitchTuneKnob01 controlling several modulators like PitchModulator01a, PitchModulator01b, etc.

The line with the issue doesn't allow onNoteOn callback and timers to run until the GUI is closed and re-opened.

[d.healey]

@gorangrooves said in Many knobs to control even more pitch modulators in a scalable fashion. How?:

local mods = Synth.getAllModulators(fxid);

You should get all module references in on init rather than doing it dynamically like this.

[gorangrooves]

@d-healey Yes, I did. See the post above.