@tobante So the issue was a virtual destructor that I had defined. Both gcc & clang did not complain, but on Windows MSVC gave an error message. I guess that caused ABI problems. After removing said dtor it loads on all systems.

@Straticah When you create a node template file using the file menu item, it will be picked up automatically by the exporter.

There's no use for adding a code editor for the C++ file, just go in the IDE project of the dll and edit the C++ in Xcode / VS Studio:

Create a C++ template file Export the DLL Open the project (in DspNetworks/Binaries/) Edit the C++ code, debug in Xcode / VS by attaching the debugger to your HISE build.

Once you've set it up, the workflow is pretty similar to the usual workflow for C++ coders.

@Sawer did it work? :)

@Lindon said in Adding a C++ library to our HISE based instrument:

So... we have a deal with a very large distributor/developer to carry our plugin. As you may guess this is a very very big deal for us.

However.... they want us to use their authorisation system, which is a C++ library ( a .cpp file and a header). I have no idea where to begin with this. I am assuming I add these files into the AdditionalSourceCode folder but from there I have no idea how to get it callable from within HISE....

Any help for a complete C++ novice gratefully received.

I am also curious to learn it..

And in case it helps, Faust can already be used with Cmajor, see: https://faustdoc.grame.fr/tutorials/cmajor/

@Christoph-Hart Hey Legend,

Any tip on how to get started here?
In Three.js, Nothing makes sense to me LOL
Where and How to Download another example from Three.js?
Contacting Images and s, and Index?

Appreciate your help

@Christoph-Hart said in Move scripted algorithm to a third party C++ lib:

@ustk welcome to C++. Your .cpp file is probably not added to the Xcode project as translation unit (which is C++ gibberish for something that will be compiled).

I have seen that xcode might miss the file on StackOverflow but wasn't sure if it was my case and even less the how to :)

Why do you need to split it into .cpp and .h? If you want to keep the implementation organised like this, you need to use a header file which includes the two files.

For 2 reasons actually, my own experience, and be able to link existing libraries without too much modifications

@d-healey sounds good, so in the doc, it says if it's bigger than 50mo you're better off not putting them in the binary.
Seems logical!

Well!! Figured it out. For others facing this: HISE 3.0.0 (AFAIK) and newer needs Engine.loadAudioFilesIntoPool(); in order to correctly pool audio files for C++ API

So basically add:

Engine.loadAudioFilesIntoPool();

into the main script processor for your HISE project and proceed with the normal export.

There are a few ways to do it - https://docs.hise.audio/cpp_api/index.html

@ulrik I just wanted to thank you again for taking the time to write this code. I ended up adapting it, and thank you.

I've opened a github issue about this

Link Preview Image [bug] getUserPresetDirectory() doesn't work with full expansions · Issue #381 · christophhart/HISE

Forum Discussion https://forum.hise.audio/topic/7228/get-current-expansion-within-frontendhandler-getuserpresetdirectory Commit fcad7d6 Tested OS: Linux HISE: n/a Compiled Project: Yes In compiled Full Expansion projects FrontendHandler:...

favicon

GitHub (github.com)

It will work :) I'm going to combine it with Lindon's timer idea because I also have a pre-loading screen that pops up and prevents the second click being registered, a time will solve that.

That looks like a ready to use C++ plugin built with JUCE. Just throw it in the compiler and enjoy :)

You might want to ask for the Projucer file to so that it creates the project for your IDE.