FYI - Solved this issue by 'Saving the network' in the latest version of HISE.
I then unloaded the network with the issue and proceeded to load up the newly saved one.

I've just opened up an older scriptnode project in Hise 3.6.2 and I'm seeing this error also:

Network -: 0 (expected: 0 )

Did anybody find a solution to this at all?

Thought so... thanks for confirming @d-healey

Guess we'll just have to continue working within a fixed UI size :grinning_face_with_big_eyes:

Hey guys,

Quick question...

Is it possible to expand panels/resize a compiled plugins UI with HISE like so?

Was curious whether it's possible to implement a lookahead compressor in Hise, either with by use of the main modules or via scriptnode.

Has anybody achieved this, or now how to do so?

From what I can see, by default the scriptnode Peak node outputs a value between 0-1 the same as what we get when we use Effect.getCurrentLevel() from the main modules.

If this is true then I guess I can proceed with something like Engine.getDecibelsForGainFactor(PeakOut) to convert the SN peak output to db.

Please shout if you see otherwise :beaming_face_with_smiling_eyes:

Hi guys,

Does anybody know what value measurement the Peak node in Scriptnode outputs?

I'm ultimately trying to get the value of it converted to db but wanted to be clear on what I'm starting with.

Appreciate the clarity @ustk.
Very useful!

Makes me wonder how the likes of Waves and Klanghelm achieved measurements in their VU meters.
Obviously, they weren't built using HISE, but I'm now curious as to whether they too inherit similar inaccuracies when it comes to displaying these calculations in a filmstrip.

@ustk Fair enough.

I probably should have mentioned that I'm attempting to build a vintage style VU meter capable of various output measurements.

I guess even if there was a "pure" way to get all the samples and make said calculations, the accuracy of the display of these values (in a png strip for example) would always be skewed, due to the fact that a timer would have to be used.

If I've understood correctly that is! :grinning_face_with_big_eyes:

Great explanation as always @ustk.

I appreciate that it will still lead to some level of measurement inaccuracy, but is there a way to reduce the lower level of the timer in HISE to ultimately get more samples?

Reduce it lower than the 30ms limit that is?

How's it going Hise crew?!

Does anybody know how to go about calculate RMS and potentially K-Meter levels in Hise from:

Engine.getMasterPeakLevel() 

I've been searching around the web trying to find the maths but nothing so far.

If you've got any links, or info in general don't hold back :smiling_face_with_sunglasses:

Hope everybody's good either way!

@orange Thanks for the heads up!
I’ll try when I’m back at my machine and will report back

@d-healey A ha... I was completely unaware of this!

Ok, I'll compile the SNEX workbench application and see how I get on :beaming_face_with_smiling_eyes:

@Christoph-Hart Ok, so by restarting the "SNEX workbench" do you mean restarting the whole of HISE? I don't see a specific option for the workbench.

I get as far as this after choosing to Wrap into DSP Network but things appear blank after Saving and reopening the project in HISE.

After saving an reopening things look like this:

@Christoph-Hart thanks for jumping in!
Really don't want to take up too much of your time on this one, but I guess I never saw instructions on how to compile this 'pitch shifter to a dll'.

So step 1. I guess :beaming_face_with_smiling_eyes:

Thanks for clarifying about the renamed "compile DSP networks" @d-healey.
Thought this might be the case but didn't want to assume.

Hey @d-healey, do you think you'll get any time soon to put together a video tutorial of this for us patreons?

Personally, I've been banging my head against the wall trying to get the Pitchshifter Tutorial working in an exported plugin.

I get as far as this after choosing to Wrap into DSP Network but things appear blank after Saving and reopening the project in HISE.

After saving an reopening things look like this:

I should note that I am using the develop branch to load this Pitchshifter tutorial project as I believe that the 'SNEX Workbench' is only available in develop.
Is this true?

The instructions included in the tutorial project appear simple enough but attempting it seems far from trivial (see instructions below).
I'm also unable to find 'Tools/Compile All nodes' anywhere in HISE

Any thoughts?... Sorry for the brain dump!

**Compile the PitchShift node
The first thing you should do is to compile the PitchShifter.xml network into a C++ node. Open the Network in the SNEX workbench, then go to Tools / Compile All nodes.

The performance of the uncompiled node is around 5% CPU, and goes down to 0.9% CPU in Release mode.

Build the examples
When you compile the nodes in a project, they will also be copied to the AdditionalSourceCode directory of the project root and when you export a plugin from the project that uses one of the compiled nodes, it will compile them again and embed them into the binary of the plugin (so you don't need to ship that .dll that you've used in the SNEX workbench with your plugin). This is the recommended workflow for all non-trivial custom nodes in a project.**

@Natan Cool, no probs

On the topic of Presets, does anybody know how to set a preset folder to 'Read-Only' so that users can't overwrite or rename factory presets?

I think that this was introduced a while back, but I can't find any documentation on how to achieve this.

Cheers