I want to integrate JUCE dsp modules into HISE

[Straticah]

Hey i have a talented C++ programmer who is not yet familliar with HISE.

I want to integrate some of our JUCE dsp modules into HISE (prefered inside scriptnode) if not possible as rack container.

Which API/features can we use to integrate a C++ bridge?

Is it correct that we need to compile the juce modules twice - static + dynamic(dll)

How does the compilation work with C++ Nodes/Rack?

Best Ju

[Christoph Hart]

@Straticah If you are following the API from the juce::dsp::Processor classes then you can just use the wrapper I'm using to integrate the other juce::dsp effects into a scriptnode node.

https://github.com/christophhart/HISE/blob/d3f364f5c2832770a8bade634607e0f70b55f9df/hi_dsp_library/dsp_nodes/JuceNodes.h#L45

The compilation / development process usually involves compiling a DLL that only contains your custom effects that you hot plug into HISE during development and which gets included into the compilation of your final build at the end.

[Straticah]

@Christoph-Hart Ok, so to confirm: We create a AdditionalSourceCode.cpp in the AdditionalSourceCode folder where we include "JUCE style" all the other cpp files we need to compile?

How does the HISE-Editor pick up the changes, so we can use the new nodes?

Edit: this path looks promising aswell but i am not sure \HISE-develop\hi_modules\nodes

[Straticah]

@Christoph-Hart is there a documentation about this process? I wonder how and where HISE recognizes a custom node.

Also, would it be possible to have a juce.dsp node with a compiler and code editor link like there is one for FAUST?

[Christoph Hart]

@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:

1. Create a C++ template file
2. Export the DLL
3. Open the project (in DspNetworks/Binaries/)
4. 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.