You're almost there, you need to right-click the "Parallel Bandpasses_DynamicLibrary", not the Solution. It's the first nested entry in the solution browser.
Then, check the path set to "Command", visible when navigating "Configuration Properties" -> "Debugging". This path needs to reference your HISE binary.

Save and hit run

You're almost there, you need to right-click the "Parallel Bandpasses_DynamicLibrary", not the Solution. It's the first nested entry in the solution browser.
Then, check the path set to "Command", visible when navigating "Configuration Properties" -> "Debugging". This path needs to reference your HISE binary.

Save and hit run

Found the file: hi_backend/backend/ProjectDllTemplate.cpp

Update:

I tested the same workflow on Windows and encoutered the same problem (linker errors). This made me investigate a little more and I found the reasons for the linker error:

1. I have another installation of JUCE (v. 8.0.0) that may have overriden the module paths. I had to make sure that the module is set to the version shipped with HISE.
2. The AutogeneratedProject.jucer that is generated does not include the "juce_audio_processors" module. Add it and it works, on both mac and Windows.

I don't know why this choice was made and if there is a way in the UI of HISE to change which modules are included in the auto generated project.
Alternatively, if someone could point me to where I have to modify the source code of HISE would great! Maybe that is quickly done by @Christoph-Hart ?

Otherwise, exporting the plugin using the HISE interface will overwrite the project each time and I have to add the module again and again.

I might share a few more insights, maybe someone has an idea.

First, find an image of the aforementioned linker error below.

I assume that if I would compile the same thing on Apple Silicon, I would get a x86_x64 linking error.

Interestingly enough, when I export the HISE project containing the very same code as FX plugin (using the export functionality in HISE), I do not get linker errors.

Any idea?

@Lindon

This is good to know. Thanks!

@Lindon

So is that a known bug? I'm quite new to the field, that would be good to know.

However, I have to note that all other effects (including my own JUCE VST3 effect) worked just fine on the affected systems.

In HISE, i.e., in BackendProcessor.cpp and MainController.cpp I see some, let's say "FL Studio-specific" code. But whatever it does, it does not seem to fix this issue.

I was able to fix the problem on the affected systems by changing an Audio setting in FL Studio.

The solution is to enable "Align tick lengths".

However, I have no idea why this is necessary and if this points towards a bug in the backend of HISE.

Dear HISE community,

related to my first post, I have a couple more issues that I could use your help for.

I wanted to integrate a JUCE effect for which I have the c++ source code in the form of AudioProcessor.h/.cpp.
This code compiles and works with JUCE 7 and 8.

Question 1. Will HISE be bumped to a more recent version of JUCE at some point?

For now, I created a backport for JUCE 6.

To integrate it into HISE, I followed the described procedure:

1. Tools -> Create C++ third party node template
2. I copied the AudioProcessor.cpp/.h file into the src/ subdirectory.
3. I wrote glue code to actually use the code in the generated template.
4. I included both AudioProcessor.cpp and AudioProcessor.h in the template file.
5. I compile the code using Export -> Compile DSP networks as dll

Now the compilation works well, however the linking fails, indicating that code from juce::AudioProcessor has not been linked.
More precisely, no code seems to have been compiled for arm64 (I'm compiling a MacBook with Intel hardware, using XCode and MacOS Ventura).
Some other classes from JUCE compile and link without any problems.

When I actually copy the definitions of the missing functions from JUCE (that comes with HISE) into the third party node template, the linker errors vanish.
(Please note, that I did not remove all linker errors since I do not consider that a solution to the problem, I just wanted to check if the deinitions are actually missing).

Question 2. So I assume that the source files (at least containing juce::AudioProcessor) are not linked properly in the export sequence of HISE?

The last question assumes that some node with dials has been added to the DSP network.
Please also assume that HISE has beed compiled as VST3 plugin and is used in a DAW (I'm using FL Studio).

Question 3: Is there a way to automate dials/sliders/... of HISE in the DAW? Again related to my first post, I wish to test the effect I'm designing right inside the DAW. (Afterall I assume that is the intended use-case of the plugin-version of HISE?)

Thank you very much in advance!

Dear HISE community,

I'm working with HISE for a week now.
The goal is to use it as plugin inside a DAW (I'm using FL Studio) and to plug together an effect using the node-graph network editor and to test and work work with it live in the DAW.

For that, I compiled the vanilla source code of the plugin project of HISE (testing both remote HEADs of develop #b7eb82e, and master HEAD #40c0e0a).
The only change I made to the respective JUCE project was to set HISE_BACKEND_AS_FX=1 to the preprocessor definitions.

I signed/notarized the resulting VST3 plugin, and loaded it into FL studio on each of the following hardware/software configurations.
Also, I created a simple "pass-through" network. I would expect an unmodified sound, as if no VST3 plugin was loaded.
The result I obtain however, was:

1. Mac OS Ventura, Intel Chip -> weird distorted sound
2. Mac OS Monterey, Apple M1 Chip -> weird distorted sound
3. Mac OS Ventura, Apple M2 Chip -> clean sound

Only configuration 3 lead to the expected output, hence I assume it works in principle (it's the very same binary!).
Configuration 1 is the system that I use for development. It is pretty much a vanilla system.

I tried changing buffer size and sample rate in FL Studio, which has a marginal effect. Increasing the buffer size seems to help a bit, though.
The weird distorted sound to me sounds very similar to what I got when I compiled a VST3 plugin in debug mode, as it could not keep up processing in time.
However, I explicitly deleted all debug targets and made sure I build in release mode. Also, the processing network is so simple that even in debug mode, I would expect a clean sound.

Is there some flag I have to set or some setting to adjust that could help?

Thank you very much in advance!

Btw: I have more questions that would not fit inside this post so I'll create another topic.