@d-healey Hey David, Im doing something wrong here.

The knobs that control the FX work correctly. The Master has no effect at all on anything EXCEPT the linked Saturator knob. All it does is turn it back to 0 instantly.

Can you spot what Im doing wrong here?

//MAIN EFFECTS const KnobsMax = [1, 1]; //Knobs Being Controlled const knobs = []; for (i = 0; i < 4; i++) { knobs.push(Content.getComponent("knb" + i)); knobs[i].setControlCallback(onknobControl); } //Link Buttons const btns = []; for (i = 0; i < 2; i++) { btns.push(Content.getComponent("linkbtn" + i)); } //Linked FX const var SatLink = Synth.getEffect("Saturator1"); const var ChorLink = Synth.getEffect("Chorus1"); const var PhaseLink = Synth.getEffect("PhaseFX1"); const var BitLink = Synth.getEffect("BitCrusher"); //Linked Knobs Callbacks inline function onknobControls(component, value) { local index = knobs.indexOf(component); KnobsMax[index] = value; setSaturator(index, value); setChorus(index, value); setPhaser(index, value); setBitCrusher(index, value); } //Master Knob const MainFXknb = Content.getComponent("MainFXknb"); MainFXknb.setControlCallback(onMainFXknbControl); inline function onMainFXknbControl(component, value) { for(i = 0; i < knobs.length; i++) { if(btns[i].getValue()) { knobs[i].setValue(knobsMax[i] * value); setSaturator(i, knobsMax[i] * value); setChorus(i, knobsMax[i] * value); setPhaser(i, knobsMax[i] * value); setBitCrusher(i, knobsMax[i] * value); } } } inline function setSaturator(index, value) { SatLink[index].setAttribute(Saturator1[index].WetAmount, value); } inline function setChorus(index, value) { ChorLink[index].setAttribute(Chorus1[index].Rate, value); } inline function setPhaser(index, value) { PhaseLink[index].setAttribute(PhaseFX1[index].Mix, value); } inline function setBitCrusher(index, value) { BitLink[index].setAttribute(BitCrusher[index].Quant, value); }

@d-healey no, cleaned everything out.

@Lindon I haven't experienced this exact issue, but Studio One can be grumpy.
I'd build a debug version of the plug and see where it fails when you load the DAW

@Matt_SF wow, this is so cool :)

@orange yep thanks - exactly what I was looking for - and there it was all along sitting in front of mee in the Module browser, sorry to waste everyones time...lazy lazy lazy...

@orange Yeah, I've seen some of the videos of @d-healey , they are really a great ressource, but I didn't see the one you suggested. I'll look into it... :-)

@Lindon Yeah, I think I'll add an error message when you try to rename the root node. Then you can still go into the XML and rename the file manually.

@d-healey Yes. Ok. I got it.

It has the correct name, but while it had a callback on the main interface onInit, it didn't have the variable definition. So, it worked manually selecting notes, but not with this script.

Thank you, Dave. I crossed this bridge :)

Something else I'd suggest is disabling IPP by default on all operating systems. Those who want it can enable it but it will make it easier for beginners who are always finding it a stumbling block.

@d-healey that was my first idea but then it will change the other ‘ok’ buttons. All good I can work around it. Thanks!

@Christoph-Hart great, all working so far, thanks!

@toxonic I have posted a couple of videos about building an xy pad (they might be Patron only at the moment, I'm not sure)

@Lindon Most of the "portworthy" effects are already available in scriptnode (or can be reproduced super easy with the low level types). But maybe that's actually a good use case of the template system, I'll check that.

@DanH Ahhhh, I see. That makes much more sense to do actually. Thanks!

@iamlamprey Thank you... did the trick... I tried everything I could think of in the script... and it comes down to a component param... I have an long way to go...

@Christoph-Hart more like smalltalk everyday...

@Christoph-Hart @Fortune It's super useful, now the compressor sounds much better. Thank you!

@d-healey thank you sir