<![CDATA[Scriptnode cpu ?]]>Is it normal for the Scriptnode to be so CPU hungry or is the Hise cpu meter inaccurate as it does not match the task manager one ?

Is it expected that one would export as cpp and incorporate like that or will it take less when exported as VST ?

I am working on an ensemble fx , and just the modulation(no delays) with no samplers or instruments loaded is about 3-4 % on my CPU on the HISE cpu meter and 0.7 in Task manager.

]]>https://forum.hise.audio/topic/3011/scriptnode-cpuRSS for NodeSat, 16 May 2026 11:46:52 GMTSat, 26 Sep 2020 19:10:49 GMT60<![CDATA[Reply to Scriptnode cpu ? on Tue, 19 Jan 2021 23:34:12 GMT]]>@LeeC Nice, I have version 11 of Parallels Desktop and I remember I had problems, I think it was the installation of ipp, I guess it's working better in the later versions of Parallels...

]]>https://forum.hise.audio/post/29091https://forum.hise.audio/post/29091Tue, 19 Jan 2021 23:34:12 GMT<![CDATA[Reply to Scriptnode cpu ? on Tue, 19 Jan 2021 21:37:15 GMT]]>@ulrik Yep pretty sure I did!

Here's a screenshot of the preferences of a recent project running through HISE on Windows 10 Parallels.

alt text

The project makes use of the 'Audio Analyser' floating tile which (if I'm not mistaken) requires IPP to be enabled. As you can see in the screenshot above, the 'Use IPP' flag is ticked and enabled.

Compilation works fine without errors.

]]>https://forum.hise.audio/post/29086https://forum.hise.audio/post/29086Tue, 19 Jan 2021 21:37:15 GMT<![CDATA[Reply to Scriptnode cpu ? on Tue, 19 Jan 2021 19:42:04 GMT]]>@LeeC Did you manage to install ipp on Parallel?

]]>https://forum.hise.audio/post/29075https://forum.hise.audio/post/29075Tue, 19 Jan 2021 19:42:04 GMT<![CDATA[Reply to Scriptnode cpu ? on Tue, 19 Jan 2021 19:33:19 GMT]]>@DanH yeah I can compile plugins just fine with my current setup.

Currently running the following:

Mac Pro
Mac OSX Mojave 10.14.6
Parallels Desktop 16 running Windows 10

]]>https://forum.hise.audio/post/29073https://forum.hise.audio/post/29073Tue, 19 Jan 2021 19:33:19 GMT<![CDATA[Reply to Scriptnode cpu ? on Mon, 18 Jan 2021 20:57:27 GMT]]>@DanH I'm running BootCamp and am able to compile Hise / plugins, using windows 10
I tried to use "Parallels" but it didn't work, I remember I had big problems installing ipp and I went the BootCamp way instead.

]]>https://forum.hise.audio/post/29045https://forum.hise.audio/post/29045Mon, 18 Jan 2021 20:57:27 GMT<![CDATA[Reply to Scriptnode cpu ? on Mon, 18 Jan 2021 20:01:08 GMT]]>@LeeC Out of interest can you compile HISE / plugins on Windows in your virtual machine ?

]]>https://forum.hise.audio/post/29044https://forum.hise.audio/post/29044Mon, 18 Jan 2021 20:01:08 GMT<![CDATA[Reply to Scriptnode cpu ? on Mon, 18 Jan 2021 11:08:01 GMT]]>@LeeC - yeah - buying a windows machine is probably a good idea too.

]]>https://forum.hise.audio/post/29021https://forum.hise.audio/post/29021Mon, 18 Jan 2021 11:08:01 GMT<![CDATA[Reply to Scriptnode cpu ? on Mon, 18 Jan 2021 10:59:50 GMT]]>@Lindon I agree. Setting up a windows virtual machine via Parallels is a good solution for any Mac users that are interested.

]]>https://forum.hise.audio/post/29017https://forum.hise.audio/post/29017Mon, 18 Jan 2021 10:59:50 GMT<![CDATA[Reply to Scriptnode cpu ? on Mon, 18 Jan 2021 10:50:04 GMT]]>-- If I was a Mac-only user I'd consider this a warning that at some point....this windows-only-for-development is gonna happen - and get myself a windows machine...

]]>https://forum.hise.audio/post/29015https://forum.hise.audio/post/29015Mon, 18 Jan 2021 10:50:04 GMT<![CDATA[Reply to Scriptnode cpu ? on Sun, 17 Jan 2021 21:49:38 GMT]]>@Christoph-Hart you're a legend honestly!

]]>https://forum.hise.audio/post/29003https://forum.hise.audio/post/29003Sun, 17 Jan 2021 21:49:38 GMT<![CDATA[Reply to Scriptnode cpu ? on Sun, 17 Jan 2021 17:23:15 GMT]]>@Christoph-Hart 🍻

]]>https://forum.hise.audio/post/28983https://forum.hise.audio/post/28983Sun, 17 Jan 2021 17:23:15 GMT<![CDATA[Reply to Scriptnode cpu ? on Sun, 17 Jan 2021 17:22:16 GMT]]>@Christoph-Hart Thanks :)

]]>https://forum.hise.audio/post/28982https://forum.hise.audio/post/28982Sun, 17 Jan 2021 17:22:16 GMT<![CDATA[Reply to Scriptnode cpu ? on Sun, 17 Jan 2021 16:41:53 GMT]]>@Christoph-Hart 😘

]]>https://forum.hise.audio/post/28974https://forum.hise.audio/post/28974Sun, 17 Jan 2021 16:41:53 GMT<![CDATA[Reply to Scriptnode cpu ? on Sun, 17 Jan 2021 16:40:54 GMT]]>Alright, the people have spoken. In that case I try to offer at least Intel macOS support ;)

]]>https://forum.hise.audio/post/28973https://forum.hise.audio/post/28973Sun, 17 Jan 2021 16:40:54 GMT<![CDATA[Reply to Scriptnode cpu ? on Sun, 17 Jan 2021 16:09:06 GMT]]>@Christoph-Hart macOS definitely :)
Sorry but the weird guy named Greg above is me, just had an issue with my account... 😐

]]>https://forum.hise.audio/post/28970https://forum.hise.audio/post/28970Sun, 17 Jan 2021 16:09:06 GMT<![CDATA[Reply to Scriptnode cpu ? on Sun, 17 Jan 2021 14:23:23 GMT]]>@Christoph-Hart macOS only too here

]]>https://forum.hise.audio/post/28966https://forum.hise.audio/post/28966Sun, 17 Jan 2021 14:23:23 GMT<![CDATA[Reply to Scriptnode cpu ? on Sun, 17 Jan 2021 14:16:51 GMT]]>@Christoph-Hart I'm on Mac OS

]]>https://forum.hise.audio/post/28963https://forum.hise.audio/post/28963Sun, 17 Jan 2021 14:16:51 GMT<![CDATA[Reply to Scriptnode cpu ? on Sun, 17 Jan 2021 14:14:10 GMT]]>@Christoph-Hart Mac OSX as my main machine.
But I constantly flick between a Windows virtual machine so no real problem either way!

]]>https://forum.hise.audio/post/28961https://forum.hise.audio/post/28961Sun, 17 Jan 2021 14:14:10 GMT<![CDATA[Reply to Scriptnode cpu ? on Sun, 17 Jan 2021 13:16:02 GMT]]>@Christoph-Hart macOS here :)

]]>https://forum.hise.audio/post/28953https://forum.hise.audio/post/28953Sun, 17 Jan 2021 13:16:02 GMT<![CDATA[Reply to Scriptnode cpu ? on Sun, 17 Jan 2021 11:10:43 GMT]]>Actually I am thinking about making it a Windows only feature (the development tools of course, the end product will run on any platform). How many of you are relying on Linux or macOS as development machine?

The reason is that the JIT compiler is pretty low-level and porting it to ARM for future-proofness in the macOS world is basically doubling the task.

]]>https://forum.hise.audio/post/28952https://forum.hise.audio/post/28952Sun, 17 Jan 2021 11:10:43 GMT<![CDATA[Reply to Scriptnode cpu ? on Sat, 16 Jan 2021 22:14:49 GMT]]>@Christoph-Hart said in Scriptnode cpu ?:

can export any node now into a custom dll

Does it work on GNU/Linux and Mac too?

]]>https://forum.hise.audio/post/28913https://forum.hise.audio/post/28913Sat, 16 Jan 2021 22:14:49 GMT<![CDATA[Reply to Scriptnode cpu ? on Sat, 16 Jan 2021 17:40:45 GMT]]>@Christoph-Hart Watching git like a hawk ☺

]]>https://forum.hise.audio/post/28894https://forum.hise.audio/post/28894Sat, 16 Jan 2021 17:40:45 GMT<![CDATA[Reply to Scriptnode cpu ? on Sat, 16 Jan 2021 17:30:30 GMT]]>

Still think it would be good to know the last known version of Scriptnode when 'Export to CPP Meta Node' worked end to end ( from within HISE all the way into DAWs).

Now that I think about it, it never worked full end to end. In PercX I took the generated C++ code and wrote some custom wrappers around it, but there never was a proper export when you compile plugins.

I'm afraid you need to wait until the revamp is ready. I am closing in on a first prototype for the SNEX workbench. It's kind of nice because you can export any node now into a custom dll that will be loaded as plugin without having to restart the app (also the compile time is a fraction of the full HISE compilation, so the development cycle is quite efficient this way).

]]>https://forum.hise.audio/post/28893https://forum.hise.audio/post/28893Sat, 16 Jan 2021 17:30:30 GMT<![CDATA[Reply to Scriptnode cpu ? on Sat, 16 Jan 2021 17:24:00 GMT]]>Prety Stocked Here :(
@Christoph-Hart Could You Please Help Out Our Hise Buddies :(

]]>https://forum.hise.audio/post/28892https://forum.hise.audio/post/28892Sat, 16 Jan 2021 17:24:00 GMT