A Button that shows/hides knobs?

resonant

Thank you so much @d-healey .
Last question, for example:
At the same time; if I want to assign this button to Phaser LFO Modulator TempoSync, should it be like this? But it doesn't work.

Content.makeFrontInterface(600, 200);

const var button = Content.getComponent("Button1");
const var knob1 = Content.getComponent("Knob1");
const var knob2 = Content.getComponent("Knob2");

inline function onButton1Control(number, value)
{
        knob1.showControl(value);
        knob2.showControl(1-value);    
}

button.setControlCallback(onButton1Control);
Button1.setModule(LFO Modulator, Synth.getEffect("TempoSync"));

resonant

@christoph-hart
For showing or hiding 2 knobs relatively, with a button on/off.
When button is on, knob 1 will be showed (knob 2 will be hided)
When button is off, knob 2 will be showed (knob 1 will be hided)

Christoph Hart

LOL don‘t know my own API anymore :)

Dan Korneff

@d-healey this worked great! Thanks!
What's the best way to set a knob's visibility at initialization?

Christoph Hart

Just call onButton1Control in the onInit callback with the value you need.

resonant

@christoph-hart Can you give an example, excuse me I really struggle with this stuff bro.

d.healey

@remarkablex There isn't a setModule() command so I'm not too sure what you're trying to do. Whenever you want an action to happen when a button is clicked you must put that code inside the button's callback. So if you want it to control an FX module you first need to grab that FX and store it in a variable (similarly to how a control is stored in a variable), you can then use the setAttribute() command to change a parameter of that effect.

@dustbro If you want it set at initialisation then just set it in the property editor, no need to script it.

Dan Korneff

I have set visible in the property editor to disable. Once I enter in my script, the knobs become visible again. :(
Here's what I'm doing:

const var Button1 = Content.getComponent("Button1");
const var Knob1 = Content.getComponent("Knob1");
const var Knob2 = Content.getComponent("Knob2");
const var Knob3 = Content.getComponent("Knob3");
const var Button2 = Content.getComponent("Button2");
const var Knob4 = Content.getComponent("Knob4");
const var Knob5 = Content.getComponent("Knob5");
const var Knob6 = Content.getComponent("Knob6");

inline function onButton1Control(component, value)
{
	Button2.setValue(0);
	Knob1.showControl(value);
	Knob2.showControl(value);
	Knob3.showControl(value);
    Knob4.showControl(1-value);
	Knob5.showControl(1-value);
	Knob6.showControl(1-value);
};


Content.getComponent("Button1").setControlCallback(onButton1Control);

inline function onButton2Control(component, value)
{
	Button1.setValue(0);
	Knob1.showControl(1-value);
	Knob2.showControl(1-value);
	Knob3.showControl(1-value);
	Knob4.showControl(value);
	Knob5.showControl(value);
	Knob6.showControl(value);
};

Content.getComponent("Button2").setControlCallback(onButton2Control);

Once I hit compile, knobs 1 2 3 become visible. If I remove knobs 4 5 6 from the project, the knobs stay hidden.

d.healey

@dustbro After initialisation all control callbacks are called so this will undo anything you set in the initialisation or in the property editor for controls that are affected by callbacks. A solution for this is to have a variable that is set to a value in the last control callback called and then in any other callback you'll be able to check this variable and only carry out the actions after it's value has been set.

For example create a variable called initComplete and set it to 0. Then in your last control's callback you can put initComplete = 1 Now in all your other callbacks you just need to encapsulate the code inside an if statement if (initComplete == 1){};

Another option instead of using a variable is to use a button set to 0 and then set it to 1 in its own control callback and check its value in the other callbacks.

@Christoph-Hart Maybe it would be good to have a built in variable for this purpose that can be tested when you don't want actions to happen straight after initialization?

Christoph Hart

Just set saveInPreset to false for the button that toggles the visibility, that‘s precisely what it‘s for, then call it in the onInit and it won‘t get overriden.

Dan Korneff

@christoph-hart said in A Button that shows/hides knobs?:

Just set saveInPreset to false for the button that toggles the visibility, that‘s precisely what it‘s for, then call it in the onInit and it won‘t get overriden.

Is there documentation on the Property Editor?
That did work somewhat. But after I recompile, some knobs are still visible intermittently. Adding setValue before the callbacks did the trick.

Button1.setValue(0);
const var Knob1 = Content.getComponent("Knob1");
Knob1.showControl(false);
const var Knob2 = Content.getComponent("Knob2");
Knob2.showControl(false);
const var Knob3 = Content.getComponent("Knob3");
Knob3.showControl(false);
const var Button2 = Content.getComponent("Button2");
Button2.setValue(0);
const var Knob4 = Content.getComponent("Knob4");
Knob4.showControl(false);
const var Knob5 = Content.getComponent("Knob5");
Knob5.showControl(false);
const var Knob6 = Content.getComponent("Knob6");
Knob6.showControl(false);

Dan Korneff

@d-healey Hurry up and make a HISE tutorial so I can purchase it!! ;)

Dan Korneff

I'm almost there....
With this current script, the UI initializes with all knobs hidden and button 1 + 2 are set to off.
I can toggle between Button 1 and 2, which shows knobs 1-3 or 4-6.

Content.makeFrontInterface(600, 500);
const var Button1 = Content.getComponent("Button1");
Button1.setValue(0);
const var Knob1 = Content.getComponent("Knob1");
Knob1.showControl(false);
const var Knob2 = Content.getComponent("Knob2");
Knob2.showControl(false);
const var Knob3 = Content.getComponent("Knob3");
Knob3.showControl(false);
const var Button2 = Content.getComponent("Button2");
Button2.setValue(0);
const var Knob4 = Content.getComponent("Knob4");
Knob4.showControl(false);
const var Knob5 = Content.getComponent("Knob5");
Knob5.showControl(false);
const var Knob6 = Content.getComponent("Knob6");
Knob6.showControl(false);


inline function onButton1Control(component, value)
{
	Button2.setValue(0);
	Knob1.showControl(true);
	Knob2.showControl(true);
	Knob3.showControl(true);
	Knob4.showControl(false);
	Knob5.showControl(false);
	Knob6.showControl(false);
};

Content.getComponent("Button1").setControlCallback(onButton1Control);



inline function onButton2Control(component, value)
{
	Button1.setValue(0);
    Knob1.showControl(false);
	Knob2.showControl(false);
	Knob3.showControl(false);
	Knob4.showControl(true);
	Knob5.showControl(true);
	Knob6.showControl(true);
};

Content.getComponent("Button2").setControlCallback(onButton2Control);

The Only thing I don't have previsions for yet is what happens when a button is unselected. For instance, If I select Button1, knobs 1-3 are revealed. When I hit Button1 again, the button turns off, but knobs 1-3 are still visible.
Would an IF/ELSE statement work after the callbacks? or is this something I need to set in each callback?

d.healey

@dustbro http://hise.audio/manual/VideoTutorials.php ;)

Christoph Hart

Use the radioGroupId property for mutually exclusive button groups.
Check that the value of the callback is true before you do anything (the callback might get fired for all buttons with each click, but only the active one is 1).
Use an array to store all elements in a page
Use a dedicated function that you just call from your callback.

Check out this example, which should do what you need in the most recommended way:

HiseSnippet 1235.3ocsWssaaaDDcosoSDSUPBPerOrvOIA3pHJeoEnvnNVNNPH0NBUtFEnnHXE4JyshZWgcWZEUCCj+u9Izeh9GzNKuHRYKoXFWym3d4LyYNyr25JEdTkRHQVO67oioHquxt2TtNnc.gwQcNFY8b6SIJMUhS55noiIJE0GYYs9aMcXUYCT72+7iGQBIbOZdWHzEBlG8mXiX57dGe36XggmP7omyFUX16dXGOAusHTDA7Yc6lnwDugjKomQLSaMazUL5DExpo8NsZHG51+Oecia8MgdTiFCFLe+HuHojx0W.vQV1V+K7YY+FelVH6oIZJXy0OR3OsWfXBOw0WvTr9gTSCWTOfSIciZGvB86lIaJDxZit4h35Ih3WaeJymMq+bw7EwCfyQTTNsVadJswbTxcYT5DQnuw.KgdVEn2FIz6k187jrw57QLb6Y1c3Pdd.AxfEoUxbQqctscaALCttwHxP5IRnwLD01uYysw60rY8enpSUmW8JbOxUTrNfhgbpVJBUXFWKv5IBLQJISU3ABIlRTLn1hAlgnYBtAL.PowWQj3wPx2Ee.92xb7kTcawnwBNzn1VuiK56tU8sq5fu62xgzp7P1Yq5+dbfca10Z0ra2x6p8JOj8yXGH6l7Fnz3lXPcci0XSRvv0Nbe5GwPNPA0TXJC5OShEoQSUGFOjwo3AQbOS9HdtcggpMyB0q5bcBAAiWanwYwFoNNo2qyY+vFF3sSJ.xs.9fCvPgR7ztIY1KvfsJmAcm2fN2XDjaGMB9QQZsf6lYBuLkbaHkFFQyCNPKaGP8FBxGQGqgwS.yTfrpfB4.3uIvFYXHgf8HggTev9gSwSBnbrWHyaH0upSE1fZYlthwvyTTPBLd4OhTI3ichHNqLivPCZUmahytKt.HMf1pdCko+3vpMXs9vdm0tc7lr5bYpRqUqJKORbShjHEsPLXxNPtzjdtuQQqUGEslKJ.GdFTGGmGLLQgIXOpTSRqeZT0oHAq5THdOSnoumWqty0NUbt4NiLXvhFJ06gT4hF0bVlbEvpwiF0mJyTzz4A6IO+l9ad+1z2KQEKLQAuCmoe+XZZ67iEbWvwBnzz.b.wloDDlpN93gmmd7PuPlOUhXfQdhc7dsnXtW77cz8FbqGB3cdHf28g.duGB38W.3eoywDMwbvbZJ.RKigxVlI6acL8J3BSIGSWw9XpZnVLFY8zYKUf+m2oIKMhcZE6zU6nOl6xiObZwFSX95.ykf9DzLfxtLPaZ8MPKEbhcGdWIEVBZN3WR7Yh2JEQiyphJCIZsTRb9+WjXyOa85RnvmHKiBMSxu2aWDGk1V+Ef5wv76jX9gVeYl+Ie1UFEMus0eCvWgouJauHq0KiW1aNM5wxK6emjco7zcukLbWcgeTHQO+E3MO5Ic.X+84tor41vbESOs3ihJws5atva0uvsuumz8k1cYZufEy20V.eg8kdr4a5ajpZ+lACnd5bxtg8I+5W5ChJAU9YQjlwu7ThVxLElmEMpG7hSOJvDNmFpLkGqYVHkztoosQY5Q49Myd+X5ftl1VoC5lMHZDwSJ9P1Ke.Q8ow8.bhG+V1Jvipg13YmnZ38H3ogevyyHDeKv7EinUoQrSoQraoQrWoQreoQ7ckFw2uBDl2g+5HsXTxxBD5+r0WLdC

resonant

Dear @d-healey can you make an example, I really don't know what to do :)

resonant

How can we add a phaser modulation tempo sync assignment to this button? @d-healey @Christoph Hart

Content.makeFrontInterface(600, 200);

const var button = Content.getComponent("Button1");
const var knob1 = Content.getComponent("Knob1");
const var knob2 = Content.getComponent("Knob2");

inline function onButton1Control(number, value)
{
        knob1.showControl(value);
        knob2.showControl(1-value);    
}

button.setControlCallback(onButton1Control);

Dan Korneff

@christoph-hart total noob question... what do I do with your HiseSnippit? is it a link of some sort?

Christoph Hart

Select everything (including the HiseSnippet part), copy it into the clipboard and choose File -> Replace with clipboard content.

This is the recommended way to share little example patches in HISE as it contains scripts, control properties, modules etc (but no external resources like images or samples).

Dan Korneff

@christoph-hart :love-you_gesture_medium-light_skin_tone: :love-you_gesture_medium-light_skin_tone: :love-you_gesture_medium-light_skin_tone:

A Button that shows/hides knobs?

27

1.7k

11.8k

102.7k