Scriptnode cpu ?
-
@Natan Could you try this again? Or did this not work out?
-
@iamlamprey It Has Its Own CPU Usage Story, It Removes The Artifacts,
And Another Wierd Issue With This, It'll Add Around +5 dB :/ To The FX Plugins Output. -
@Natan @iamlamprey For me, use of the transient shaper is the worst culprit. As @Natan mentioned, the 'Export To Cpp Meta Node' method reduces CPU significantly in HISE but the nodes become inaudible when used in exported plugins.
Guess we'll just have to wait until @Christoph-Hart roles out the scriptnode revamp - Can't be an easy task mind! -
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).
If anyone has this info please chime in
-
Prety Stocked Here :(
@Christoph-Hart Could You Please Help Out Our Hise Buddies :( -
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).
-
@Christoph-Hart Watching git like a hawk
-
@Christoph-Hart said in Scriptnode cpu ?:
can export any node now into a custom dll
Does it work on GNU/Linux and Mac too?
-
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.
-
@Christoph-Hart macOS here :)
-
@Christoph-Hart Mac OSX as my main machine.
But I constantly flick between a Windows virtual machine so no real problem either way! -
@Christoph-Hart I'm on Mac OS
-
@Christoph-Hart macOS only too here
-
@Christoph-Hart macOS definitely :)
Sorry but the weird guy named Greg above is me, just had an issue with my account...
-
Alright, the people have spoken. In that case I try to offer at least Intel macOS support ;)
-
@Christoph-Hart :face_blowing_a_kiss:
-
@Christoph-Hart Thanks :)
-
-
@Christoph-Hart you're a legend honestly!
-
-- 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...
