Once compiled, can Hardcoded module still access specific node/node's value?

[ustk]

Because once compiled I get -> "! Unknown function 'get'"

const var bottomNetwork = Engine.getDspNetworkReference("BottomFX", "BottomFxNetwork");
const var bottomNetworkCompReductionNode = bottomNetwork.get("CompReductionAddNode"); // ! Unknown function 'get'
const var bottomNetworkCompReductionNodeValue = bottomNetworkCompReductionNode.getParameter("Value");

So is the error mine?

[ustk]

Bump
I am unable to push my plugin in testing phase without this. Totally stuck

[d.healey]

@ustk It's no longer a network once it's compiled, so I would assume you can't access the individual nodes.

[ustk]

@d-healey Thanks for your response Dave!
That is what I assume too, but nodes must have been translated to something still accessible or there would be no point in having an API for that, since DSPs are meant to be compiled... @Christoph-Hart ?

How one reads a simple value? I could get a display buffer, but calling an entire buffer just to grab the last value doesn't seem right... right?

[ustk]

@d-healey @Christoph-Hart In fact in the DspNetworks/Binaries/Source folder there are the header files with the entire DSP structure using the node IDs, so in the end there should be a translation to still have the script access, making me think that it's more a bug/lack of implementation rather than an impossibility

[Christoph Hart]

@ustk nope once compiled they are a blackbox.

You don‘t need to compile nodes it just makes them faster especially when doing complex stuff and if you need to access them through the API then it‘s definitely a case of leaving them in the interpreted state.

[ustk]

This post is deleted!