@David-Healey I finally managed to get a successful VST3 export! "BUILD SUCCEEDED" in the terminal.

What fixed the SDK error: The issue was indeed the VST3 SDK path. I had to point it exactly to the folder containing the base, public.sdk, and pluginterfaces directories. After correcting this in the Projucer Global Paths, the "SDK missing" error disappeared.

@DanH said in RNBO Integration in HISE 4.1.0: Updated Workflow for Hardcoded-style DSP Networks?:

@voxuer1 so I'm on RNBO 1.4.2 and everything works fine

@d-healey ok, thank you, that helps

@voxuer1 This'll most likely be some Windows rendering issue with JUCE. Probably not something Christoph is going to address himself, and it might not be addressable by the JUCE team either.

All said and done, you're almost certainly going to be much better off rendering out the exactly resolution you need, both in terms of memory efficiency, and also future proofing.

If you need to support different resolutions, and you can't just turn your SVG's into SVG paths using the Projucer SVG Path converter, then you should export your PNG at different scales and choose the right file to insert at runtime based on a global scale factor.

@d-healey yes, that´s it, thanx

@voxuer1 You don't need to split them when selecting/loading the preset, you only need to do that for displaying them.

@d-healey I did it, broadcaster was the right tool!

@voxuer1 That means the thing on the left side of the dot doesn't have a function with that name. You probably need to get the reference to your module in a different way.

@voxuer1 working code

const var Speed = Content.getComponent("Speed");
const var SpeedValue = Content.getComponent("SpeedValue");

inline function onSpeedControl(component, value)
{
local formattedValue = Engine.doubleToString(value, 2);
SpeedValue.set("text", formattedValue);
Console.print("Slider Value: " + formattedValue);
};

Content.getComponent("Speed").setControlCallback(onSpeedControl);