@xander what faust code are you using?

@pcs800 modulate the values with your UI component.

@d-healey said in Toggle Button States & Automation:

@Lindon All parameters have a range of 0 - 100 I think, regardless of the control type. I recall it being brought up on the forum a while back.

so its a DAW issue then not HISE..?

@aralbar so buttons have a 0 or 1 value - what you are describing seems to be (at best guess) a slider...

@HISEnberg said in Dynamic resetting of processor ID:

It struck me that this might be a bad idea. I sketched out a new idea for a dynamic FX processor system where I reassign the processor IDs that my UI components are linked to. Am I going to have issues down the road when doing this?

you are probably better off assigning your processor IDs into some array and referencing them in the UI component....what processors are you using>? if not Hardcoded Master FX - I suggest you use them.

@JulesV open the included file - copy its contents into your Faust file....

@d-healey said in Display output levels.:

@Lindon you can with laf

oh of course, silly me...

@d-healey said in remove a macro from a control with scripting...:

@Lindon Give me a minimal snippet and I'll see what I can do.

thanks - but actually I think I've resolved it.... by bypassing the control in some well defined scenarios....

@d-healey Sorry I should have been considerably more clear...

I have a set of Macro Modulators...

	Engine.setFrontendMacros(["LFO1", "LFO2", "LFO3", "LFO4", "LFO5", "LFO6"]);

So now you can right click on the control and assign one to that control....

I want a way to unassign these assigned controls using scripting...

Re: Macros - Clear All?
I read the above but I dont think it got implemented -pushed =- but even then I'm pretty sure its not what I want, I need to unassign a macro from a specific set of controls... do we have that ? - cant see anything in the documentation.

@DanH said in SliderPackLAF:

@Oli-Ullmann said in SliderPackLAF:

@Lindon
Oh, that's great! :-)

Do you have any idea how to modify your current script so that the value is only displayed when you move the slider or when you hover over the slider? Is that even possible?

@Lindon I have this question too! Also, how to do a gradient on the sliders?

well we are at the limit of my CSS here so not sure how to do this...

@d-healey said in Display output levels.:

@Lindon said in Display output levels.:

Then use a timer in a panel to display these.

Why not use a peak meter tile?

'cause I cant seem to make the peak meter work horizontally...

EDIT: oh the forum gods just struck - and now I can....

its a pity we cant set some warning and overs colours... so anything over -6 = orange anything over 0 = red...

@d-healey oh, nice... I will give it a go...

@d-healey ... to create components from the JSON - so I can copy and paste my complex panels JSON into a script that I can use in another project.

Its really about saving the hassel of going through every one of my child components and declaring it then "FromJSONing" it...

@Lindon back here again........ any possible answer to this?

@Delamere said in Display output levels.:

I have managed to work out how to display the amount of Compression & Limiter being applied with a VU Meter, but I don't want a VU meter just the values displayed in the boxes provided. Does anyone knob how to do this?

so you will have a simple gain before and after your effects, get a reference to these and use .getCurrnetlLevel(x); (x=0 is right, x = 1 is Left)

Then use a timer in a panel to display these.

HISE | Scripting | Effect

The FX script reference

(docs.hise.dev)

@Christoph-Hart said in Global Cables Don't Work when compiled:

you are correct Global Cables DONT work in compiled scriptnode

Wrong. This was the case, but now they work and you can even send arbitrary data through it (which will get copied though so it might not be the fastest option).

well that's good news.

@Orvillain said in Global Cables Don't Work when compiled:

@Lindon Huhh.... so if you use global cables, don't ever compile your script-node networks and just compile the plugin using the uncompiled networks??? Do I have that right???

no, - design your instrument structure so that your effects are in your compiled script nodes - but the signal routing(using Global Cables) are separated out...

@griffinboy you are correct Global Cables DONT work in compiled scriptnode....and I cant recall Christophs reason for it..but it seemed reasonable at the time...so I only ever use them "standalone before and after the HCFX

@Morphoice said in Summing plugins, snake oil or useful?:

I do have access to some consoles, but from what I can test-record and measure the differences in sound (unless you crank them to extremes) are so subtle, they are not even worth the CPU to algorithmically rebuild them, or am I on the wrong track here?

yes they are all very subtle when you test them in a single track - but thats not really how they are supposed to be used - its a cumulative effect - so every track in your DAW has your console plugin - so only in the master out do you hear any noticeable difference.