@Christoph-Hart - great - downloading now...

@arminh It's not, nothing has changed with expansions.

@d-healey Well the sets are not correct, SSE 4.2 is NOT the highest or newest that HISE uses. Most likely AVX and AVX2 aswell. Or indeed I would have to dig out that old spiked-on AMD cpu in my intel machine.

Architecture = "native" is the issue. It over-rides any setting you make in hise. It uses your build-cpu´s sets available to do the best enhancements available. And whoever said IPP is the only thing in need of higher sets hasnt read the amount of issues on this topic over at the juce forums.

Setting Architecture to x64 in the .jucer project is the ONLY thing I was able to start my instrument build with. That flattens it to x86_64, which is basic original specs of the first 64-bit cpus, so no SSE3 or above, most likely.

@d-healey Done!

I figured it out, in case somebody else would use this. The file

..\hi_scripting\scripting\components\ScriptingContentOverlay.cpp

needs to be edited. The lines 572, 573 and 578 can be commented out or deleted.

jassertfalse.jpg

Recompile. Now it works! :)

showcallback.gif

Did you ever get this sorted?

@Christoph-Hart Superb.. 👌 ☺

Okey :) That Was So Easy, I Got It Up And Running:)
Somehow The First Custom Created node Caused A Bad Crash, But Just Made A Simple Gain, And It Works Smoothly, Gonna Investigate The Nodes :)
Thanks, @Christoph-Hart Your Rock <3

oopsies. Consider it fixed.

@Christoph-Hart Sorry I just forgot to replace it with a string... but I'm sure after testing different config with unmerged and merged time API that it doesn't come from that. Just try this string instead "2020-12-01T14:02:45" (it crashes with the string in unmerged time API Hise)

@d-healey Yeeeeei!!! Supreme 👍 ☺

@Christoph-Hart Wow , Thank you.
I will add this to my project now ,

@orange Yes, it passes all the tests and then.... crashes the Validation tool 😆

It's always been a bit of a lottery to be honest, even before scriptnode, but that seemed to be largely down to choosing a Plugin Code that worked.

@dustbro Yup. @ustk and @d-healey are helping to get me to the right track.

@Lunacy-Audio cool..

Be aware that it increases the memory usage for the streaming buffers which is the reason the default value is 16 and not over 9000 ;)

Sorry it is an old topic but,

Yes I can confirm that, setLatencySamples works perfectly in all of the daws except FL Studio.

Weirdly, when I don't use setLatencySamples, FL studio matches the delay compensation perfectly 😮

So what is the difference that only FL studio doesn't take setLatencySamples correctly? Have anyone solved that?