Plugin Parameter - global disable

[d.healey]

@Lindon No the plugin parameters are fixed at compilation, I believe this is part of the vst standard. That's why Kontakt has a bunch of assignable parameters rather than adding them dynamically. The HISE equivalent would be the macro system.

But why don't you just not use them if you don't want the user to?

[Lindon]

@d-healey said in Plugin Parameter - global disable:

@Lindon No the plugin parameters are fixed at compilation, I believe this is part of the vst standard. That's why Kontakt has a bunch of assignable parameters rather than adding them dynamically. The HISE equivalent would be the macro system.

But why don't you just not use them if you don't want the user to?

Because its a player that is essentially just "hiding" the editor controls - so I set a flag - and I build the player , I unset the flag and I build the "proper" program.

[Lindon]

@Matt_SF said in Plugin Parameter - global disable:

@Lindon what about :

const allControls = Content.getAllComponents("");

for(c in allControls)
	c.set("isPluginParameter", false);

wouldn't that lead to problems with the AU validation?

Plus I'd want to be able to turn them back on - and not all controls are plugin params....

[d.healey]

@Lindon Oh in that case doing as Matt suggested should work because it's pre-compile time.

[Lindon]

@d-healey said in Plugin Parameter - global disable:

@Lindon Oh in that case doing as Matt suggested should work because it's pre-compile time.

--yeah see my concerns above...I think it means the plugin will fail plugin validation..

-- I guess I could copy the entire project into a new space and do this:

const allControls = Content.getAllComponents("");

for(c in allControls)
{
	c.set("isPluginParameter", false);
        c.set("pluginParameterName", "");
        c.set("isMetaParameter", false);
}

[Matt_SF]

@Lindon yes if I'm not mistaken, auval gets angry when the 'metaParameter' is not enabled for UI items controlling more than 1 parameter, but if you don't have any, it should be fine

[Lindon]

@Matt_SF said in Plugin Parameter - global disable:

@Lindon yes if I'm not mistaken, auval gets angry when the 'metaParameter' is not enabled for UI items controlling more than 1 parameter, but if you don't have any, it should be fine

I think "auval" - and its sneaky little friend Logic - get snippy if :

isPluginParameter = false && pluginParameterName = !empty
isPluginParameter = true && pluginParameterName = empty

[d.healey]

@Lindon If you're not using the component tooltip or text you could put the parameter name you want in there and clear or assign it dynamically in your loop. Otherwise you'll have to store it separately.

[Matt_SF]

@Lindon ah interesting, I never ran into this (I always have a name for the param if it is a plugin Parameter)

[Lindon]

@d-healey said in Plugin Parameter - global disable:

@Lindon If you're not using the component tooltip or text you could put the parameter name you want in there and clear or assign it dynamically in your loop. Otherwise you'll have to store it separately.

Yeah thats a good idea - sadly there are literally many hundreds of controls - its HoriZEN....

[d.healey]

@Lindon Couldn't you write a loop to grab all the names before you wipe them and put them in a separate file?

[Matt_SF]

@Lindon take the lazy road : grab and store everything you need in an array or object. Write everything in a file. Include that file in your script

[Lindon]

@Matt_SF said in Plugin Parameter - global disable:

@Lindon take the lazy road : grab and store everything you need in an array or object. Write everything in a file. Include that file in your script

thanks guys I'm taking the even lazier road - copy the project - do it there...it needs its own plugin name anyway...