This script processor has a network that consumes the parameters

[modularsamples]

@d-healey I ran into the same message, but under different circumstances, my combobox is selecting UI elements..

I guess you've figured it out by now, but what cleared it up for me was exporting the preset as snippet and then importing it, after that the message was gone.

[David Healey]

@modularsamples Yeah I ran into this again yesterday and can't remember how I solved it :p

[Christoph Hart]

@d-healey A scriptFX will forward the parameter callbacks to the DspNetworks parameters by default so that combobox callback will not be executed and this message is supposed to save you some brain cells. You can use DspNetwork. setForwardControlsToParameters(false) to deactivate this and implement the callbacks for your scripted UI elements.

[Adam_G]

@Christoph-Hart i tired using this in the onInit but got an error

"Interface:! Unknown function 'setForwardControlsToParameters' {SW50ZXJmYWNlfG9uSW5pdCgpfDEzM3w3fDQy}
: onInit() - Line 7, column 42 {SW50ZXJmYWNlfG9uSW5pdCgpfDEzM3w3fDQy}"

Does this command go some where specific?

@modularsamples unfortunately exporting as a snippet and reimporting did not work for me

[Adam_G]

@d-healey any recollection how you figured this one out?

[Christoph Hart]

@argon Use the solution I posted above. And don't type in DspNetwork.xxx but use your object name instead:

const var dsp = Engine.createDspNetwork("whatever");
dsp.setForwardControlsToParameter(true);

[Adam_G]

@Christoph-Hart thanks so much, that set me on the right path. it works now :)

[HISEnberg]

@Christoph-Hart I think I am missing something but this won't work for me.

The "whatever" here is just the name of the scriptFx correct (whatever we named the xml file)?

** Edit: Something strange with how the project was set up. There is something buggy about this feature that I can't quite put my finger on. Does the scriptnode have to be compiled to dll first? I solved the issue but I can't say exactly how. This has happened to me numerous times in the past.

[Jeetender]

@Christoph-Hart Unknown function 'setForwardControlsToParameter'

[dannytaurus]

@Jeetender Check the docs. Looks like you're missing an 's' at the end - setForwardControlsToParameters

https://docs.hise.dev/scripting/scripting-api/dspnetwork/index.html#setforwardcontrolstoparameters

[Jeetender]

@dannytaurus said in This script processor has a network that consumes the parameters:

@Jeetender Check the docs. Looks like you're missing an 's' at the end - setForwardControlsToParameters

https://docs.hise.dev/scripting/scripting-api/dspnetwork/index.html#setforwardcontrolstoparameters

Yes it was missing am 's' at the end, thank you. it works but gives out a warning in almost every script "Warning: 'local' used outside of callback/inline function, treating as 'var' "

[David Healey]

@Jeetender The only place you should use var is within functions and paint routines. In on init you should use const as much as possible, followed by reg. In MIDI callbacks and inline functions you should use local.

That warning is telling you you've used local where you should use var (or possibly const/reg) but HISE is still going to accept it and behind the scenes treat it as a var. This is for the benefit of AI agents who don't understand HISE script.

[dannytaurus]

@David-Healey said in This script processor has a network that consumes the parameters:

The only place you should use var is within functions and paint routines. In on init you should use const as much as possible, followed by reg. In MIDI callbacks and inline functions you should use local.

We should just use var everywhere and let the parser/compiler sort it out.

[David Healey]

@dannytaurus said in This script processor has a network that consumes the parameters:

We should just use var everywhere and let the parser/compiler sort it out.

Probably true...