One knob controlling two parameters

[d.healey]

@DanH Can you write a callback that controls 1 parameter?

[DanH]

@d-healey Hi David, the scripting is super new to me so the short answer is not really!

I find the Hise UI very intuitive and have made pretty much the sampler I wanted in a couple of days, but the extra functionality afforded by scripting is currently beyond me and I need to learn!

I've opened the knob link snippet from the Hise website (https://docs.hise.audio/tutorials/recipes/ui/general.html#link-sliders) and got close but ultimately couldn't link the three knobs to the ASDR functions.

PS - I downloaded and compiled Hise for the first time on Wednesday! Following your video of course!

[d.healey]

@DanH The snippets given in this page so far (with a little modification) can do what you want. Since that's a little complex for you at the moment it's probably best to start with this video and get familiar with the basics of HISE scripting.

[DanH]

@d-healey Thank you, much appreciated :)

[Dan Korneff]

@DanH I highly recommend @d-healey Patreon. You'll learn so much AND he's a great teacher.
https://www.patreon.com/davidhealey

[DanH]

@dustbro Great shout, thanks for letting me know!

In the meantime, I'm getting my head around the script in the snippet you posted above @dustbro. However, in line 3, when I try to change 'EQ1' to the modulator I want (in this case the AHDSR which I have called 'ENV1') I get the error 'ENV1 was not found'.

My line is: const var ENV1 = Synth.getEffect("ENV1");

I had this before as well, I don't know if there is a special name / code for 'Gain' modulators as opposed to 'FX' modulators... FX always works, Gains do not!

[Dan Korneff]

@DanH said in One knob controlling two parameters:

My line is: const var ENV1 = Synth.getEffect("ENV1");

This declaration is not correct. You would need to use:

const var ENV1 = Synth.getModulator("ENV1");

The easiest way to to get reference to a module is by right clicking on it and selecting "create generic script reference" and then pasting that into your script :)

And that's only half of the story. Once you get reference to that module, you'll have to use setAttribute() to select the parameter you wish to control.
Available parameters for the module can be found in the Module Browser:

[DanH]

@dustbro Thanks Dan, that is massively helpful. I've somehow managed to do it! No doubt be asking you tomorrow about something else

[DanH]

@DanH So I'm attempting to apply the same script to a Legato On/Off button for all 3 synth/sampler modules. In the Module Browser these's no value for On/Off for any of the modules (I don't think). Does this need to be done a different way? Script below:

//LEGATO

const var LEG1 = Synth.getMidiProcessor("LEG1");
const var LEG2 = Synth.getMidiProcessor("LEG2");
const var LEG3 = Synth.getMidiProcessor("LEG3");

inline function onLEGATOControl(component, value)

{
//onoff
local legdx1 = 0 * LEG1.BandOffset + LEG1.On;
local legdx2 = 0 * LEG2.BandOffset + LEG2.On;
local legdx3 = 0 * LEG3.BandOffset + LEG3.On;
LEG1.setAttribute(0, value);
LEG2.setAttribute(0, value);
LEG3.setAttribute(0, value);
};

Content.getComponent("LEGATO").setControlCallback(onLEGATOControl);

[d.healey]

@DanH .setBypassed()

[DanH]

@d-healey Many thanks David, what do I need between the parentheses to make it switchable?

[d.healey]

true or false, 1 or 0.

[DanH]

@d-healey Thanks again David, so my script is: LEG1.setBypassed(0); which will turn the legato on when I click the LEGATO button, but not off again.

[d.healey]

@DanH And if you set it to 1 it will do the opposite. Can you think of a way to get a 1 or a 0 when the button is clicked?

[DanH]

@d-healey haha, I will certainly try! PS - I am exhausting all avenues before eventually posting on here and am hugely grateful

[d.healey]

@DanH I'll give you a hint, try checking the value of the button inside the callback ;)

[DanH]

@d-healey 2 hours later and I still can't do it! I'm hopeless

[d.healey]

@DanH LEG1.setBypassed(value);

[DanH]

@d-healey Thank you, I don't understand but thank you! (why no Boolean in there?!)

[d.healey]

@DanH In the callback you get the parameters component and value. Component refers to the control that triggered the callback (in this case the button), and value refers to the value of the control... so the button's value, which will be either 1 or 0 depending on if the button is on or off. You can put Console.print(value); in your callback to see the button's value printed each time you click it, very useful for testing.