@d-healey It worked, thanks buddy 😎

Is that fixed? @Christoph-Hart

@Christoph-Hart Hmm... not sure but it might...
The older built I'm using is 20 days old only, and my labels are saveInPreset: disabled in my project anyway, so why would the last build enable it? (so empty their text is a consequence of this I guess)
It looks like the saveInPreset property has been re-enabled by default
The problem is not for new labels, but the actual ones that are already here

@Christoph-Hart Oh, thanks.

I increseed mouse sensivity of the slider, so it is more slow and these frequency jumps are more stable.

Thanks for the bandpass example!

@dustbro I can confirm it does not work for me either on arrays with [i]

@Christoph-Hart mailed :)

@Christoph-Hart Thank you! Checking now.
Looks good

@Christoph-Hart Wow cool! Thanks 👍

@Christoph-Hart yes please, I think it's helpful when I want to use peak meters if I remember correctly. I'll try out the new build this afternoon. Thank you!

It seems like the project is not including the stk module, which was recently added. You most probably are using a project file that was created with the master branch version and try to compile it with the scriptnode branch.

Try a full clean and rebuild.

@Lindon
That's what I thought at first, but I don't know when or where I would have changed it.

@Christoph-Hart
I've pulled the latest scriptnode from Github with no change.

I did fail to mention in my initial post that the preset browser functions correction when inside a floating panel. This is really where I need it to work and in the grand scheme of things, this does not seem to effect the performance and operation of my compiled apps/plugs.

Screen Shot 2019-08-15 at 1.35.06 PM.png

Thank you both for your replies. I'll keep troubleshooting on my end.

Best,

@Trivalve said in Endless trouble trying to build scriptnode:

@d-healey My build succeeded with that one, so it's definitely a scriptnode-specific problem... Frustrating that I can't use the latest version, but whatever. I suppose I'll try again in a month or so when Christoph releases 3.0 (that is what he said, right?)

If it makes you feel better I can't use it either :(

@Christoph-Hart said in New compiling error...:

This usually happens if you have some sort of library version mismatch between the C++ standard library and your compiler.

How would I check that?
And why this error for this project and not for the others?

Also, my project crashes sometimes if I push it hard, both in Hise or the standalone export. Probably because a "dirty" code, even though I checked it hundreds of times, I've never found what causes the crash.
Is it possible a dirty code can be linked with the AUi/VSTi compiling issue?

@Christoph-Hart Thank you! I will check ASAP.

Yes, the internal buffers of the delay module are set to 65536 samples, which is a little bit more than a second on 44kHz.

However you can change it, it's just a template parameter in hi_dsp/modules/DspCoreModules.h (line 19).

I'm using the scriptnode branch from the 28th of July, it works now...